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

Claude Code v2.1.318 ·

New CLAUDE_CODE_PROGRAM_USE_CASE_STAMPED variable for programs that launch Claude Code

Claude Code now reads CLAUDE_CODE_PROGRAM_USE_CASE_STAMPED, which a launching program can set; the value follow picks a separate way of working out the use case

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
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ConfigurationArea: what it touches
New FeaturesKind: in v2.1.318,
What probably matters to youSection of the release

Unclear It is not stated what the program use case controls, so the effect of setting the variable is unknown.

What

Claude Code now reads an environment variable called CLAUDE_CODE_PROGRAM_USE_CASE_STAMPED. Claude Code never sets it itself. It is meant to be set by whatever program starts Claude Code, and it is passed through to processes Claude Code starts.

  • follow: Claude Code works out the program's use case in a different way
  • any other non-empty value: the use case counts as already stamped
Why

This appears to be the plumbing that lets a program running Claude Code pass a use-case label down to the processes it starts. It only matters if the program that starts Claude Code sets the variable. Ordinary use is unaffected.

Read from
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 stated what the program use case controls, so the effect of setting the variable is unknown.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_PROGRAM_USE_CASE_STAMPED

See this entry in the whole of v2.1.318 →

Feedback