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.221 ·

Org-memory write grants get stricter verdicts and new telemetry

Org memory now falls back to read-only when write permission is ambiguous, with new logging for why.

Under the hood Improvements
JSON All of v2.1.221
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.221,
ImprovementsSection of the release
What

The org-memory mount computes an explicit verdict before granting rw and clamps to ro whenever that verdict fails, with three new telemetry events recording why.

Details
  • mirrored or duplicate paths are rejected as "conflicted_mirror"
  • rw requires exactly one grouping root at depth 0 with mode rw, otherwise "verdict_failed"
  • private candidates are vetoed as "private_candidate_veto"
  • the org_memory_writes gate event now reports those reasons, tengu_org_memory_root_write_outcome records the outcome per mount, and tengu_org_memory_token_discarded fires when a stale token is dropped
  • all three event names are new in this build; the path is only reached for org-memory mounts
Evidence

tengu_org_memory_root_write_outcome

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

See this entry in the whole of v2.1.221 →

Feedback