What
The claude auto-mode subcommands defaults, reset, config, and critique were being attached to the wrong internal command object, meaning they weren't properly registered under auto-mode. This has been fixed so they now work as expected.
Why
Before this fix, these subcommands could fail to run properly because of a plumbing mistake rather than any issue with what they were meant to do; now claude auto-mode defaults, reset, config, and critique work correctly.
Names in the bundleclaude auto-mode
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up claude auto-mode, on Configure auto mode.
`claude auto-mode defaults` prints three kinds of environment entry.auto-mode-config see the edit
Confirmed since
Anthropic's documentation has since written up auto-mode, on Customize Claude Tag.
| Auto mode allow rules | Actions pre-approved in a scope's sessions that Claude's permission checker would otherwise flag or stop | [Auto mode allow rules](#auto-mode-allow-rules) |claude-tag/admins/customize see the edit
Added since
A small documentation edit on Orchestrate subagents at scale with dynamic workflows touched a line naming auto-mode after this was published.
An `agent()` call resolves to `null` if you stop it mid-run or it hits an unrecoverable API error. In [auto mode](/docs/en/permission-modes#eliminate-prompts-with-auto-mode), the classifier can block an `agent()` call before the subagent s…workflows see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Orchestrate subagents at scale with dynamic workflows touched a line naming auto-mode after this was…