LakshmanTurlapati/FSB

Highlights

This release polishes the public Stats page, broadens the active users metric so installed extensions count even when idle, brings the chrome client name into the owner chip, and locks the chat input when a tab is being driven by an external agent. It also closes four P2 Codex review findings on the same code paths.

/stats page

The Average agents per user tab now renders a real chart inside the chart card. Previously a large headline number escaped the container and overlapped the footer. The chart shows a daily series of agents active divided by unique installs over the last thirty days.

The Issues tab Sankey labels now sit fully inside the diagram. The two outside the node labels were being clipped by the SVG viewBox edges. Nodes shifted inward symmetrically so Opened and Closed labels stay visible at any width.

The Commits and Cumulative commits tabs collapsed into a single Commits tab. The cumulative line is the more informative of the pair so it kept the slot and inherited the shorter label.

The page heading now reads Stats for nerds. The FSB prefix and the dot were dropped from the visible H1. The browser tab title still shows FSB plus Stats for share and tab brand context.

Active right now metric

Idle installed extensions are now counted as active. Previously the metric only counted installs that were currently running MCP agent sessions. With this release the telemetry collector emits a presence event on each five minute beat when there is no other activity to report, so an extension that is installed and connected to the server shows up as active even when no agent is running. A new guard suppresses the presence event when retry events are still pending in the queue, so the heartbeat never causes telemetry loss at queue cap.

Owner chip and chat input lock

When a tab is owned by an external agent, the chip in the popup and sidepanel header now reads owned by Claude or owned by Codex or whichever client is driving the tab. The chip previously showed a six character hex prefix of the internal agent id. The MCP client label is sourced from the same allowlist the telemetry server enforces.

The chat input is now locked while the chip is visible. Typing is disabled with a tooltip explaining the lock, and the send button is greyed out. The lock composes cleanly with the existing send button enable and disable logic, so the normal lifecycle is preserved when ownership is released. The popup now subscribes to storage changes so ownership flips while the popup is open are picked up live, matching the sidepanel.

Per agent client labels are now serialized through a promise chain mutex when written to chrome storage. Concurrent dispatches in hub mode no longer clobber each other, and a reconnect cannot resurrect a stale label even if a fire and forget write was already in flight.

Codex review

The four P2 findings raised by Codex on the original PR are all addressed in this release. The fixes cover the label storage race, the reconnect stale write window, the heartbeat backlog interaction, and the missing popup ownership listener.

Tests

The full CI suite is green on the merge commit. Telemetry collector coverage went from 105 to 116, owner chip coverage from 39 to 50, MCP dispatcher client label coverage from 45 to 51, and the wire payload internal fields test stays at 15. The MCP smoke and showcase build and crawler smoke jobs all pass.

Install

Drop the attached fsb-extension-v0.9.72.zip into chrome://extensions and load unpacked, or wait for the Chrome Web Store listing to roll the new version.