Pinned-memory scanning and injection are gated on tengu_stone_shell with a false fallback and suppressed by CLAUDE_COWORK_MEMORY_INDEX_CONTENT.
Memory files whose frontmatter carries pinned: true are injected so they apply to every session rather than only when retrieved.
- Pinned files are scanned, sorted by mtime, capped in count, and truncated when oversized
- Frontmatter documentation now describes the
pinnedfield - New one-shot telemetry event
tengu_memdir_pinned_injectedreports pinned_file_count, pinned_injected_count, pinned_injected_chars, truncated and malformed counts - New scan-failure paths log "memory_scan_readdir_failed" and "pin_scan_failed"
- Gated on
tengu_stone_shellwith fallback false, and suppressed entirely when CLAUDE_COWORK_MEMORY_INDEX_CONTENT is set
tengu_memdir_pinned_injected
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_stone_shell Off in both readingsThe 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.219: 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.219. It isn't a statement about your account. What a flag value here can and cannot tell you
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.
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.