2026年4月9日 12:56

17 ファイル変更 +49 -30

この更新の概要

acceptEditsモードの権限範囲が拡大され、ファイル編集だけでなくmkdirやmvなどの一般的なファイルシステム操作も自動承認されるようになりました。フルスクリーン表示中のCtrl+o操作に、直近のプロンプトとレスポンスのみを表示するフォーカスビューが追加されています。MCPツールの出力制限に関して、個別のツール設定が環境変数よりも優先される仕様が明文化されました。分散トレーシングを可能にするTRACEPARENT環境変数の継承や、ステータスラインの定期更新設定など、開発効率を高める細かな機能改善が含まれています。

agent-sdk/agent-loop +2 -2

@@ -175,13 +175,13 @@ The permission mode option (`permission_mode` in Python, `permissionMode` in Typ

| Mode | Behavior |

| :- | :- |

| `"default"` | Tools not covered by allow rules trigger your approval callback; no callback means deny |

| `"acceptEdits"` | Auto-approves file edits, other tools follow default rules |

| `"acceptEdits"` | Auto-approves file edits and common filesystem commands (`mkdir`, `touch`, `mv`, `cp`, etc.); other Bash commands follow default rules |

| `"plan"` | No tool execution; Claude produces a plan for review |

| `"dontAsk"` | Never prompts. Tools pre-approved by [permission rules](/en/settings#permission-settings) run, everything else is denied |

| `"auto"` (TypeScript only) | Uses a model classifier to approve or deny each tool call. See [Auto mode](/en/permission-modes#eliminate-prompts-with-auto-mode) for availability and behavior |

| `"bypassPermissions"` | Runs all allowed tools without asking. Cannot be used when running as root on Unix. Use only in isolated environments where the agent's actions cannot affect systems you care about |

For interactive applications, use `"default"` with a tool approval callback to surface approval prompts. For autonomous agents on a dev machine, `"acceptEdits"` auto-approves file edits while still gating `Bash` behind allow rules. Reserve `"bypassPermissions"` for CI, containers, or other isolated environments. See [Permissions](/en/agent-sdk/permissions) for full details.

For interactive applications, use `"default"` with a tool approval callback to surface approval prompts. For autonomous agents on a dev machine, `"acceptEdits"` auto-approves file edits and common filesystem commands (`mkdir`, `touch`, `mv`, `cp`, etc.) while still gating other `Bash` commands behind allow rules. Reserve `"bypassPermissions"` for CI, containers, or other isolated environments. See [Permissions](/en/agent-sdk/permissions) for full details.

### Model

agent-sdk/permissions +3 -1

@@ -172,7 +172,9 @@ Auto-approves file operations so Claude can edit code without prompting. Other t

**Auto-approved operations:**

- File edits (Edit, Write tools)

- Filesystem commands: `mkdir`, `touch`, `rm`, `mv`, `cp`

- Filesystem commands: `mkdir`, `touch`, `rm`, `rmdir`, `mv`, `cp`, `sed`

Both apply only to paths inside the working directory or `additionalDirectories`. Paths outside that scope and writes to protected paths still prompt.

**Use when:** you trust Claude's edits and want faster iteration, such as during prototyping or when working in an isolated directory.

agent-sdk/quickstart +1 -1

@@ -259,7 +259,7 @@ With `Bash` enabled, try: `"Write unit tests for utils.py, run them, and fix any

| Mode | Behavior | Use case |

| - | - | - |

| `acceptEdits` | Auto-approves file edits, asks for other actions | Trusted development workflows |

| `acceptEdits` | Auto-approves file edits and common filesystem commands, asks for other actions | Trusted development workflows |

| `dontAsk` | Denies anything not in `allowedTools` | Locked-down headless agents |

| `auto` (TypeScript only) | A model classifier approves or denies each tool call | Autonomous agents with safety guardrails |

| `bypassPermissions` | Runs every tool without prompts | Sandboxed CI, fully trusted environments |

desktop +1 -1

@@ -60,7 +60,7 @@ Permission modes control how much autonomy Claude has during a session: whether

| Mode | Settings key | Behavior |

| - | - | - |

| **Ask permissions** | `default` | Claude asks before editing files or running commands. You see a diff and can accept or reject each change. Recommended for new users. |

| **Auto accept edits** | `acceptEdits` | Claude auto-accepts file edits but still asks before running terminal commands. Use this when you trust file changes and want faster iteration. |

| **Auto accept edits** | `acceptEdits` | Claude auto-accepts file edits and common filesystem commands like `mkdir`, `touch`, and `mv`, but still asks before running other terminal commands. Use this when you trust file changes and want faster iteration. |

| **Plan mode** | `plan` | Claude reads files and runs commands to explore, then proposes a plan without editing your source code. Good for complex tasks where you want to review the approach first. |

| **Auto** | `auto` | Claude executes all actions with background safety checks that verify alignment with your request. Reduces permission prompts while maintaining oversight. Currently a research preview. Available on Team, Enterprise, and API plans. Requires Claude Sonnet 4.6 or Opus 4.6. Enable in your Settings → Claude Code. |

| **Bypass permissions** | `bypassPermissions` | Claude runs without any permission prompts, equivalent to `--dangerously-skip-permissions` in the CLI. Enable in your Settings → Claude Code under "Allow bypass permissions mode". Only use this in sandboxed containers or VMs. Enterprise admins can disable this option. |

env-vars +1 -1

@@ -168,7 +168,7 @@ Claude Code supports the following environment variables to control its behavior

| `HTTP_PROXY` | Specify HTTP proxy server for network connections |

| `HTTPS_PROXY` | Specify HTTPS proxy server for network connections |

| `IS_DEMO` | Set to `1` to enable demo mode: hides your email and organization name from the header and `/status` output, and skips onboarding. Useful when streaming or recording a session |

| `MAX_MCP_OUTPUT_TOKENS` | Maximum number of tokens allowed in MCP tool responses. Claude Code displays a warning when output exceeds 10,000 tokens (default: 25000) |

| `MAX_MCP_OUTPUT_TOKENS` | Maximum number of tokens allowed in MCP tool responses. Claude Code displays a warning when output exceeds 10,000 tokens. Tools that declare [`anthropic/maxResultSizeChars`](/en/mcp#raise-the-limit-for-a-specific-tool) use that character limit for text content instead, but image content from those tools is still subject to this variable (default: 25000) |

| `MAX_STRUCTURED_OUTPUT_RETRIES` | Number of times to retry when the model's response fails validation against the [`--json-schema`](/en/cli-reference#cli-flags) in non-interactive mode (the `-p` flag). Defaults to 5 |

| `MAX_THINKING_TOKENS` | Override the [extended thinking](https://platform.claude.com/docs/en/build-with-claude/extended-thinking) token budget. The ceiling is the model's [max output tokens](https://platform.claude.com/docs/en/about-claude/models/overview#latest-models-comparison) minus one. Set to `0` to disable thinking entirely. On models with adaptive reasoning (Opus 4.6, Sonnet 4.6), the budget is ignored unless adaptive reasoning is disabled via `CLAUDE_CODE_DISABLE_ADAPTIVE_THINKING` |

| `MCP_CLIENT_SECRET` | OAuth client secret for MCP servers that require [pre-configured credentials](/en/mcp#use-pre-configured-oauth-credentials). Avoids the interactive prompt when adding a server with `--client-secret` |

fullscreen +7 -4

@@ -37,7 +37,7 @@ Because the conversation lives in the alternate screen buffer instead of your te

| Before | Now | Details |

| :- | :- | :- |

| `Cmd+f` or tmux search to find text | `Ctrl+o` then `/` to search, or `Ctrl+o` then `[` to write the conversation to native scrollback so `Cmd+f` works again | [Search and review the conversation](#search-and-review-the-conversation) |

| `Cmd+f` or tmux search to find text | `Ctrl+o` once for transcript mode (then `/` to search or `[` to write to scrollback), or `Ctrl+o` twice for focus view (last prompt + tool summary + response) | [Search and review the conversation](#search-and-review-the-conversation) |

| Terminal's native click-and-drag to select and copy | In-app selection, copies automatically on mouse release | [Use the mouse](#use-the-mouse) |

| `Cmd`-click to open a URL | Click the URL | [Use the mouse](#use-the-mouse) |

@@ -86,7 +86,9 @@ A value of `3` matches the default in `vim` and similar applications. The settin

## Search and review the conversation

Press `Ctrl+o` to enter transcript mode. With fullscreen rendering active, transcript mode gains `less`-style navigation and search:

In fullscreen rendering, `Ctrl+o` cycles through three states: normal prompt, transcript mode, and focus view. Press it once to enter transcript mode, press it again to return to a focus view showing just your last prompt, a one-line summary of tool calls with edit diffstats, and the final response. Press it a third time to return to the normal prompt screen.

Transcript mode gains `less`-style navigation and search:

| Key | Action |

| :- | :- |

@@ -96,14 +98,15 @@ Press `Ctrl+o` to enter transcript mode. With fullscreen rendering active, trans

| `g` / `G` or `Home` / `End` | Jump to top or bottom |

| `Ctrl+u` / `Ctrl+d` | Scroll half a page |

| `Ctrl+b` / `Ctrl+f` or `Space` / `b` | Scroll a full page |

| `Esc`, `q`, or `Ctrl+o` | Exit transcript mode |

| `Ctrl+o` | Advance to focus view |

| `Esc` or `q` | Exit transcript mode and return to the prompt |

Your terminal's `Cmd+f` and tmux search don't see the conversation because it lives in the alternate screen buffer, not the native scrollback. To hand the content back to your terminal, press `Ctrl+o` to enter transcript mode first, then:

- **`[`**: writes the full conversation into your terminal's native scrollback buffer, with all tool output expanded. The conversation is now ordinary text in your terminal, so `Cmd+f`, tmux copy mode, and any other native tool can search or select it. Long sessions may pause for a moment while this happens. This lasts until you exit transcript mode with `Esc` or `q`, which returns you to fullscreen rendering. The next `Ctrl+o` starts fresh.

- **`v`**: writes the conversation to a temporary file and opens it in `$VISUAL` or `$EDITOR`.

Press `Esc`, `q`, or `Ctrl+o` to return to the prompt.

Press `Esc` or `q` to return to the prompt.

## Use with tmux

headless +1 -1

@@ -140,7 +140,7 @@ claude -p "Run the test suite and fix any failures" \

--allowedTools "Bash,Read,Edit"

```

To set a baseline for the whole session instead of listing individual tools, pass a [permission mode](/en/permission-modes). `dontAsk` denies anything not in your `permissions.allow` rules, which is useful for locked-down CI runs. `acceptEdits` lets Claude write files without prompting, but shell commands and network requests still need an `--allowedTools` entry or a `permissions.allow` rule, otherwise the run aborts when one is attempted:

To set a baseline for the whole session instead of listing individual tools, pass a [permission mode](/en/permission-modes). `dontAsk` denies anything not in your `permissions.allow` rules, which is useful for locked-down CI runs. `acceptEdits` lets Claude write files without prompting and also auto-approves common filesystem commands such as `mkdir`, `touch`, `mv`, and `cp`. Other shell commands and network requests still need an `--allowedTools` entry or a `permissions.allow` rule, otherwise the run aborts when one is attempted:

```bash

claude -p "Apply the lint fixes" --permission-mode acceptEdits

how-claude-code-works +1 -1

@@ -160,7 +160,7 @@ Checkpoints are local to your session, separate from git. They only cover file c

Press `Shift+Tab` to cycle through permission modes:

- **Default**: Claude asks before file edits and shell commands

- **Auto-accept edits**: Claude edits files without asking, still asks for commands

- **Auto-accept edits**: Claude edits files and runs common filesystem commands like `mkdir` and `mv` without asking, still asks for other commands

- **Plan mode**: Claude uses read-only tools only, creating a plan you can approve before execution

- **Auto mode**: Claude evaluates all actions with background safety checks. Currently a research preview

interactive-mode +1 -1

@@ -28,7 +28,7 @@ See [Terminal configuration](/en/terminal-config) for details.

| `Ctrl+D` | Exit Claude Code session | EOF signal |

| `Ctrl+G` or `Ctrl+X Ctrl+E` | Open in default text editor | Edit your prompt or custom response in your default text editor. `Ctrl+X Ctrl+E` is the readline-native binding |

| `Ctrl+L` | Clear prompt input | Clears typed text, keeps conversation history |

| `Ctrl+O` | Toggle verbose output | Shows detailed tool usage and execution. Also expands MCP read and search calls, which collapse to a single line like "Queried slack" by default |

| `Ctrl+O` | Toggle transcript viewer | Shows detailed tool usage and execution. Also expands MCP read and search calls, which collapse to a single line like "Queried slack" by default. In [fullscreen rendering](/en/fullscreen), cycles through three states: normal prompt, transcript mode, and focus view (last prompt + tool summary + response) |

| `Ctrl+R` | Reverse search command history | Search through previous commands interactively |

| `Ctrl+V` or `Cmd+V` (iTerm2) or `Alt+V` (Windows) | Paste image from clipboard | Inserts an `[Image #N]` chip at the cursor so you can reference it positionally in your prompt |

| `Ctrl+B` | Background running tasks | Backgrounds bash commands and agents. Tmux users press twice |

mcp +7 -6

@@ -691,8 +691,9 @@ Tips:

When MCP tools produce large outputs, Claude Code helps manage the token usage to prevent overwhelming your conversation context:

- **Output warning threshold**: Claude Code displays a warning when any MCP tool output exceeds 10,000 tokens

- **Configurable limit**: You can adjust the maximum allowed MCP output tokens using the `MAX_MCP_OUTPUT_TOKENS` environment variable

- **Default limit**: The default maximum is 25,000 tokens

- **Configurable limit**: you can adjust the maximum allowed MCP output tokens using the `MAX_MCP_OUTPUT_TOKENS` environment variable

- **Default limit**: the default maximum is 25,000 tokens

- **Scope**: the environment variable applies to tools that don't declare their own limit. Tools that set [`anthropic/maxResultSizeChars`](#raise-the-limit-for-a-specific-tool) use that value instead for text content, regardless of what `MAX_MCP_OUTPUT_TOKENS` is set to. Tools that return image data are still subject to `MAX_MCP_OUTPUT_TOKENS`

To increase the limit for tools that produce large outputs:

@@ -707,7 +708,7 @@ This is particularly useful when working with MCP servers that:

- Generate detailed reports or documentation

- Process extensive log files or debugging information

### Override result size per tool

### Raise the limit for a specific tool

If you're building an MCP server, you can allow individual tools to return results larger than the default persist-to-disk threshold by setting `_meta["anthropic/maxResultSizeChars"]` in the tool's `tools/list` response entry. Claude Code raises that tool's threshold to the annotated value, up to a hard ceiling of 500,000 characters.

@@ -718,14 +719,14 @@ This is useful for tools that return inherently large but necessary outputs, suc

"name": "get_schema",

"description": "Returns the full database schema",

"_meta": {

"anthropic/maxResultSizeChars": 500000

"anthropic/maxResultSizeChars": 200000

}

```

The annotation raises the per-tool persist threshold but does not bypass the global `MAX_MCP_OUTPUT_TOKENS` limit, which defaults to 25,000 tokens or roughly 100,000 characters. To return results larger than that, users must also raise `MAX_MCP_OUTPUT_TOKENS`.

The annotation applies independently of `MAX_MCP_OUTPUT_TOKENS` for text content, so users don't need to raise the environment variable for tools that declare it. Tools that return image data are still subject to the token limit.

If you frequently encounter output warnings with specific MCP servers you don't control, consider increasing the `MAX_MCP_OUTPUT_TOKENS` limit. You can also ask the server author to add the `anthropic/maxResultSizeChars` annotation or to paginate their responses. The annotation has no effect on tools that return image content; for those, raising `MAX_MCP_OUTPUT_TOKENS` is the only option.

## Respond to MCP elicitation requests

monitoring-usage +2 -0

@@ -115,6 +115,8 @@ Tracing is off by default. To enable it, set both `CLAUDE_CODE_ENABLE_TELEMETRY=

Spans redact user prompt text and tool content by default. Set `OTEL_LOG_USER_PROMPTS=1` and `OTEL_LOG_TOOL_CONTENT=1` to include them.

When tracing is active, Bash subprocesses automatically inherit a `TRACEPARENT` environment variable containing the W3C trace context of the active tool execution span. This lets any subprocess that reads `TRACEPARENT` parent its own spans under the same trace, enabling end-to-end distributed tracing through scripts and commands that Claude runs.

### Dynamic headers

For enterprise environments that require dynamic authentication, you can configure a script to generate headers dynamically:

overview +6 -6

@@ -19,19 +19,19 @@ To install Claude Code, use one of the following methods:

**macOS, Linux, WSL:**

```bash theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null}

curl -fsSL https://claude.ai/install.sh | bash

```

**Windows PowerShell:**

```powershell theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null}

irm https://claude.ai/install.ps1 | iex

```

**Windows CMD:**

```batch theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null}

curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

```

@@ -41,13 +41,13 @@ If you see `The token '&&' is not a valid statement separator`, you're in PowerS

Native installations automatically update in the background to keep you on the latest version.

brew install --cask claude-code

```

Homebrew installations do not auto-update. Run `brew upgrade claude-code` periodically to get the latest features and security fixes.

winget install Anthropic.ClaudeCode

```

@@ -79,7 +79,7 @@ Download and install:

- [macOS](https://claude.ai/api/desktop/darwin/universal/dmg/latest/redirect?utm_source=claude_code\&utm_medium=docs) (Intel and Apple Silicon)

- [Windows](https://claude.ai/api/desktop/win32/x64/setup/latest/redirect?utm_source=claude_code\&utm_medium=docs) (x64)

- [Windows ARM64](https://claude.ai/api/desktop/win32/arm64/setup/latest/redirect?utm_source=claude_code\&utm_medium=docs) (remote sessions only)

- [Windows ARM64](https://claude.ai/api/desktop/win32/arm64/setup/latest/redirect?utm_source=claude_code\&utm_medium=docs)

After installing, launch Claude, sign in, and click the **Code** tab to start coding. A [paid subscription](https://claude.com/pricing?utm_source=claude_code\&utm_medium=docs\&utm_content=overview_desktop_pricing) is required.

permission-modes +5 -2

@@ -16,7 +16,7 @@ Each mode makes a different tradeoff between convenience and oversight. The tabl

| Mode | What runs without asking | Best for |

| :- | :- | :- |

| `default` | Reads only | Getting started, sensitive work |

| [`acceptEdits`](#auto-approve-file-edits-with-acceptedits-mode) | Reads and file edits | Iterating on code you're reviewing |

| [`acceptEdits`](#auto-approve-file-edits-with-acceptedits-mode) | Reads, file edits, and common filesystem commands (`mkdir`, `touch`, `mv`, `cp`, etc.) | Iterating on code you're reviewing |

| [`plan`](#analyze-before-you-edit-with-plan-mode) | Reads only | Exploring a codebase before changing it |

| [`auto`](#eliminate-prompts-with-auto-mode) | Everything, with background safety checks | Long tasks, reducing prompt fatigue |

| [`dontAsk`](#allow-only-pre-approved-tools-with-dontask-mode) | Only pre-approved tools | Locked-down CI and scripts |

@@ -93,7 +93,9 @@ claude remote-control --permission-mode acceptEdits

## Auto-approve file edits with acceptEdits mode

`acceptEdits` mode lets Claude create and edit files in your working directory without prompting. Writes to [protected paths](#protected-paths) and all non-edit actions still prompt the same as default mode. The status bar shows `⏵⏵ accept edits on` while this mode is active.

`acceptEdits` mode lets Claude create and edit files in your working directory without prompting. The status bar shows `⏵⏵ accept edits on` while this mode is active.

In addition to file edits, `acceptEdits` mode auto-approves common filesystem Bash commands: `mkdir`, `touch`, `rm`, `rmdir`, `mv`, `cp`, and `sed`. Like file edits, these are auto-approved only for paths inside your working directory or `additionalDirectories`. Paths outside that scope, writes to [protected paths](#protected-paths), and all other Bash commands still prompt.

Use `acceptEdits` when you want to review changes in your editor or via `git diff` after the fact rather than approving each edit inline. Press `Shift+Tab` once from default mode to enter it, or start with it directly:

@@ -168,6 +170,7 @@ The classifier trusts your working directory and your repo's configured remotes.

- Reading `.env` and sending credentials to their matching API

- Read-only HTTP requests

- Pushing to the branch you started on or one Claude created

- Sandbox network access requests

Run `claude auto-mode defaults` to see the full rule lists. If routine actions get blocked, an administrator can add trusted repos, buckets, and services via the `autoMode.environment` setting: see [Configure the auto mode classifier](/en/permissions#configure-the-auto-mode-classifier).

permissions +1 -1

@@ -36,7 +36,7 @@ Claude Code supports several permission modes that control how tools are approve

| Mode | Description |

| :- | :- |

| `default` | Standard behavior: prompts for permission on first use of each tool |

| `acceptEdits` | Automatically accepts file edit permissions for the session, except writes to protected directories |

| `acceptEdits` | Automatically accepts file edits and common filesystem commands (`mkdir`, `touch`, `mv`, `cp`, etc.) for paths in the working directory or `additionalDirectories` |

| `plan` | Plan Mode: Claude can analyze but not modify files or execute commands |

| `auto` | Auto-approves tool calls with background safety checks that verify actions align with your request. Currently a research preview |

| `dontAsk` | Auto-denies tools unless pre-approved via `/permissions` or `permissions.allow` rules |

settings +1 -0

@@ -280,6 +280,7 @@ Configure advanced sandboxing behavior. Sandboxing isolates bash commands from y

| `network.allowUnixSockets` | Unix socket paths accessible in sandbox (for SSH agents, etc.) | `["~/.ssh/agent-socket"]` |

| `network.allowAllUnixSockets` | Allow all Unix socket connections in sandbox. Default: false | `true` |

| `network.allowLocalBinding` | Allow binding to localhost ports (macOS only). Default: false | `true` |

| `network.allowMachLookup` | Additional XPC/Mach service names the sandbox may look up (macOS only). Supports a single trailing `*` for prefix matching. Needed for tools that communicate via XPC such as the iOS Simulator or Playwright. | `["com.apple.coresimulator.*"]` |

| `network.allowedDomains` | Array of domains to allow for outbound network traffic. Supports wildcards (e.g., `*.example.com`). | `["github.com", "*.npmjs.org"]` |

| `network.allowManagedDomainsOnly` | (Managed settings only) Only `allowedDomains` and `WebFetch(domain:...)` allow rules from managed settings are respected. Domains from user, project, and local settings are ignored. Non-allowed domains are blocked automatically without prompting the user. Denied domains are still respected from all sources. Default: false | `true` |

| `network.httpProxyPort` | HTTP proxy port used if you wish to bring your own proxy. If not specified, Claude will run its own proxy. | `8080` |

statusline +8 -1

@@ -59,6 +59,8 @@ The `command` field runs in a shell, so you can also use inline commands instead

The optional `padding` field adds extra horizontal spacing (in characters) to the status line content. Defaults to `0`. This padding is in addition to the interface's built-in spacing, so it controls relative indentation rather than absolute distance from the terminal edge.

The optional `refreshInterval` field re-runs your command every N seconds in addition to the [event-driven updates](#how-status-lines-work). The minimum is `1`. Set this when your status line shows time-based data such as a clock, or when background subagents change git state while the main session is idle. Leave it unset to run only on events.

### Disable the status line

Run `/statusline` and ask it to remove or clear your status line (e.g., `/statusline delete`, `/statusline clear`, `/statusline remove it`). You can also manually delete the `statusLine` field from your settings.json.

@@ -117,6 +119,8 @@ Claude Code runs your script and pipes [JSON session data](#available-data) to i

Your script runs after each new assistant message, when the permission mode changes, or when vim mode toggles. Updates are debounced at 300ms, meaning rapid changes batch together and your script runs once things settle. If a new update triggers while your script is still running, the in-flight execution is cancelled. If you edit your script, the changes won't appear until your next interaction with Claude Code triggers an update.

These triggers can go quiet when the main session is idle, for example while a coordinator waits on background subagents. To keep time-based or externally-sourced segments current during idle periods, set [`refreshInterval`](#manually-configure-a-status-line) to also re-run the command on a fixed timer.

**What your script can output**

- **Multiple lines**: each `echo` or `print` statement displays as a separate row. See the [multi-line example](#display-multiple-lines).

@@ -135,6 +139,7 @@ Claude Code sends the following JSON fields to your script via stdin:

| `cwd`, `workspace.current_dir` | Current working directory. Both fields contain the same value; `workspace.current_dir` is preferred for consistency with `workspace.project_dir`. |

| `workspace.project_dir` | Directory where Claude Code was launched, which may differ from `cwd` if the working directory changes during a session |

| `workspace.added_dirs` | Additional directories added via `/add-dir` or `--add-dir`. Empty array if none have been added |

| `workspace.git_worktree` | Git worktree name when the current directory is inside a linked worktree created with `git worktree add`. Absent in the main working tree. Populated for any git worktree, unlike `worktree.*` which applies only to `--worktree` sessions |

| `cost.total_cost_usd` | Total session cost in USD |

| `cost.total_duration_ms` | Total wall-clock time since the session started, in milliseconds |

| `cost.total_api_duration_ms` | Total time spent waiting for API responses in milliseconds |

@@ -175,7 +180,8 @@ Your status line command receives this JSON structure via stdin:

"workspace": {

"current_dir": "/current/working/directory",

"project_dir": "/original/project/directory",

"added_dirs": []

"added_dirs": [],

"git_worktree": "feature-xyz"

"version": "2.1.90",

"output_style": {

@@ -231,6 +237,7 @@ Your status line command receives this JSON structure via stdin:

**Fields that may be absent** (not present in JSON):

- `session_name`: appears only when a custom name has been set with `--name` or `/rename`

- `workspace.git_worktree`: appears only when the current directory is inside a linked git worktree

- `vim`: appears only when vim mode is enabled

- `agent`: appears only when running with the `--agent` flag or agent settings configured

- `worktree`: appears only during `--worktree` sessions. When present, `branch` and `original_branch` may also be absent for hook-based worktrees

sub-agents +1 -1

@@ -314,7 +314,7 @@ The `permissionMode` field controls how the subagent handles permission prompts.

| Mode | Behavior |

| :- | :- |

| `default` | Standard permission checking with prompts |

| `acceptEdits` | Auto-accept file edits except in protected directories |

| `acceptEdits` | Auto-accept file edits and common filesystem commands for paths in the working directory or `additionalDirectories` |

| `auto` | [Auto mode](/en/permission-modes#eliminate-prompts-with-auto-mode): a background classifier reviews commands and protected-directory writes |

| `dontAsk` | Auto-deny permission prompts (explicitly allowed tools still work) |

| `bypassPermissions` | Skip permission prompts |