{"version":"2.1.286","anchor":"skillchromeworktree-editor-clis-share-a-session-guard","canonical_anchor":"skillchromeworktree-editor-clis-share-a-session-guard","heading":"Editor commands now share one check for being run inside a session","tier":"internal","area":"CLI","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/skillchromeworktree-editor-clis-share-a-session-guard","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Editor commands now share one check for being run inside a session\n\nThe skill, Chrome and worktree editor commands now use one shared check before refusing to run from inside a Claude Code session\n\n**Unclear.** Whether the shared check uses the same conditions as the old `CLAUDE_CODE_CHILD_SESSION` test is not established.\n\n**What**\n\nThree 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.\n\n`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.\n\n**Why**\n\nThe 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.\n\n- Area: CLI\n- Names: `claude edit-skill-overrides`, `claude edit-chrome-settings`, `claude drop-worktree-registrations`, `CLAUDE_CODE_CHILD_SESSION`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}