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_DISABLE_DANGEROUS_RM_TIMEOUT

env in the build documented JSON

A Claude Code environment variable, read out of the shipped bundle. It has been in the build since v2.1.281, including the newest one read.

Set to 1 to turn off the time limit on critical-path removal prompts. In auto mode Claude Code then sends these removals to the classifier instead, and in bypassPermissions mode the prompt waits for your answer. Set it in the environment that launches Claude Code, since Claude Code ignores a copy delivered through a settings env block. Requires Claude Code v2.1.281 or later

Anthropic's own wording. Read off Environment variables, captured 2026-09-26.

First seen v2.1.281 23 Sep 2026
Last seen v2.1.283 25 Sep 2026
Builds3 / 126on this box, as of v2.1.283
Written about v2.1.281 first named in a changelog, 23 Sep 2026
v2.1.281in the build not in the build never minedv2.1.283

In the changelogs

3

Releases whose published page names CLAUDE_CODE_DISABLE_DANGEROUS_RM_TIMEOUT.

  1. v2.1.281
    Safety-check permission dialogs can now auto-deny after a timeout (new tengu_splendid_horizon config)

    Safety-check permission dialogs can now deny the request on their own if nobody answers before a timeout runs out

    found in this entry's text

  2. v2.1.281
    Auto-mode safety-check dialog now auto-denies on a timer (tengu_splendid_horizon)

    Auto-mode safety-check prompts can now deny the command on their own if left unanswered, with a cap after repeated timeouts

    found in this entry's text

  3. v2.1.281
    Destructive-command safety prompts now deny themselves after a timeout, and stop appearing after 3 unanswered

    Unanswered safety-check permission prompts now deny themselves after a timeout, and after 3 of them the check denies without asking

    found in this entry's text

First cited

1

The earliest release whose published evidence quoted CLAUDE_CODE_DISABLE_DANGEROUS_RM_TIMEOUT was v2.1.281, 23 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.28123 Sep 2026CLAUDE_CODE_DISABLE_DANGEROUS_RM_TIMEOUT

Presence across releases

1
BuildsHow manyDatesReading
v2.1.281 – v2.1.2833 builds23 Sep 2026 → 25 Sep 2026 ◆in the build

Build by build

3

One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.

BuildDateStateThe record behind it
v2.1.28123 Sep 2026·addedverdict: added · bool
v2.1.28224 Sep 2026·presentverdict: present · bool
v2.1.28325 Sep 2026·presentverdict: present · bool

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the environment variable does. All environment variables.

Feedback