Skip to content

Claude Code

crc is an IDE that Claude Code connects to, the same way it connects to VS Code or JetBrains. You do not install an extension; the bridge is part of the editor.

  1. Open the terminal panel with ⌃`.

  2. Run claude.

    It finds the crc window it is running in and connects by itself.

You need Claude Code installed and signed in; crc does not bundle it.

Without copying anything into the prompt, Claude can ask crc for:

Tool What crc answers
getCurrentSelection, getLatestSelection The file and selection you are on.
getDiagnostics Errors and warnings from the language servers.
getOpenEditors Your open tabs, which one is active and which have unsaved changes.
getWorkspaceFolders The project folder.
checkDocumentDirty, saveDocument Whether a file has unsaved edits, and saving it.
openFile Opening a file in a tab.
openDiff, closeAllDiffTabs Proposing an edit as a diff, and closing those diffs.

Every edit Claude proposes opens as a diff tab. Read it, then:

Accept the change⌘↩
Reject itEsc

Claude waits for your answer, however long you take.

Files that Claude writes to disk directly show up in their tabs at once, the same way any file changed by another program does: a clean tab reloads, and a tab with unsaved edits asks before anything is overwritten.

To turn the bridge off entirely, start crc with CRC_NO_CLAUDE=1 in its environment:

Terminal window
CRC_NO_CLAUDE=1 open -a crc .

Claude Code connecting to crc is the first step of a larger idea: an agent as a protocol client, reading the same buffer state, syntax tree and index the editor’s own UI uses. That is not built yet; Why crc exists says more.