タイムラインに戻る

5 ファイル変更+8-8

この更新の概要

セッションのバックグラウンド実行時におけるモニターツールの挙動が明記されました。設定の優先順位に関する説明が強化され、拒否ルールが許可ルールよりも常に優先される仕組みや、スカラー値と配列値で異なるマージの挙動が詳しく解説されています。また、管理設定（managed settings）によって強制されたプラグインやフックの無効化に関する制約事項が追加されました。

agent-view+1-1

インタラクティブセッションをバックグラウンドへ移行する際、モニターツールが継続されない制限と、移行後に開始したモニターは維持される仕様が追記されました。

@@ -230,7 +230,7 @@ When agent view is grouped by directory, the highlighted row's directory becomes
Run `/background` or its alias `/bg` to move the current conversation into a background session. Pass a prompt such as `/bg run the test suite and fix any failures` to give one more instruction first.
Backgrounding from an interactive session starts a fresh process that resumes from the saved conversation, so running subagents and background commands do not transfer to it. Claude asks you to confirm before backgrounding when any are running. Once in the background, the session can start new subagents and background commands, and those keep running across later detach and reattach.
Backgrounding from an interactive session starts a fresh process that resumes from the saved conversation, so running subagents, [monitors](/en/tools-reference#monitor-tool), and background commands do not transfer to it. Claude asks you to confirm before backgrounding when any are running. Once in the background, the session can start new subagents, monitors, and background commands, and those keep running across later detach and reattach.
### From your shell
hooks-guide+1-1

フックを無効化する設定に関して、管理設定で定義されたフックを実行停止するには管理設定側での指定が必要であるという補足が追加されました。

@@ -707,7 +707,7 @@ Where you add a hook determines its scope:
| [Plugin](/en/plugins) `hooks/hooks.json` | When plugin is enabled | Yes, bundled with the plugin |
| [Skill](/en/skills) or [agent](/en/sub-agents) frontmatter | While the skill or agent is active | Yes, defined in the component file |
Run [`/hooks`](/en/hooks#the-hooks-menu) in Claude Code to browse all configured hooks grouped by event. To disable all hooks at once, set `"disableAllHooks": true` in your settings file.
Run [`/hooks`](/en/hooks#the-hooks-menu) in Claude Code to browse all configured hooks grouped by event. To disable hooks, set `"disableAllHooks": true` in your settings file. Hooks configured in managed settings still run unless `disableAllHooks` is also set there.
If you edit settings files directly while Claude Code is running, the file watcher normally picks up hook changes automatically.
permissions+1-1

権限設定の優先度について、ユーザー設定とプロジェクト設定のどちらであっても拒否ルールが許可ルールに優先して適用される論理が明確化されました。

@@ -340,7 +340,7 @@ If a tool is denied at any level, no other level can allow it. For example, a ma
Embedding hosts can supply additional managed policy via the SDK `managedSettings` option when [`parentSettingsBehavior`](/en/settings#settings-precedence) is set to `"merge"`; embedder values can tighten policy but not loosen it.
If a permission is allowed in user settings but denied in project settings, the project setting takes precedence and the permission is blocked.
For example, if user settings allow a permission and project settings deny it, the deny rule blocks it. The reverse is also true: a user-level deny blocks a project-level allow, because deny rules from any scope are evaluated before allow rules.
## Example configurations
plugins+1-1

ローカルディレクトリからのプラグイン読み込みにおいて、管理設定で強制的に有効化・無効化されたプラグインは上書きできない制約が明示されました。

@@ -280,7 +280,7 @@ The flag also accepts a `.zip` archive of the plugin directory, which requires C
claude --plugin-dir ./my-plugin.zip
```
When a `--plugin-dir` plugin has the same name as an installed marketplace plugin, the local copy takes precedence for that session. This lets you test changes to a plugin you already have installed without uninstalling it first. Marketplace plugins force-enabled by managed settings are the only exception and cannot be overridden.
When a `--plugin-dir` plugin has the same name as an installed marketplace plugin, the local copy takes precedence for that session. This lets you test changes to a plugin you already have installed without uninstalling it first. The exception is plugins that managed settings force-enable or force-disable: `--plugin-dir` cannot override those.
As you make changes to your plugin, run `/reload-plugins` to pick up the updates without restarting. This reloads plugins, skills, agents, hooks, plugin MCP servers, and plugin LSP servers. Test your plugin components:
settings+4-4

設定の優先順位に関する説明が刷新され、単一の値は上書きされ、配列形式の設定値は連結されるという具体的な継承の仕組みが解説されています。

@@ -50,7 +50,7 @@ Claude Code uses a **scope system** to determine where configurations apply and
### How scopes interact
When the same setting is configured in multiple scopes, more specific scopes take precedence:
When the same setting appears in multiple scopes, Claude Code applies them in priority order:
1. **Managed** (highest) - can't be overridden by anything
2. **Command line arguments** - temporary session overrides
@@ -58,7 +58,7 @@ When the same setting is configured in multiple scopes, more specific scopes tak
4. **Project** - overrides user settings
5. **User** (lowest) - applies when nothing else specifies the setting
For example, if a permission is allowed in user settings but denied in project settings, the project setting takes precedence and the permission is blocked.
For example, if your user settings set `spinnerTipsEnabled` to `true` and project settings set it to `false`, the project value applies. Permission rules behave differently because they merge across scopes rather than override. See [Settings precedence](#settings-precedence).
### What uses scopes
@@ -520,7 +520,7 @@ Settings apply in order of precedence. From highest to lowest:
This hierarchy ensures that organizational policies are always enforced while still allowing teams and individuals to customize their experience. The same precedence applies whether you run Claude Code from the CLI, the [VS Code extension](/en/vs-code), or a [JetBrains IDE](/en/jetbrains).
For example, if your user settings allow `Bash(npm run *)` but a project's shared settings deny it, the project setting takes precedence and the command is blocked.
For example, if your user settings set `permissions.defaultMode` to `acceptEdits` and a project's shared settings set it to `default`, the project value applies. The example below covers how array-valued settings such as permission rules combine instead.
**Array settings merge across scopes.** When the same array-valued setting (such as `sandbox.filesystem.allowWrite` or `permissions.allow`) appears in multiple scopes, the arrays are **concatenated and deduplicated**, not replaced. This means lower-priority scopes can add entries without overriding those set by higher-priority scopes, and vice versa. For example, if managed settings set `allowWrite` to `["/opt/company-tools"]` and a user adds `["~/.kube"]`, both paths are included in the final configuration.
@@ -535,7 +535,7 @@ Run `/status` inside Claude Code to see which settings sources are active and wh
- **Skills**: Custom prompts that can be invoked with `/skill-name` or loaded by Claude automatically
- **MCP servers**: Extend Claude Code with additional tools and integrations
- **Precedence**: Higher-level configurations (Managed) override lower-level ones (User/Project)
- **Inheritance**: Settings are merged, with more specific settings adding to or overriding broader ones
- **Inheritance**: Settings merge across scopes; scalar values from higher-priority scopes override, and arrays concatenate
### System prompt