{"version":"2.1.248","anchor":"worktree-state-reporting-to-the-remote-bridge-stays-off","canonical_anchor":"worktree-state-reporting-to-the-remote-bridge-stays-off","heading":"Worktree state reporting to the remote bridge stays off","tier":"soon","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/worktree-state-reporting-to-the-remote-bridge-stays-off","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Worktree state reporting to the remote bridge stays off\n\nReporting worktree dirtiness and unpushed commits to the remote bridge stays off.\n\n**What**\n\nThe 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.\n\n**Evidence**\n\n`[remote-bridge] worktree_state \\u2192 `\n\n- Flag `tengu_ccr_handoff_metadata`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.248; this account: on, anonymous baseline: on, compiled default: off)\n- Area: Sessions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}