BullseyeUber — Bullseye Control

One install puts the whole Bullseye set in one tab. FleetView, BullseyeBacklog, DeepAgent, BullseyeSync and BullseyeNotify sit behind one tab-strip called Bullseye Control.

You drive all of it by talking to your AI (Claude Code, Codex or Copilot). There are no forms, no add-row button and no edit dialog: you say what you want, the AI does it through the members, and the tab is where you watch it happen.

🏆 The members, most important first

🆕 What's new since 17 Oct, biggest wins first

In Bullseye Control itself

Across the members, biggest first

Each member's own listing carries the full story. Earlier wins stay in force: FleetView's editor load fell from 82–86% to a measured 24% of a core, Uber starts even with an empty .obsolete file, a reload request is always answered, and the Reload button reloads at once.

Full per-version list: Release notes and CHANGELOG.

🤝 Why all of them under one umbrella

Each member works alone; hosted together they share one tab, one reload, one dialog and each other's data. What that buys, in the code today:

• 🎯🚢 A story and its agent on one screen. The Pair layout stacks the BullseyeBacklog board over the FleetView roster; the board's ▶🚢 Start agents press hands the stories to FleetView's queue, and a running-agent marker returns onto its board row.
• 🛟 One safe reload for the whole set. Every member carries the same reload coordinator, so one press parks each member's live work first; afterwards FleetView revives the killed subagents into their main's inbox.
• 🐳🚢 Keys and cost agree. FleetView's usage ledger files requests under the account that paid for them, and DeepAgent reads its subscription counts back from that ledger; an AI session can ask DeepAgent's provider_room how much room each Claude subscription has left before it picks an account.
• ⚡ A slow member holds nobody. Each member's tab opens the moment its own extension is ready — BullseyeSync can take most of a minute and the rest are already open.
• 🔔 One dialog. A question or alert from any member, including BullseyeNotify's, is drawn over whichever tab you are on.
• 🔄 Sync and notifications next to the work. BullseyeSync's status and BullseyeNotify's configuration are tabs beside the board and the fleet, and the Dashboard card shows each member's version and whether it is open here.
• 📦 One install. Installing the pack pulls in any member you are missing; each keeps its own listing and updates.

✨ At a glance

• 🎯 The whole set in one tab — FleetView, BullseyeBacklog, DeepAgent, BullseyeSync and BullseyeNotify as member tabs of one Bullseye Control editor tab.
• 🎛️ Dashboard — every member as a card, with its version, whether it is open here, and its web UI links.
• 🧩 Layouts — 1️⃣ One, ↕️ Stack, ↔️ Side, 🔀 Swap and the 🎯🚢 Pair preset that puts the board over the fleet.
• ⚡ One install pulls in what you are missing — each member keeps its own listing and updating; while Uber is enabled an installed member stands aside and runs here, never twice.
• ⏱️ Each member's tab opens the moment its own extension is ready — a slow member (BullseyeSync can take most of a minute) no longer holds the others on "Opening its page here…"; the tab also says what is happening instead of waiting silently, and nothing opens by itself at window start.
• 📦 Kept alive while hidden — each member's panel is drawn as its own tab would be, restyled to your theme, with scroll, filters and live updates surviving a switch.
• 🛡️ Always the newest installed member — Bullseye Control hosts the newest release VS Code has installed for each member (never the copy frozen when the pack was built), and skips a build VS Code has marked superseded.
• 🧱 One member failing never takes the rest down — a member that cannot start shows a ⛔ "did not start" card with the reason, and says so in the shared Bullseye dialog, never a VS Code error toast, while every other member keeps running; if Bullseye itself cannot start, the shared dialog's status item says why.
• ⌨️ Alt+0 Dashboard · Alt+1…5 a member · Alt+\ split on/off.

What to type

Copy any sentence into your AI chat. The screenshot beside it is what the tab shows afterwards.

1. One sentence, two members

File a P1 story: the 3.2 release notes are assembled from closed rows and open questions, then put an agent on it.

The 🎯🚢 Pair layout: the story is a row on the board above, its agent is a row on the fleet below, and the story number #419 appears in both.

2. Ask what can be reused

Which standby agent could take the 3.2 release notes instead of a fresh one?

The 1️⃣ One layout: FleetView full size. The Reuse column names each standby agent and the tokens it saves.

3. Two members side by side

Switch codex to my BYOK key and test it, and show me what the fleet is costing.

The ↔️ Side layout: DeepAgent's per-agent mode on the left, the fleet's token cost on the right.

4. Everything at a glance

What needs my attention across the Bullseye pack?

The 🎛️ Dashboard: a card per member with its version, whether it is open here, and its web UI links.

After the first screen

Open the tab with BullseyeUber: Open Bullseye Control, then tell your AI what you want about your repos, agents, keys, machines or notifications. The panels you are looking at are what your AI reads and writes, so the quickest way to learn them is to ask: "Show me everything open on the board", "Which agents are running and on which story?", "Is every machine in sync?".

The layout buttons only arrange what you see — they are the one thing you click rather than say:

The screenshots are renders of the shipped shell.js and shell.css in a headless browser, over invented members and data. The member panels inside them are those extensions' own listing renders, cropped to the pane — no real session, folder, host or name.

What it hosts

How the pack installs and hands over

BullseyeUber is an extension pack: installing it installs any of the five you do not have yet, and VS Code keeps each one updating on its own from its own listing. Every member that is installed — whether the pack brought it or you already had it — draws its editor panel as a tab in Bullseye Control instead of a tab of its own. Each member's page is drawn exactly as VS Code would draw it in a tab of its own, and stays alive while hidden, so switching away and back keeps its scroll position, filters and live updates. A member's sidebar views stay in the sidebar. A window reload puts back the tabs whose member restores its own tab after a reload.

A member whose own standalone extension is also installed is never started twice: that extension keeps its own tab, and the Dashboard card says which extension runs each member.

Commands and controls

BullseyeUber has no settings of its own; each member keeps its own.

Build

cd vscode-extension
npm install
npm run compile    # compile BullseyeUber and re-stage every member into build/
npm run package    # compile + stage + bullseye-uber-<version>.vsix
./release.sh --dry-run   # stage, then build the .vsix through the shared release chain; publishes nothing

Each member must already be built by its own build. Staging refuses a member whose sources are newer than its build; --member=<name>=<dir> stages a member from another checkout.

Release notes