Follow Discord
Sweep 01 Oct 2026 · 17:27Z Build v2.1.287 508 read Stable v2.1.285 Latest v2.1.287 Next v2.1.287 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.286 ·

Editor commands now share one check for being run inside a session

The skill, Chrome and worktree editor commands now use one shared check before refusing to run from inside a Claude Code session

Under the hood Internal Changes
JSON All of v2.1.286
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
CLIArea: what it touches
Internal ChangesKind: in v2.1.286,
Internal ChangesSection of the release
What

Three commands refuse to run from inside a Claude Code session: claude edit-skill-overrides, claude edit-chrome-settings and claude drop-worktree-registrations. Each used to test CLAUDE_CODE_CHILD_SESSION itself, an environment variable Claude Code sets in programs it starts. They now all ask one shared check and print the message it returns, if any.

claude drop-worktree-registrations still gives its own message: it cannot run from inside a Claude Code session because the VS Code extension runs it.

Why

The rule is now kept in one place for all three commands. Because the shared check decides on its own, the exact conditions for refusing may differ from the old single-variable test.

Read from
Names in the bundleclaude edit-skill-overridesclaude edit-chrome-settingsclaude drop-worktree-registrationsCLAUDE_CODE_CHILD_SESSION
What the documentation says
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 doubtWhether the shared check uses the same conditions as the old `CLAUDE_CODE_CHILD_SESSION` test is not established.

See this entry in the whole of v2.1.286 →

Feedback