Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.309entry #31

Claude Code v2.1.309 ·

Hooks in some remote sessions can receive the session access token

In some remote sessions, command hooks can now be given CLAUDE_CODE_SESSION_ACCESS_TOKEN in their environment

You'll notice Notable Improvements
JSON All of v2.1.309
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
HooksArea: what it touches
ImprovementsKind: in v2.1.309,
What probably matters to youSection of the release

Unclear It is not confirmed that the token actually reaches hooks' environment in practice.

What

Hooks are your own commands that Claude Code runs at set moments, such as before a tool runs. In some remote sessions, Claude Code can now hand CLAUDE_CODE_SESSION_ACCESS_TOKEN to command hooks. This happens only when all of these hold:

  • CLAUDE_CODE_WORKER_EPOCH is 1.
  • A check on the host machine passes.
  • Neither project settings nor local settings are in use.

Claude Code also now marks a hook that runs synchronously when the same hook appears in the settings passed in on the command line for that event.

Why

This gives hooks access to a session token, which is worth knowing when you review what your hooks can see and do.

Read from
Names in the bundleCLAUDE_CODE_SESSION_ACCESS_TOKEN
What the documentation says
Documented inclaude-code/self-hosted-environments-configuration
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 doubtIt is not confirmed that the token actually reaches hooks' environment in practice.

See this entry in the whole of v2.1.309 →

Feedback