The Morph panel

Morph is CodeMorph's built-in agent, and the Morph panel is where you work with it. It lives in the secondary sidebar on the right side of the editor.

Opening and closing

• Press Ctrl L from anywhere.
• Click the typed counter in the status bar.
• Run View → Appearance → Secondary Side Bar if the right sidebar is hidden.

Morph remembers whether it was open or closed for each project, so it reopens the way you left it.

The three tabs

Tab	What it's for
Migrate	Scan & Plan, the batch list with progress, and the files waiting for review.
Verify	Run & Verify: typecheck, test suite and build, with each step's result.
Ask	Questions about your migration. Morph knows every change it made and why.

The instruction box

At the bottom of the panel is an input that reads Ask Morph or give an instruction…. It does two jobs:

• Instructions start or steer work: "Migrate the api folder, strict mode, keep tests green."
• Questions get answers: "Why is price a number and not a string?"

Press Enter or the send button to submit.

Adding context with @

Type @ to point Morph at something specific: a file, a folder or a symbol. Context narrows what Morph reads and makes answers more precise.

Commands with /

Type / for quick commands, such as starting a migration or running Verify, without leaving the keyboard.

Choosing a model

The model picker next to @ context and / commands chooses which Claude model Morph uses. Your choice is saved to the codemorph.ai.model setting. A larger model is worth it for conversions with tricky inference; a faster one is fine for quick questions.

Writing good instructions

Good instructions are specific about scope, standard and constraints.

Instead of	Try
"Migrate everything"	"Migrate lib and utils first, then stop"
"Make it typed"	"Migrate the api folder with strict mode"
"Be careful"	"Keep tests green and don't change module syntax in config/"
"Fix this"	"@payments.ts why does this need review, and can you type meta without any?"

Morph always respects the dependency order from the plan, so an instruction like "start with routes" still converts what those routes depend on first.

Starting fresh

CodeMorph: New Chat from the Command Palette starts a fresh conversation. The migration history (plan, results and changes) is kept, so Morph can still explain earlier work.

What Morph can and can't do

• Morph proposes changes as diffs. Nothing lands until you accept it.
• Morph reads your project through the dependency graph and the migration history.
• Morph doesn't send anything anywhere except your configured model provider, and only for conversion and Ask.
• Morph doesn't run arbitrary commands on your machine. Run & Verify runs your own tsc, test and build scripts.