20-person Windows pilot

BIS Mission Control

Install the VS Code extension, join a team room, launch local Claude or Codex sessions, and keep the team's work visible without pasting terminal transcripts into chat.

Version
0.4.0
Package
bis-gastown-extension-0.4.0.vsix
Verification
959aa26ecaf7...
VS Code
# team-room 3

Sam spawned a Codex agent in production.

Mission Control split onboarding API work from report cleanup.

AgentsTasksApprovalsLive agents

First install

Three steps for testers

  1. Download the VSIX.Open VS Code, choose Extensions, then Install from VSIX.
  2. Sign in with BIS email.Use the code sent to your inbox, then create or join your team room.
  3. Launch agents from Mission Control.Claude and Codex sessions open as visible VS Code terminals and stream summarized activity to the room.

Product tour

What opens after install

01

Account

Send a BIS email code, verify it, and keep your display name attached to every room event.

02

Team room

Create a team or paste an invite. Each team gets one room and one shared project memory.

03

BIS context

Point to the production repo once. Mission Control indexes code and the knowledge base for spawned agents.

04

Agents

Launch Claude or Codex locally. Teammates see a read-only live card, not a noisy raw transcript.

05

Tasks

The orchestrator turns agent progress into tasks, blockers, decisions, and suggested Linear updates.

06

Approvals

When an agent needs human approval, the team sees it in one place before work continues.

Pilot updates

No repeat scripts after install

Side-loaded extensions do not get native Marketplace auto-updates. This pilot build checks https://bis-mission-control-download.pages.dev/releases/latest.json from inside VS Code and shows an automatic Update prompt plus a dashboard Update button when a newer hash-verified VSIX is available.

Operator fallback script

Normal testers update from inside VS Code. The fallback script is only for first-install recovery or operator troubleshooting.