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

Memory Write Confirmation [Gradual Rollout]

Entry
JSON All of v2.1.120
EntryKind: in v2.1.120,
Bug FixesSection of the release
What

The interactive approve/reject dialog for memory file writes.

Status

Feature-flagged behind tengu_slate_siskin (default false), with configurable timeout, throttle, and summary threshold.

Details
  • Full UI infrastructure is in place including diff rendering, AI-powered summaries, and undo capability
  • Configurable via the feature flag's schema: enabled, timeoutMs (1000-120000), throttleMs (0-3600000), summaryLineThreshold (1-50)
  • When enabled, every memory write surfaces a brief confirmation with countdown timer
Read from
Feature flag
tengu_slate_siskin Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.120: no gate table built for this version

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.120. 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 {"enabled":false,"summaryLineThreshold":5,"throttleMs":30000,"timeoutMs":8000} for tengu_slate_siskin, 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_slate_siskin, 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.120 →

Feedback