Extensions
Your extensions, from an open registry.
CodeMorph's Extensions view is connected to Open VSX, the open, vendor-neutral extension registry. Thousands of extensions install in one click, exactly as you'd expect.
How it works
Open VSX, built in
Open VSX is an open-source extension registry run by the Eclipse Foundation.
Search and install
Open the Extensions view with Ctrl+Shift+X, search, and click Install. No account needed.
Updates
Installed extensions update from Open VSX automatically, the way you'd expect.
Standard extension API
CodeMorph runs the standard extension host, so extensions on Open VSX work unchanged.
Install from VSIX
Have a .vsix file? Run Extensions: Install from VSIX in the Command Palette.
Workspace trust
Restricted Mode limits what extensions can do in folders you haven't trusted.
Publish your own
Extension authors publish to Open VSX with the ovsx command-line tool.
Recommended
A good setup for a TypeScript migration
These extensions work well alongside CodeMorph. Search for each ID in the Extensions view.
| Extension | ID | Why |
|---|---|---|
| ESLint | dbaeumer.vscode-eslint | Lints JavaScript and TypeScript as you go. Pair it with typescript-eslint once files are converted. |
| Prettier | esbenp.prettier-vscode | Keeps converted files formatted the way your team expects, so diffs stay about types, not whitespace. |
| Error Lens | usernamehw.errorlens | Shows compiler diagnostics inline on the line they belong to. Handy when reviewing files that need you. |
| Pretty TypeScript Errors | yoavbls.pretty-ts-errors | Turns long TypeScript errors into readable, formatted explanations. |
| Vitest | vitest.explorer | Run and debug Vitest tests from the editor, alongside Run & Verify. |
| Jest | Orta.vscode-jest | Watch-mode test results in the editor for Jest projects. |
| GitLens | eamodio.gitlens | Blame, history and branch tools for reviewing migration commits. |
Availability on Open VSX is controlled by each extension's author. These were listed there at the time of writing.
Not available
What you won't find
Some extensions are licensed only for their publisher's own products, so they aren't on Open VSX.
- · Proprietary extensions whose licenses limit them to their publisher's own editors, such as some remote-development and live-collaboration tools.
- · Other built-in AI assistants. Morph is the built-in agent.
- · Cloud settings sync. Copy your settings.json and keybindings.json across instead.
Can't find an extension?
Many authors publish to both registries. If one you rely on is missing, ask its author to publish to Open VSX; it takes a few minutes with the ovsx tool.
For extension authors
Publish to Open VSX
- 01
Create an account
Sign in at open-vsx.org with GitHub, sign the publisher agreement and create an access token. - 02
Create your namespace
The namespace matches the publisher field in your package.json. - 03
Publish
Use the ovsx CLI from your extension's folder, or publish an existing .vsix.
Terminal
npx ovsx create-namespace <publisher> -p <token>
npx ovsx publish -p <token>
# or publish a packaged file
npx ovsx publish my-extension-1.0.0.vsix -p <token>FAQ
Questions about extensions
Why Open VSX?
It's the open, vendor-neutral extension registry, so CodeMorph can install extensions from it freely. Most popular extensions are published there.
Do extensions from my other editor carry over?
Not automatically. CodeMorph keeps its own extensions folder (~/.codemorph/extensions), so install your favorites again from Open VSX.
Are extensions safe?
Extensions run with full access to your workspace, as in any desktop editor. Install from authors you trust, and use Restricted Mode for folders you haven't reviewed.
Does CodeMorph need any extension to migrate?
No. The migration engine and Morph are built in. Extensions are for your everyday editing.
Can I turn off automatic extension updates?
Yes. Set extensions.autoUpdate to false in Settings.
Bring your setup with you.
Download the beta, open a project and see your migration plan in under a minute.