Run tool calls from code with Code Mode - Claude Code Docs
Documentation Index Fetch the complete documentation index at: /docs/llms.txt Use this file to discover all available pages before exploring further. Skip to main content Assistant Responses are generated using AI and may contain mistakes. Code Mode changes how Claude uses its tools . Without Code Mode, Claude asks for tool calls such as Bash, Read, or Edit directly and reads each result before it decides what to do next.
With Code Mode, Claude writes a piece of JavaScript that makes the tool calls, and Claude Code runs that code in your session. Code Mode is experimental and off by default. It may change or be removed in any release. To share feedback, run /feedback . How Code Mode works In a Code Mode session, you still describe your task in a prompt, and Claude writes JavaScript to carry it out. One piece of code can run commands in parallel, use one result in the next call, and return the part of the output that Claude needs to read.
For example, if you ask Claude to raise a retry limit, Claude might write this code to find the file, edit it, and run the tests. The last line returns the file’s path and the test output to Claude: const files = await $ `rg -l "function retryPolicy" src` . text (); const target = files . trim (). split ( " \n " )[ 0 ]; await edit ( target , "maxAttempts: 3" , "maxAttempts: 5" ); ({ edited: target , tests: $ `npm test -- retryPolicy` . nothrow () }); In the conversation, you see the tool calls, such as the edit’s diff, and not the code.
To read the code, press Ctrl+O to open the transcript viewer . Each piece of code appears there as a collapsed Code row, with a hint for how to expand it. When to use Code Mode Try Code Mode on tasks that take many related tool calls, such as: A change that repeats across many files A search whose results need filtering before Claude reads them Several independent commands that can run at the same time Code Mode limitations Before you turn on Code Mode, check that you can accept these limits: Resuming : you can resume a Code Mode session only in the terminal, with Code Mode on Auto mode : auto mode’s classifier reviews the code, not each tool call Long-running code : unless code can run in the background , you wait for it to finish, and it stops after ten minutes Hooks : you can see tool calls refused when a PreToolUse hook can’t run or times out Unavailable features : you can’t use Remote Control , Claude in Chrome , or computer use Moving the session : you can’t move the session to the Desktop app or turn it into a background session , and /fork can’t start a background copy Requirements Version : Claude Code v2.1.323 or later, on either release channel .
An older version starts without Code Mode, with or without the reason it isn't open to your account yet Account : a Claude subscription or Console account. You can’t use Code Mode through a gateway, Amazon Bedrock, Claude Platform on AWS, Google Cloud’s Agent Platform, Microsoft Foundry, or Claude Models on Google Cloud (Anthropic managed) Organization : your organization doesn’t use the HIPAA configuration or zero data retention Model : Claude Opus 5.5, Sonnet 5.5, Haiku 5.5, or Fable 5.2 Surface : an interactive claude session in a terminal.
Code Mode doesn’t work with -p , the Agent SDK, the VS Code panel, the Desktop app, or cloud sessions Agent teams : to use Code Mode with agent teams on, you need v2.1.326 or later. Teammates run in Code Mode in the default in-process display mode , and start without it in split panes Installation : the native build of Claude Code Windows : Git for Windows is installed You also can’t start Code Mode with some settings on, such as an API key helper, OpenTelemetry export, or DISABLE_TELEMETRY .
For the fix for each, see Code Mode doesn’t start . Try Code Mode Turn on Code Mode, give Claude a task, and look at the code that Claude wrote. 1 Check your version Run claude --version . If the version is older than v2.1.323, run claude update . If you’re on the stable channel and the update doesn’t reach v2.1.323, wait for stable to catch up or switch to latest . 2 Start Claude Code with Code Mode on Set the CLAUDE_CODE_EXPERIMENTAL_CODE_MODE environment variable to 1 .
To try Code Mode, set it in your shell. To turn on Code Mode for every new session, set it in your user settings. macOS, Linux, WSL Windows PowerShell settings.json CLAUDE_CODE_EXPERIMENTAL_CODE_MODE = 1 claude $ env: CLAUDE_CODE_EXPERIMENTAL_CODE_MODE = "1" claude Save this env block in ~/.claude/settings.json and start claude : { "env" : { "CLAUDE_CODE_EXPERIMENTAL_CODE_MODE" : "1" } } Claude Code ignores this variable in a project’s settings files , so a repository you clone can’t turn on Code Mode for you.
3 Confirm that you want Code Mode Claude Code asks you to confirm before your first Code Mode session. Select Yes, turn on Code Mode . Claude Code restarts and shows this line near the top of the session: Code Mode (experimental) is on · this session can be resumed only with Code Mode on If you see a different line or none, see Code Mode doesn’t start . 4 Give Claude a task with many tool calls In a project you know, send a prompt such as this one: Read every Markdown file in this project and list the links that point to local files that don't exist.
5 Read the code Claude wrote Press Ctrl+O and expand a Code row to see the JavaScript behind the tool calls. Press Ctrl+O again to return to the conversation. To resume a Code Mode session later, keep CLAUDE_CODE_EXPERIMENTAL_CODE_MODE set to 1 when you run claude --continue or claude --resume . With Code Mode off, Claude Code refuses to resume the session. Sessions that you started without Code Mode resume without Code Mode, even with the variable set.
Turn off Code Mode Remove CLAUDE_CODE_EXPERIMENTAL_CODE_MODE from your shell and from ~/.claude/settings.json , then start a new session. You can also keep the variable and change its value to 0 in either place. With a 0 in one place, Code Mode stays off even if you set 1 in the other. Block Code Mode for your organization Add CLAUDE_CODE_EXPERIMENTAL_CODE_MODE with the value 0 to your managed settings so that nobody in your organization can use Code Mode: { "env" : { "CLAUDE_CODE_EXPERIMENTAL_CODE_MODE" : "0" } } Users who are in a Code Mode session stay in it until they exit or restart Claude Code.
After that, your users start without Code Mode and can’t resume their Code Mode sessions while the 0 is in place. You can’t turn on Code Mode for your users from managed settings. Permissions and long-running code Your permission mode decides how the code that Claude writes is checked and whether you can talk to Claude while the code runs. Permission checks In auto and bypassPermissions modes, code can run from start to finish without a permission prompt.
Some calls still prompt you, such as the actions no mode auto-approves . Each tool call in the code goes through your deny and ask permission rules and PreToolUse hooks under the tool’s usual name, such as Bash or an MCP tool’s name . Beyond rules and hooks, a classifier reviews the code in auto mode, and you answer prompts in the modes that ask: Auto mode : the classifier reviews each piece of code before it runs, not each tool call.
It doesn’t see values computed at run time, such as a path taken from search output, so keep rules or hooks for calls you must control. You can still be prompted for some calls , such as calls in code that you approved yourself after repeated classifier blocks Other permission modes : you’re prompted for each tool call that would prompt you in that mode If you have a PreToolUse hook that allows or blocks shell commands, make it check each part of a command, as Bash rules do .
In Code Mode, a git push in a folder named app can reach your hook as cd 'app' && git push . To check the code itself, write a PreToolUse hook that matches REPL , the tool that runs the code, and read the JavaScript from tool_input.cod
The rest of this page is on the live site.