Step-by-step guide to get an access token for publishing to the Open VSX Registry, the open alternative to the VS Code Marketplace used by VS Codium, Gitpod, and other open-source editors.
- A GitHub account
- Access to your GitHub repository settings
- Go to open-vsx.org
- Click Log In (top right)
- Sign in with your GitHub account
- After signing in, go to your user settings
- Under Namespaces, type your publisher ID (same as
publisherinpackage.json) - Click Create
Note: The namespace must match the
publisherfield in yourpackage.jsonexactly.
- Go to your user settings → Tokens
- Enter a description (e.g.,
GitHub Actions publish) - Click Create Token
- Copy the token immediately — you won't be able to see it again
Go to your repository → Settings → Secrets and variables → Actions → New repository secret
| Secret Name | Value |
|---|---|
OVSX_PAT |
The access token from Step 3 |
The CD workflow will automatically publish to Open VSX after publishing to the VS Code Marketplace.
- Create the namespace first in your Open VSX user settings (Step 2).
- Make sure you are a member/owner of the namespace that matches your
publisherinpackage.json.
- Generate a new token in your Open VSX user settings and update the
OVSX_PATsecret.
The VS Code Marketplace is proprietary and only accessible from Microsoft's VS Code. Open VSX provides the same extension registry for:
- VS Codium — FOSS build of VS Code
- Gitpod — cloud development environments
- Eclipse Theia — extensible IDE platform
- Other editors using the Open VSX protocol
Publishing to both registries ensures your extension reaches the widest audience.