Getting started

CodeMorph is a desktop code editor with a migration engine built in. You open a JavaScript project, and CodeMorph maps how every file depends on every other file, then plans a migration to TypeScript that starts at the leaves of that graph and works upward.

The idea is simple: a file is easiest to type correctly when everything it imports is already typed. So CodeMorph never asks a model to guess the shape of an import it hasn't seen yet.

What's in the beta

Capability	Status
CodeMorph editor for Windows, built from Code - OSS	Available now
Morph panel in the right sidebar (Ctrl L)	Available now
Scan & Plan: dependency graph and leaf-first batches	Available now
Batch migration and diff review	Available now
Run & Verify: typecheck, tests and build	Available now
Ask Morph about any change	Available now
Local models with Ollama	Coming soon
macOS and Linux	Coming soon

Four steps to your first migration

1. Install CodeMorph. Download the Windows installer and get past the SmartScreen prompt for the unsigned beta.
2. Open a JavaScript project. Use Open Folder on the Welcome page and trust the workspace when asked.
3. Run Scan & Plan. Press Ctrl Shift M, or open Morph with Ctrl L and click Start Migration. A few seconds later you'll see the plan.
4. Migrate, review, verify. Start the migration, accept each file's diff, then run Verify. Set your API key first.

How CodeMorph thinks about a migration

Every migration moves through the same stages, and each stage produces something you can inspect:

• Scan reads every source file and resolves every import into a dependency graph.
• Plan orders files so dependencies always come before the files that use them, then groups them into batches.
• Convert types each file against imports that are already TypeScript.
• Review shows every change as a diff you accept or reject.
• Verify runs your typecheck, tests and build across the whole project.

Key concepts

A few ideas show up everywhere in CodeMorph. Knowing them makes the rest of the docs quicker to read.

• Dependency graph. Which files import which. CodeMorph builds it by parsing your code, not by guessing from folder names.
• Leaf-first order. Files that import nothing local are migrated first, and your entry point last, so every file is typed against imports that are already TypeScript.
• Batches. Groups of about ten files, in dependency order, sized for one review sitting. Files that import each other in a cycle always share a batch.
• Baseline. The type errors your JavaScript already has, measured before anything changes. Progress is measured against it.
• Review. Every converted file is a diff you accept or reject. Nothing lands without you.
• Verified. Zero type errors, a passing test suite and a successful build, across the whole project.

See the Glossary for every term.

How these docs are organized

Section	Read it when
Start here	You're installing CodeMorph or running your first migration
Using CodeMorph	You want depth on a part of the workflow: the Morph panel, Scan & Plan, batch migration, review, Verify, Ask, settings or extensions
Reference	You need a fact quickly: supported projects, commands, shortcuts, privacy, troubleshooting, FAQ

What CodeMorph is not

• Not a codemod that sprinkles any. Files that can't be typed cleanly are left for you, not silenced.
• Not a cloud service. There's no CodeMorph server that receives your code. Conversion and Ask go to the model provider you choose.
• Not a plugin. It's a complete editor, so the workflow (graph, diffs, terminal, tests) lives in one place.

Next steps

• System requirements lists what your machine and project need.
• Your first migration walks through the whole workflow.
• The Morph panel explains the tabs, instructions and context.
• Settings and API keys covers the AI provider setup.
• Troubleshooting has fixes for the common beta snags.