Adding tools mid-conversation can still force a session reset, gated by an unread flag
When tools are added partway through a conversation, Claude Code's server-side continuation planner decides whether to keep using the same underlying thread or reset and start a new one. A new check now controls this: if a flag called tengu_lucid_anchor is off, adding tools mid-conversation still forces the thread to reset rather than continue.
This means whether tool additions can continue smoothly in the same thread, instead of forcing a reset, currently depends on this flag's setting.
tengu_lucid_anchor Not enough to sayNothing 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.268: off
Read once, for one account on one subscription tier, against v2.1.268. 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.
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.
Nothing has been read yet about how the `tengu_lucid_anchor` flag is set for any account, so it's unknown whether resets are currently being…
New in this build: tengu_lucid_anchor