3 ファイル変更 +6 -2
この更新の概要
WebセッションにおけるプルリクエストのAuto-fix機能の制御方法が追加されました。Claude 3 Opusモデルの1Mコンテキストへの自動アップグレードに関する記述が更新され、Sonnetモデルでの利用条件が明確化されています。サーバー管理設定の強制適用時においても、認証切れに対応するための一部コマンドが制限の対象外となるよう仕様が変更されました。
@@ -684,6 +684,8 @@ There are a few ways to turn on auto-fix depending on where the PR came from and
- **From the mobile app**: tell Claude to auto-fix the PR, for example "watch this PR and fix any CI failures or review comments"
- **Any existing PR**: paste the PR URL into a session and tell Claude to auto-fix it
Auto-fix is a per-PR toggle. To stop monitoring, open the CI status bar in the web session and clear the **Auto-fix** toggle, or tell Claude to stop watching the PR.
### How Claude responds to PR activity
When auto-fix is active, Claude receives GitHub events for the PR including new review comments and CI check failures. For each event, Claude investigates and decides how to proceed:
Opusモデルの1Mコンテキストへの自動アップグレードについて補足され、Sonnetモデルで1Mコンテキストを利用する際は有料プランでも追加利用枠が必要な点が明記されました。
@@ -233,7 +233,7 @@ Thinking output is collapsed by default. Press `Ctrl+O` to toggle verbose mode a
Opus 4.7, Opus 4.6, and Sonnet 4.6 support a [1 million token context window](https://platform.claude.com/docs/en/build-with-claude/context-windows#1m-token-context-window) for long sessions with large codebases.
Availability varies by model and plan. On Max, Team, and Enterprise plans, Opus is automatically upgraded to 1M context with no additional configuration. This applies to both Team Standard and Team Premium seats.
Availability varies by model and plan. On Max, Team, and Enterprise plans, Opus is automatically upgraded to 1M context with no additional configuration. This applies to both Team Standard and Team Premium seats. Sonnet with 1M context is not part of the automatic upgrade and requires [extra usage](https://support.claude.com/en/articles/12429409-extra-usage-for-paid-claude-plans) on every subscription plan, including Max.
| Plan | Opus with 1M context | Sonnet with 1M context |
| - | - | - |
設定の取得に失敗してCLIが終了する設定になっている場合でも、認証情報の更新に必要なauthサブコマンドだけは実行可能になったことが説明されています。
@@ -161,6 +161,8 @@ To enable this, add the key to your managed settings configuration:
Before enabling this setting, ensure your network policies allow connectivity to `api.anthropic.com`. If that endpoint is unreachable, the CLI exits at startup and users cannot start Claude Code.
As of v2.1.139, the `claude auth` subcommands such as `claude auth login` are exempt from this check, so users can re-authenticate when expired credentials are the reason the settings fetch fails.
### Security approval dialogs
Certain settings that could pose security risks require explicit user approval before being applied:
@@ -196,7 +198,7 @@ Server-managed settings provide centralized policy enforcement, but they operate
| :- | :- |
| User edits the cached settings file | Tampered file applies at startup, but correct settings restore on the next server fetch |
| User deletes the cached settings file | First-launch behavior occurs: settings fetch asynchronously with a brief unenforced window |
| API is unavailable | Cached settings apply if available, otherwise managed settings are not enforced until the next successful fetch. With `forceRemoteSettingsRefresh: true`, the CLI exits instead of continuing |
| API is unavailable | Cached settings apply if available, otherwise managed settings are not enforced until the next successful fetch. With `forceRemoteSettingsRefresh: true`, the CLI exits instead of continuing, except for [`claude auth` subcommands](#enforce-fail-closed-startup) |
| User authenticates with a different organization | Settings are not delivered for accounts outside the managed organization |
| User configures a [third-party model provider](#platform-availability) | Server-managed settings are bypassed. This includes setting `CLAUDE_CODE_USE_BEDROCK`, `CLAUDE_CODE_USE_MANTLE`, `CLAUDE_CODE_USE_VERTEX`, `CLAUDE_CODE_USE_FOUNDRY`, or a non-default `ANTHROPIC_BASE_URL` |