When auto mode's classifier errors, a debug dump lands beside your transcript and gets cleaned up later.
What's wrong with this entry?
When the classifier behind auto mode errors, Claude Code now writes a diagnostic file next to the session transcript capturing what it was asked to classify, and the normal session cleanup sweep deletes those files on the usual retention schedule so they do not accumulate. This gives you something concrete to attach to a bug report about a misclassified action without leaving debris in the transcript directory.
- The dump is written to
auto-mode-classifier-error.txtin the session's transcript directory, owner-readable only. - It contains the system prompt, the transcript prompt, the error itself, and a context comparison section covering token counts, message counts and the action being classified.
- Nothing is written when session persistence is off, including when
CLAUDE_CODE_SKIP_PROMPT_HISTORYis set, so on those setups the dump never appears. - The per-session cleanup sweep now removes
auto-mode-classifier-error.txtand any file namedauto-mode-dump.*.json, including partially written.json.tmp.staging files, alongside theccr-tip.jsonandprecompact.jsonfiles it already handled. - That cleanup runs unconditionally under the existing
cleanupPeriodDaysretention setting, with no separate switch for the auto-mode files.
=== CONTEXT COMPARISON ===, auto-mode-classifier-error.txt
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
Auto mode exit message is tailored, and subagents no longer get it
Both mention auto mode
-
v2.1.229
Auto-mode setup confirmation is now a single keyboard form
Both mention auto mode
-
v2.1.229
Auto-mode setup wizard reduced to one screen
Both mention auto mode