Follow Discord
Sweep 01 Oct 2026 · 17:27Z Build v2.1.287 508 read Stable v2.1.285 Latest v2.1.287 Next v2.1.287 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.287 ·

Admins can set CLAUDE_CODE_TRANSCRIPT_LOCAL_GC through managed policy

CLAUDE_CODE_TRANSCRIPT_LOCAL_GC, which turns on local transcript clean-up, is now accepted from managed policy settings

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

CLAUDE_CODE_TRANSCRIPT_LOCAL_GC turns on local garbage collection of transcripts, meaning automatic clean-up of the saved conversation records Claude Code keeps on your machine. This environment variable can now be supplied through managed policy settings, the settings an organization's administrator deploys to everyone's machines.

When neither the variable nor a remote switch turns it on, the clean-up is off. Setting the variable overrides that.

Why

Administrators can turn on transcript clean-up for their whole organization from policy instead of asking each person to set the variable.

Read from
Feature flag
tengu_transcript_local_gc Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.287: off

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.287. It isn't a statement about your account. What a flag value here can and cannot tell you

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 doubtAnother condition applies when the variable comes from policy, and it is not clear what that condition is or exactly what the clean-up…

See this entry in the whole of v2.1.287 →

Feedback