Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

Safety-check prompts for dangerous removals now deny themselves after a timeout

Prompts for dangerous commands like rm in auto or bypass mode deny after 2 minutes by default and stop appearing after 3 unanswered

Group of 6 Nothing to try yet In Development
JSON All of v2.1.281
Nothing to try yetTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
PermissionsArea: what it touches
In DevelopmentKind: in v2.1.281,
What probably matters to youSection of the release

What

Some commands, such as dangerous removals with rm, trigger a safety check that asks you before running. This release adds a timer to those prompts and new handling in the auto and bypass permission modes.

  • The safety check behind dangerous removals, dangerousRemoval, is now marked autoModeDeny. In auto mode, or plan mode with auto active, such a check is treated as needing a person rather than something auto mode can approve.
  • Instead of falling back to a plain question, Claude Code either denies the command outright or shows a permission dialog with an auto-deny window (autoDenyWindow). If you do not answer before the window ends, the command is denied.
  • In bypassPermissions mode, the same checks can now show this timed dialog when an interactive dialog is available. Before, there was no dialog path. If showDialog is off or no dialog can be shown, the command is denied immediately.
  • After a set number of unanswered prompts in one session, Claude Code stops showing the dialog and denies straight away. The count resets when you allow or deny a prompt.
  • These prompts no longer offer an "always allow" rule when the reason cannot be approved automatically (suppressAlwaysAllowRule).
  • The behaviour is controlled by the server config tengu_splendid_horizon. Nothing has been read about that config for this release. Its built-in fallbacks are enabled: true, showDialog: true, timeoutMs: 120000 (2 minutes) and maxDialogTimeouts: 3.
  • The server can set the timeout between 5,000 and 3,600,000 milliseconds, and a value outside that range is not used as given. A server enabled value counts only when it arrives in the config payload.
  • Setting the environment variable CLAUDE_CODE_DISABLE_DANGEROUS_RM_TIMEOUT turns the feature off.

Why

A dangerous-command prompt in an unattended session no longer waits forever. It resolves to a deny, which is the safe outcome, and after three unanswered prompts the session stops asking. If you would rather such prompts wait for you indefinitely, set CLAUDE_CODE_DISABLE_DANGEROUS_RM_TIMEOUT.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what happens once `maxDialogTimeouts` is reached.
Anthropic's release notes agreeChanged the dangerous rm prompt in --dangerously-skip-permissions and auto mode to wait 2 minutes for an answer, then deny the command with…

See this entry in the whole of v2.1.281 →

Feedback