Embedded Editor

Use the embedded editor when you need to read files, inspect diffs, or leave review context without leaving Coldtea.

The terminal tells you what the agent said. The editor shows what changed.

Open the editor

Use Cmd+Shift+E on macOS or Ctrl+Shift+E on Windows and Linux to toggle the editor surface. You can also open editor-focused views from workspace actions where your build exposes them.

The editor follows the active project or worktree. When you switch across projects, Coldtea starts the editor backend for the new project. When you stay in the same base project and move between linked worktree roots, Coldtea updates the workspace roots instead of treating it like a different project.

If the editor feels stuck, click the editor once, reopen the surface, and confirm the selected project before restarting the app.

Files and diffs

Use the editor to:

• Browse project files.
• Open changed files.
• Inspect a diff before accepting an agent's summary.
• Check whether the work happened in the expected project or worktree.

Do not review from terminal output alone. Agents can summarize the wrong thing with complete confidence. The diff is the part you can verify.

Comments and annotations

Coldtea supports review comments and annotations where the editor surface exposes them. Select the relevant line or range, add the comment, and send that context back to the agent when you want a revision.

Annotations are explicit context. The agent does not automatically know every open file, selection, or thought you had while reading. If a selection matters, attach it through the available annotation action or name the file and range in your prompt.

Shortcuts

Coldtea mirrors common editor shortcuts that desktop webviews often steal:

• Cmd+P / Ctrl+P for go-to-file.
• Cmd+S / Ctrl+S for save.
• Cmd+F / Ctrl+F for find.
• Cmd+Shift+P / Ctrl+Shift+P for the command palette.

If a shortcut does not respond, click the editor first and try again. Focus matters when a terminal, browser view, and editor are all on screen.

Review habit

When an agent says it is done, open the changed files before you answer. Check the small boring things: imports, paths, copy, tests, and whether the diff matches the task.

A short review prompt after that is much stronger:

In apps/docs/content/docs/features/composer.mdx, line 18 overstates file mentions. Soften it to say references are prompt text, then rerun prettier.

Next: review agent work or read how context moves between surfaces.