{"version":"2.1.304","anchor":"whiteboard-variant-latch-replaced-by-tengu-harp-pedal-gate","canonical_anchor":"whiteboard-variant-latch-replaced-by-tengu-harp-pedal-gate","heading":"Whiteboard behaviour is now set by one remote switch","tier":"internal","area":"Whiteboard","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/whiteboard-variant-latch-replaced-by-tengu-harp-pedal-gate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Whiteboard behaviour is now set by one remote switch\n\nThe whiteboard no longer picks a live or solo mode per session and instead follows a single switch controlled remotely\n\n**Unclear.** It is not clear what the whiteboard does differently for a user when this switch is on or off.\n\n**What**\n\nClaude Code used to choose a whiteboard mode, either \"live\" or \"solo\", once per session based on two local checks. It now reads a single switch, `tengu_harp_pedal`, that the server controls.\n\nIn this release's code, the switch counts as on unless the server sends a value turning it off.\n\n**Why**\n\nThe whiteboard's behaviour is no longer settled locally for each session. It can be turned off remotely, like a kill switch.\n\n- Flag `tengu_harp_pedal`: Not enough to say (read for one account on one subscription tier against v2.1.304; this account: no value returned, anonymous baseline: no value returned, compiled default: on) 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.\n- Area: Whiteboard\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}