tengu_haze_glass

A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.210, including the newest one read.

Releases whose published page names tengu_haze_glass.

1. v2.1.281 23 Sep 2026
   Memory 'tools' mode can now turn on while the org memory policy verdict is still loading

   Memory 'tools' mode can now start while the organization memory policy is still loading, instead of waiting for allow_memory_sync

   gate cited by this entry, found in this entry's text

2. v2.1.281 23 Sep 2026
   Org memory discovery can be 'held'

   Discovery of synced org memory gains a quiet 'held' state alongside open and closed

   gate cited by this entry, found in this entry's text

3. v2.1.238 20 Aug 2026
   The memory-tools gate was renamed, so everyone is back on file-based memory

   The memory-tools switch was renamed, resetting any rollout, so everyone is back on file-based memory.

   gate cited by this entry, found in this entry's text

4. v2.1.224 7 Aug 2026
   New memory_write tool for saving documents to a connected memory store

   Claude can now save documents into a connected memory store, with secret scanning blocking risky writes.

   gate cited by this entry, found in this entry's text

5. v2.1.224 7 Aug 2026
   Memory store listing gains each store's index path

   Listing memory stores can also report each store's index document path.

   gate cited by this entry, found in this entry's text

6. v2.1.224 7 Aug 2026
   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.

   gate cited by this entry, found in this entry's text

7. v2.1.224 7 Aug 2026
   Memory writes will require the version token from your last read

   Memory writes will need the version token from your last read, forcing a read before overwriting.

   gate cited by this entry, found in this entry's text

8. v2.1.223 5 Aug 2026
   Read-only org memory tools: memory_list and memory_read

   Two read-only tools let Claude browse and read org memory documents, but they stay disabled by default.

   gate cited by this entry, found in this entry's text

9. v2.1.223 5 Aug 2026
   Org-memory gating consolidated into one predicate

   Whether org memory loads is now decided in one place, driven by a kill-switch variable and a setting.

   gate cited by this entry, found in this entry's text

10. v2.1.219 24 Jul 2026
    Org memory no longer auto-selects a lone candidate store

    When only one org memory store is found, it is no longer picked for you automatically.

    gate cited by this entry, found in this entry's text

11. v2.1.219 24 Jul 2026
    Org memory: discovery telemetry and store-picker copy

    The memory store picker nudges you to pick a specific project instead of leaving the legacy default.

    gate cited by this entry, found in this entry's text

12. v2.1.219 24 Jul 2026
    Org-memory discovery can return a prompt_index path

    Org memory discovery can pick up a prompt index path from the server and attach it to the mount.

    gate cited by this entry, found in this entry's text

13. v2.1.213 17 Jul 2026
    Org Memory: Silo and Grouping Selection [Gradual Rollout]

    gate cited by this entry, found in this entry's text

14. v2.1.210 14 Jul 2026
    Memory Architecture: Org Memory Discovery Replaces Personal/Team Sync

    gate cited by this entry, found in this entry's text

Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.

One row per unbroken stretch of one reading, newest first, from snapshots taken every twenty-five minutes or so. No longer carried is not off: it means the flag server stopped returning the gate at all, which is what a retired experiment looks like. The version column is what was installed when the reading was taken, not what caused it.

The earliest release whose published evidence quoted tengu_haze_glass was v2.1.210, 14 Jul 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.