{"version":"2.1.287","anchor":"claude-code-transcript-local-gc-can-be-set-from-managed-poli","canonical_anchor":"claude-code-transcript-local-gc-can-be-set-from-managed-poli","heading":"Admins can set CLAUDE_CODE_TRANSCRIPT_LOCAL_GC through managed policy","tier":"use","area":"Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/claude-code-transcript-local-gc-can-be-set-from-managed-poli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Admins can set `CLAUDE_CODE_TRANSCRIPT_LOCAL_GC` through managed policy\n\n`CLAUDE_CODE_TRANSCRIPT_LOCAL_GC`, which turns on local transcript clean-up, is now accepted from managed policy settings\n\n**Unclear.** Another condition applies when the variable comes from policy, and it is not clear what that condition is or exactly what the clean-up deletes.\n\n**What**\n\n`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.\n\nWhen neither the variable nor a remote switch turns it on, the clean-up is off. Setting the variable overrides that.\n\n**Why**\n\nAdministrators can turn on transcript clean-up for their whole organization from policy instead of asking each person to set the variable.\n\n- Flag `tengu_transcript_local_gc`: Not enough to say (read for one account on one subscription tier against v2.1.287; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Settings\n- Names: `CLAUDE_CODE_TRANSCRIPT_LOCAL_GC`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}