The remote bridge can report worktree state (dirty flags, unpushed commit count, submodules, LFS) alongside the current branch list, but only when the tengu_ccr_handoff_metadata gate is on, and its compiled fallback is false.
Evidence
[remote-bridge] worktree_state \u2192
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Read from
Feature flag
tengu_ccr_handoff_metadataOff by default, switched on for this account
The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.248: off
Flag reading movedThe flag server now returns on for tengu_ccr_handoff_metadata, 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 movedThe flag server now returns nothing at all, having stopped carrying it for tengu_ccr_handoff_metadata, 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.
