{"version":"2.1.268","anchor":"tool-additions-mid-conversation-tether-reset-gated-by-tengu","canonical_anchor":"tool-additions-mid-conversation-tether-reset-gated-by-tengu","heading":"Tool-additions mid-conversation tether reset gated by tengu_lucid_anchor","tier":"soon","area":"Conversation Threading","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/tool-additions-mid-conversation-tether-reset-gated-by-tengu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Tool-additions mid-conversation tether reset gated by tengu_lucid_anchor\n\nAdding tools mid-conversation can still force a session reset, gated by an unread flag\n\n**Unclear.** 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 forced or avoided.\n\n**What**\n\nWhen 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.\n\n**Why**\n\nThis means whether tool additions can continue smoothly in the same thread, instead of forcing a reset, currently depends on this flag's setting.\n\n- Flag `tengu_lucid_anchor`: Not enough to say (read for one account on one subscription tier against v2.1.268; this account: no value returned, anonymous baseline: no value returned, compiled default: off)\n- Area: Conversation Threading\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}