1 ファイル変更+31-3
この更新の概要
オートモードの動作を決定する分類器（Classifier）に関連するエラーメッセージと対処法が追加されました。具体的には安全性の判断ができなかった場合や、コンテキストウィンドウを超過した場合の挙動が詳しく説明されています。インタラクティブセッションでは手動承認へのフォールバックが発生することや、非インタラクティブモードでは実行が中断される仕様が明記されました。エラー解決のためのdebugフラグの使用やcompactコマンドによる履歴圧縮についても言及されています。
オートモードの分類器が過負荷やコンテキスト不足で判断できない際のエラーメッセージとその具体的な解決策が追記されました。また、読み取りや検索などのディレクトリ内操作は分類器を介さず継続可能であるという制限事項の詳細が更新されています。
@@ -23,6 +23,8 @@ Match the message you see in your terminal to a section below.
| `API Error: Repeated 529 Overloaded errors` | [Server errors](#api-error-repeated-529-overloaded-errors) |
| `Request timed out` | [Server errors](#request-timed-out), or [Network](#unable-to-connect-to-api) if the message mentions your internet connection |
| `<model> is temporarily unavailable, so auto mode cannot determine the safety of...` | [Server errors](#auto-mode-cannot-determine-the-safety-of-an-action) |
| `Auto mode could not evaluate this action and is blocking it for safety` | [Server errors](#auto-mode-cannot-determine-the-safety-of-an-action) |
| `Auto mode classifier transcript exceeded context window` | [Server errors](#auto-mode-cannot-determine-the-safety-of-an-action) |
| `You've hit your session limit` / `You've hit your weekly limit` | [Usage limits](#youve-hit-your-session-limit) |
| `Server is temporarily limiting requests` | [Usage limits](#server-is-temporarily-limiting-requests) |
| `Request rejected (429)` | [Usage limits](#request-rejected-429) |
@@ -115,20 +117,46 @@ This can happen during periods of high load or when a very large response is bei
### Auto mode cannot determine the safety of an action
The model that [auto mode](/en/permission-modes#eliminate-prompts-with-auto-mode) uses to classify actions is overloaded, so auto mode blocked the action instead of approving it unchecked.
The model that [auto mode](/en/permission-modes#eliminate-prompts-with-auto-mode) uses to classify actions could not produce a decision, so auto mode did not approve the action automatically. The message you see depends on why the classifier failed.
Reads, searches, and edits inside your working directory skip the classifier, so they keep working in all of these cases.
When the classifier model is overloaded:
```text
<model> is temporarily unavailable, so auto mode cannot determine the safety of <tool> right now. Wait briefly and then try this action again.
```
Reads, searches, and edits inside your working directory skip the classifier, so they keep working during the outage.
**What to do:**
- Retry after a few seconds; Claude sees the same message and usually retries on its own
- If retries keep failing, continue with read-only tasks and come back to the blocked action later
- This is transient and unrelated to [auto mode eligibility](/en/permission-modes#eliminate-prompts-with-auto-mode); you do not need to change settings
When the classifier returned an unparseable response:
```text
Auto mode could not evaluate this action and is blocking it for safety — run with --debug for details
```
**What to do:**
- Retry the action; this usually succeeds on the next attempt
- Run `claude --debug` and repeat the action to see the underlying classifier response in the debug log
When the conversation has grown larger than the classifier's context window:
```text
Auto mode classifier transcript exceeded context window — falling back to manual approval (try /compact to reduce conversation size)
```
In an interactive session, auto mode falls back to a normal permission prompt for that action so you can approve or deny it manually. In [non-interactive mode](/en/headless) the run aborts because the transcript only grows and retrying cannot succeed.
**What to do:**
- Approve or deny the action in the prompt that appears
- Run `/compact` to reduce the conversation size so subsequent actions fit within the classifier window again
## Usage limits
These errors mean a quota tied to your account or plan has been reached. They are distinct from [server errors](#server-errors), which affect everyone.