タイムラインに戻る

10 ファイル変更 +26 -17

この更新の概要

バックグラウンドセッションの終了操作が変更され、Ctrl+Cの2回押しや/stopコマンドによる明示的な制御が可能になりました。MCPツールの自動再接続機能や、サブエージェントで使用不可能なツール一覧が明確化されています。また、プラグインのインストール先リポジトリの変更や、モニタリングイベントにおける権限判定のロジックに関する詳細な説明が追加されました。

agent-view +3 -1

セッション中でのCtrl+Cの動作が標準的な割り込み処理に変更され、バックグラウンドセッションを維持したままデタッチするにはCtrl+Cを2回押す操作が必要になりました。

@@ -149,7 +149,9 @@ While attached, the session behaves like any other Claude Code session: every [c
Press `←` on an empty prompt to detach and return to agent view. If a dialog has focus and isn't responding to `←`, press `Ctrl+Z` to detach immediately.
Detaching never stops a background session: `←`, `Ctrl+C`, `Ctrl+D`, `Ctrl+Z`, and `/exit` all leave it running. To end a session from inside it, run `/stop`.
`Ctrl+C` keeps its standard interrupt behavior while attached: it cancels a running response or `!` shell command rather than detaching. Pressing `Ctrl+C` twice on an empty prompt detaches, the same as in any session.
Detaching never stops a background session: `←`, `Ctrl+Z`, `/exit`, and double `Ctrl+C` or double `Ctrl+D` all leave it running. To end a session from inside it, run `/stop`.
After you've dispatched or backgrounded a session, pressing `←` on an empty prompt works from any Claude Code session, not only ones you attached to from agent view. It backgrounds the current session and opens agent view with that row selected, so you can switch sessions without leaving the terminal. The row is created even from a fresh session with no conversation history, so `→` returns to it. When that row is the only one, agent view shows an onboarding hint below it. You can turn this shortcut off in `/config` (the `leftArrowOpensAgents` setting).
discover-plugins +1 -1

公式プラグインのインストール先パッケージ名が、従来の名称からclaude-code-pluginsへ変更されました。

@@ -151,7 +151,7 @@ For example, select **commit-commands** (a plugin that adds git workflow skills)
You can also install directly from the command line:
```shell theme={null}
/plugin install commit-commands@anthropics-claude-code
/plugin install commit-commands@claude-code-plugins
```
See [Configuration scopes](/en/settings#configuration-scopes) to learn more about scopes.
features-overview +2 -4

MCPツールの接続が切断された際の自動再接続機能について追記され、/mcpコマンドで接続ステータスが確認できる旨が明記されました。

@@ -143,7 +143,7 @@ MCP connects Claude to external services. Skills extend what Claude knows, inclu
These solve different problems and work well together:
**MCP** gives Claude the ability to interact with external systems. Without MCP, Claude can't query your database or post to Slack.
**MCP** gives Claude purpose-built tools for an external system, with the connection and authentication handled by the server.
**Skills** give Claude knowledge about how to use those tools effectively, plus workflows you can trigger with `/<name>`. A skill might include your team's database schema and query patterns, or a `/post-to-slack` workflow with your team's message formatting rules.
@@ -240,9 +240,7 @@ Use `disable-model-invocation: true` for skills with side effects. This saves co
**Context cost:** [Tool search](/en/mcp#scale-with-mcp-tool-search) is on by default, so idle MCP tools consume minimal context.
**Reliability note:** MCP connections can fail silently mid-session. If a server disconnects, its tools disappear without warning. Claude may try to use a tool that no longer exists. If you notice Claude failing to use an MCP tool it previously could access, check the connection with `/mcp`.
Run `/mcp` to see token costs per server. Disconnect servers you're not actively using.
Run `/mcp` to see connection status and token costs per server. Claude Code [reconnects to remote servers automatically](/en/mcp#automatic-reconnection) if they drop, and you can disconnect servers you're not actively using.
**When:** After file edits, and on demand when Claude navigates code.
mcp +1 -1

プラグインのインストール時にマーケットプレイスが見つからない場合の対処法として、公式マーケットプレイスを追加するコマンドの手順が追加されました。

@@ -38,7 +38,7 @@ In a Claude Code session, run:
/plugin install mcp-server-dev@claude-plugins-official
```
Then run `/reload-plugins` to activate it in the current session.
If Claude Code reports that the marketplace is not found, run `/plugin marketplace add anthropics/claude-plugins-official` first, then retry the install. Once installed, run `/reload-plugins` to activate it in the current session.
```
/mcp-server-dev:build-mcp-server
monitoring-usage +5 -5

ツール実行完了イベントの詳細が更新され、拒否されたコールが含まれないことや、拒否理由に応じたdecision_sourceの分類基準が詳しく説明されています。

@@ -528,7 +528,7 @@ Logged when a user submits a prompt.
#### Tool result event
Logged when a tool completes execution.
Logged when a tool completes execution. Not emitted if the tool call was rejected; see the [Tool decision event](#tool-decision-event) for rejections.
**Event Name**: `claude_code.tool_result`
@@ -544,8 +544,8 @@ Logged when a tool completes execution.
- `duration_ms`: Execution time in milliseconds
- `error_type`: Error category string when the tool failed, such as `"Error:ENOENT"` or `"ShellError"`
- `error` (when `OTEL_LOG_TOOL_DETAILS=1`): Full error message when the tool failed
- `decision_type`: Either `"accept"` or `"reject"`
- `decision_source`: Where the decision came from. One of `"config"`, `"hook"`, `"user_permanent"`, `"user_temporary"`, `"user_abort"`, or `"user_reject"`. See the [Tool decision event](#tool-decision-event) for what each value means.
- `decision_type`: Always `"accept"`, since this event is only emitted after the tool runs (rejected calls don't produce a tool result)
- `decision_source`: Where the permission decision came from. One of `"config"`, `"hook"`, `"user_permanent"`, or `"user_temporary"`. See the [Tool decision event](#tool-decision-event) for what each value means. The reject-only sources `"user_abort"` and `"user_reject"` never appear on this event.
- `tool_input_size_bytes`: Size of the JSON-serialized tool input in bytes
- `tool_result_size_bytes`: Size of the tool result in bytes
- `mcp_server_scope`: MCP server scope identifier (for MCP tools)
@@ -657,12 +657,12 @@ Logged when a tool permission decision is made (accept/reject).
- `tool_use_id`: Unique identifier for this tool invocation. Matches the `tool_use_id` passed to hooks, allowing correlation between OTel events and hook-captured data.
- `decision`: Either `"accept"` or `"reject"`
- `source`: Where the decision came from:
- `"config"`: Decided automatically without prompting, based on project settings, allow rules in the user's personal settings, enterprise managed policy, `--allowedTools` or `--disallowedTools` flags, the active permission mode, a session-scoped grant from an earlier prompt in the same interactive CLI session, or because the tool is inherently safe. The event does not indicate which of these sources matched.
- `"config"`: Decided automatically without prompting, based on project settings, allow or deny rules in the user's personal settings, enterprise managed policy, `--allowedTools` or `--disallowedTools` flags, the active permission mode, a session-scoped grant from an earlier prompt in the same interactive CLI session, or because the tool is inherently safe. The event does not indicate which of these sources matched.
- `"hook"`: A `PreToolUse` or `PermissionRequest` hook returned the decision.
- `"user_permanent"`: Emitted when the user chose "Yes, and don't ask again for ..." at a permission prompt, which saves an allow rule to their personal settings. In the interactive CLI this is emitted only for that choice itself; later calls that match the saved rule emit `"config"` instead. In Agent SDK or non-interactive `-p` sessions, both the initial choice and later rule matches emit `"user_permanent"`. Treated as an accept.
- `"user_temporary"`: Emitted when the user chose "Yes" at a permission prompt for a one-time approval, or chose one of the "... during this session" options on a file edit or read prompt. In the interactive CLI this is emitted only for the choice itself; later calls allowed by that session-scoped grant emit `"config"` instead. In Agent SDK or non-interactive `-p` sessions, both the choice and later matches emit `"user_temporary"`. Treated as an accept.
- `"user_abort"`: Emitted when the user dismissed the permission prompt without answering. Treated as a reject.
- `"user_reject"`: Emitted when the user chose "No" when prompted, or a call matched a deny rule in their personal settings. Treated as a reject.
- `"user_reject"`: Emitted when the user chose "No" when prompted. In the interactive CLI this is emitted only for that choice itself; calls that match a deny rule in the user's personal settings emit `"config"` instead. In Agent SDK or non-interactive `-p` sessions, calls that match a deny rule in personal settings emit `"user_reject"`. Treated as a reject.
#### Permission mode changed event
permissions +2 -0

ディレクトリ追加時の例外ルールが--add-dirフラグや/add-dirコマンドにのみ適用され、設定ファイルのリストには適用されない制限事項が追記されました。

@@ -271,6 +271,8 @@ Files in additional directories follow the same permission rules as the original
Adding a directory extends where Claude can read and edit files. It does not make that directory a full configuration root: most `.claude/` configuration is not discovered from additional directories, though a few types are loaded as exceptions.
These exceptions apply only to directories added with the `--add-dir` flag or the `/add-dir` command. Directories listed in `permissions.additionalDirectories` in a settings file grant file access only and do not load any of the configuration below.
The following configuration types are loaded from `--add-dir` directories:
| Configuration | Loaded from `--add-dir` |
remote-control +1 -1

Web版のclaude.aiやモバイルアプリ側でセッション名を変更した場合、ローカルのCLI上でもそのタイトルが同期・反映されるようになりました。

@@ -109,7 +109,7 @@ The remote session title is chosen in this order:
3. The last meaningful message in existing conversation history
4. An auto-generated name like `myhost-graceful-unicorn`, where `myhost` is your machine's hostname or the prefix you set with `--remote-control-session-name-prefix`
If you didn't set an explicit name, the title updates to reflect your prompt once you send one.
If you didn't set an explicit name, the title updates to reflect your prompt once you send one. Renaming a session from claude.ai or the Claude app also updates the local title shown in `claude --resume`.
If the environment already has an active session, you'll be asked whether to continue it or start a new one.
skills +1 -1

スキルの自動読み込みが適用されるコマンドと、適用外となる設定ファイルの記述方法に関する区別が明確化されました。

@@ -126,7 +126,7 @@ Files in `.claude/commands/` still work and support the same [frontmatter](#fron
#### Skills from additional directories
The `--add-dir` flag [grants file access](/en/permissions#additional-directories-grant-file-access-not-configuration) rather than configuration discovery, but skills are an exception: `.claude/skills/` within an added directory is loaded automatically. See [Live change detection](#live-change-detection) for how edits are picked up during a session.
The `--add-dir` flag and `/add-dir` command [grant file access](/en/permissions#additional-directories-grant-file-access-not-configuration) rather than configuration discovery, but skills are an exception: `.claude/skills/` within an added directory is loaded automatically. This exception applies only to `--add-dir` and `/add-dir`. The `permissions.additionalDirectories` setting in `settings.json` grants file access only and does not load skills. See [Live change detection](#live-change-detection) for how edits are picked up during a session.
Other `.claude/` configuration such as subagents, commands, and output styles is not loaded from additional directories. See the [exceptions table](/en/permissions#additional-directories-grant-file-access-not-configuration) for the complete list of what is and isn't loaded, and the recommended ways to share configuration across projects.
sub-agents +8 -1

メイン会話のUIや状態に依存するAgent、AskUserQuestion、ScheduleWakeupなどの特定のツールが、サブエージェントでは利用できない制限が追加されました。

@@ -264,7 +264,14 @@ You can control what subagents can do through tool access, permission modes, and
#### Available tools
Subagents can use any of Claude Code's [internal tools](/en/tools-reference). By default, subagents inherit all tools from the main conversation, including MCP tools.
Subagents inherit the [internal tools](/en/tools-reference) and MCP tools available in the main conversation by default. The following tools depend on the main conversation's UI or session state and are not available to subagents, even when listed in the `tools` field:
- `Agent`
- `AskUserQuestion`
- `EnterPlanMode`
- `ExitPlanMode`, unless the subagent's [`permissionMode`](#permission-modes) is `plan`
- `ScheduleWakeup`
- `WaitForMcpServers`
To restrict tools, use either the `tools` field (allowlist) or the `disallowedTools` field (denylist). This example uses `tools` to exclusively allow Read, Grep, Glob, and Bash. The subagent can't edit files, write files, or use any MCP tools:
tools-reference +2 -2

EnterWorktreeおよびExitWorktreeツールについて、独自の作業ディレクトリで動作するサブエージェントからは利用できない旨の条件が更新されました。

@@ -21,9 +21,9 @@ To add custom tools, connect an [MCP server](/en/mcp). To extend Claude with reu
| `CronList` | Lists all scheduled tasks in the session | No |
| `Edit` | Makes targeted edits to specific files. See [Edit tool behavior](#edit-tool-behavior) | Yes |
| `EnterPlanMode` | Switches to plan mode to design an approach before coding | No |
| `EnterWorktree` | Creates an isolated [git worktree](/en/worktrees) and switches into it. Pass a `path` to switch into an existing worktree of the current repository instead of creating a new one. Not available to subagents | No |
| `EnterWorktree` | Creates an isolated [git worktree](/en/worktrees) and switches into it. Pass a `path` to switch into an existing worktree of the current repository instead of creating a new one. Not available to subagents that already run in their own working directory, such as with [`isolation: worktree`](/en/sub-agents#supported-frontmatter-fields) | No |
| `ExitPlanMode` | Presents a plan for approval and exits plan mode | Yes |
| `ExitWorktree` | Exits a worktree session and returns to the original directory. Not available to subagents | No |
| `ExitWorktree` | Exits a worktree session and returns to the original directory. Not available to subagents that already run in their own working directory, such as with [`isolation: worktree`](/en/sub-agents#supported-frontmatter-fields) | No |
| `Glob` | Finds files based on pattern matching. See [Glob tool behavior](#glob-tool-behavior) | No |
| `Grep` | Searches for patterns in file contents. See [Grep tool behavior](#grep-tool-behavior) | No |
| `ListMcpResourcesTool` | Lists resources exposed by connected [MCP servers](/en/mcp) | No |