Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.224 ·

Memory writes are scanned for secrets before they land

Memory writes get scanned for secrets and refused, naming what matched and that the store is shared.

Nothing to try yet In Development
JSON All of v2.1.224
Nothing to try yetTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
MemoryArea: what it touches
In DevelopmentKind: in v2.1.224,
What probably matters to youSection of the release

Secret scanning on memory writes is behind a gate that is false in this build.

What

Memory document content is scanned before it is written, and a match refuses the write with a message naming what matched and noting that the store is shared with everyone on the project. The tool's own instructions carry the same rule. Behind tengu_haze_glass, which is false in this build.

Evidence

Never write secrets or credentials into a memory \u2014 the store is shared with every collaborator on the project, and such writes are refused.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Feature flag
tengu_haze_glass Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.224: 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.224. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns off for tengu_haze_glass, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_haze_glass, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.224 →

Feedback