{"version":"2.1.280","anchor":"code-sign-now-supports-lifecycle-hook-processes-not-just-sp","canonical_anchor":"code-sign-now-supports-lifecycle-hook-processes-not-just-sp","heading":"code-sign now supports lifecycle-hook processes, not just spawned child sessions","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/code-sign-now-supports-lifecycle-hook-processes-not-just-sp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### code-sign now supports lifecycle-hook processes, not just spawned child sessions\n\nCode-signing now also recognizes lifecycle-hook processes, not just spawned sessions\n\n**What**\n\nClaude Code's code-signing helper, which previously identified eligible processes by reading `CLAUDE_CODE_REMOTE_SESSION_ID`, `CLAUDE_CODE_SESSION_ACCESS_TOKEN`, and `ANTHROPIC_BASE_URL`, now also accepts `CLAUDE_RUNNER_SESSION_ID` and `CLAUDE_RUNNER_API_BASE_URL`, the environment variables used by lifecycle hooks (scripts that run automatically at points in a session's life). When it finds a `CLAUDE_RUNNER_SESSION_ID` prefixed with `session_`, it converts that prefix to `cse_` to match the expected format.\n\n**Why**\n\nThis widens which processes are eligible for code signing to include lifecycle-hook processes, not just spawned child sessions.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}