Claude Code v2.1.286 · 30 Sep 2026
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 Tier: how much it should matter to you
2 Useful: my rating, 1 to 5
3 Signal: worth watching, 1 to 5
CLI Area: what it touches
Internal Changes Kind: in v2.1.286, 30 Sep 26
Internal Changes Section 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 bundle claude edit-skill-overrides claude edit-chrome-settings claude drop-worktree-registrations CLAUDE_CODE_CHILD_SESSION
What the documentation says
How sure we are
Something disagrees Something we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt Whether 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 →
30 Sep 2026 · 290 entries, this one is #210.
Use it now22 You'll notice162 Nothing to try yet19 Under the hood87
Open the release →
Names in this entry
cli edit-skill-overrides Three new hidden CLI commands let the VS Code extension edit skill, sandbox, and Chrome settings
cli edit-chrome-settings Three new hidden CLI commands let the VS Code extension edit skill, sandbox, and Chrome settings
cli drop-worktree-registrations A hidden claude drop-worktree-registrations command, used by the VS Code extension, removes git's records of deleted worktrees
env CLAUDE_CODE_CHILD_SESSION Set to 1 in subprocesses Claude Code spawns via the Bash, PowerShell, and Monitor tools, hook commands, and status line commands. Not set for stdio MCP server subprocesses, which are long-lived and outlive the session that spawned them. Unlike CLAUDECODE, this is only set by Claude Code itself when it launches a subprocess and not by IDE extensions, so it reliably distinguishes a nested session from a top-level claude launched in an IDE-integrated terminal. A nested interactive claude TUI started this way is automatically excluded from --resume, --continue, up-arrow history, and the claude agents list. Non-interactive claude -p sessions still persist. Set CLAUDE_CODE_FORCE_SESSION_PERSISTENCE=1 to override this exclusion. Requires Claude Code v2.1.172 or later
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 209 of 290
New "relayed" label for approvals passed on from another session
Under the hood Permissions
In v2.1.286 Internal Changes release-page order
Next → · 211 of 290
MCP server connections gain dial-in options, and blocked-server refusal honors a new…
Under the hood MCP