Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.318entry #21

Claude Code v2.1.318 ·

Ultrareview can write the session id of each launch to a file you choose

Setting CLAUDE_CODE_ULTRAREVIEW_LAUNCH_RECORD to a file path makes a successful ultrareview launch write its session id to that file

Use it now Notable No documentation found New Features
JSON All of v2.1.318
Use it nowTier: how much it should matter to you
5Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
UltrareviewArea: what it touches
New FeaturesKind: in v2.1.318,
What probably matters to youSection of the release
What

A new environment variable, CLAUDE_CODE_ULTRAREVIEW_LAUNCH_RECORD, holds a file path. An environment variable is a named value you set in your shell before starting a program. When it is set and an ultrareview launches successfully, Claude Code writes the launch's session id to that path. A session is one run of Claude Code with its own id.

  • The file is only created new. If a file already exists at that path, nothing is written.
  • The file is readable and writable only by your own user account.
  • If the write fails, Claude Code only logs ultrareview: no launch record written and the launch goes ahead.
  • While the variable is set, other output lines from the launch are indented.

Claude Code never sets this variable itself.

Why

A script or tool that starts an ultrareview can read the file to learn which session the review launched. When the variable is not set, nothing changes.

Read from
Names in the bundleCLAUDE_CODE_ULTRAREVIEW_LAUNCH_RECORD
How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_ULTRAREVIEW_LAUNCH_RECORD

See this entry in the whole of v2.1.318 →

Feedback