File editing inside the desktop

What you’ll know by the end of this check

• What “edit files in the app” actually means in practice
• When this replaces your editor — and when it absolutely doesn’t
• The friction-kill this introduces to long agent sessions

The shortest possible answer

The redesigned desktop lets you edit files directly in the Claude Code window. Open a file, type in it, save, move on. Claude sees your edits as part of the session context.

You’re not getting a VS Code replacement. You’re getting “no more Cmd-Tab to edit one line.”

What it’s for

Agent sessions produce situations where you want to make one small edit yourself without breaking the flow:

• Claude proposes a change. You want to tweak one sentence in the diff before approving.
• Claude edits a config file. You want to change one value before continuing.
• You spot a typo in the docs Claude just updated. Fix it in place.
• You’re reading a file Claude referenced and want to add a comment.

Before: Cmd-Tab to VS Code, find the file, edit, save, come back, tell Claude. After: click the file in the Claude Code window, edit, save, continue.

That’s it. Not a replacement for your editor. A friction-kill for the editor-adjacent moments inside an agent session.

What it’s NOT for

• Long-form writing or refactoring. Your editor has muscle-memory keybindings, extensions, themes, linters, snippets, LSP, the thing you like about your editor. The in-app editor won’t have any of that.
• Multi-file work. Cross-file renames, project-wide find-replace, big restructures. Use the real editor.
• Deep debugging. Breakpoints, watch expressions, inspector panels. Real editor.

The mental model: in-app editing is for the 10-second edits that used to cost a minute of context-switching. Anything longer, open the real editor.

The compounding effect

One 10-second friction-kill doesn’t seem like much. Fifty of them per session does. Agent sessions are death by a thousand tiny context switches: alt-tab to editor, switch to terminal, switch to browser, switch to Slack, back to Claude, “wait what was I doing.” Every one costs attention.

The in-app editor kills one class of these. Combine with integrated terminal (check 02) and you’ve killed two. That’s a meaningful change in how a session actually feels.

Things to try right now (6 minutes)

1. Start a Claude Code desktop session.
2. Have Claude edit a file that has an obvious 5-character tweak worth making (a variable name, a string, a color value).
3. Before approving the diff, edit it yourself in the app.
4. Save. Claude continues, now with your edit in context.

The canonical version

Verify behavior against Anthropic’s official release notes.

Ready to verify this check?

You’ve made an in-app edit during an agent session without opening a separate editor. You can name the difference between “in-app edit” territory and “real editor” territory. Mark it cleared.