{"version":"2.1.268","anchor":"bridge-indicator-reworked-to-carry-an-explicit-status-not-j","canonical_anchor":"bridge-indicator-reworked-to-carry-an-explicit-status-not-j","heading":"Bridge status indicator now carries an explicit status instead of a boolean","tier":"notice","area":"Status Bar","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/bridge-indicator-reworked-to-carry-an-explicit-status-not-j","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Bridge status indicator now carries an explicit status instead of a boolean\n\nThe footer's bridge indicator now shows a real status value instead of just on or off\n\n**Unclear.** What specific status values the indicator can now show, beyond the previous boolean, is not specified.\n\n**What**\n\n- The status\/footer line's bridge indicator used to render only when a column-width\/boolean gate was true, passing just a `bridgeSelected` flag. Now it always computes a status value and renders the bridge chip whenever that status isn't null, passing a `status` field to the bridge component instead of gating on column width.\n\n- As part of this, the status-line render function no longer destructures `ideSelection` or `mcpClients` from its props, and no longer computes or renders an IDE-colored badge.\n\n**Why** This makes the bridge indicator reflect a real connection status rather than a simple on\/off flag, though it also means the footer no longer shows a separate IDE badge.\n\n- Area: Status Bar\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}