Skip to content
| Marketplace
Sign in
Visual Studio Code>Visualization>Guild Mission ControlNew to Visual Studio Code? Get it now.
Guild Mission Control

Guild Mission Control

Seawolf AI

|
2 installs
| (0) | Free
Single-pane-of-glass Mission Control for the Guild.ai agent platform — agents, sessions, triggers, activity, and a connection map.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Guild Mission Control

A VS Code extension that is a single pane of glass for the Guild.ai agent platform — see your entire universe of workspaces at a glance, drill into any agent to understand what it's doing, and put a number on the ROI.

Built entirely on the Guild CLI (guild … --mode json): no extra services, no API keys beyond your existing guild auth login.

What you get

🌌 Universe view (the landing page)

One card per workspace across your whole account: running/error badges, recent-session counts, and 7-day activity sparklines. Workspaces that are quietly burning failed runs show up red before anyone thinks to look. Click a card to drill in.

📊 Workspace dashboard

  • Agent grid with live-session indicators, per-agent 7-day run sparklines, and search.
  • Activity feed of recent sessions — click through to a full session timeline.
  • Flows — one row per agent that reads as a sentence: what triggers it → the agent → what it produced (runs/errors over 7 days, sparkline, last run status). Dormant agents are visibly dormant.
  • Failing-trigger detection — a schedule whose recent runs all errored gets a red banner with one-click deactivate, plus a status-bar warning.

🔍 Session detail

Event-type-aware timeline (user / trigger / agent / runtime / LLM / console / error rows, each in its own visual language), live tail while a session runs, an in-panel composer to message the session, interrupt button, and raw JSON for debugging.

🤖 Agent detail

Versions with validation status, build logs, "latest run in the agent's own words" (statuses can say DONE while the agent said REJECTED — the message is the truth), an hour-of-week activity heatmap, systems the agent touches (reads vs. writes per integration), recent sessions, and run stats.

💰 ROI

Give any agent a value model — minutes of human work saved per successful run — and get:

  • an ROI card on the agent (hours + dollars over 30 days, at your configurable hourly rate),
  • a universe-level rollup (total savings, top agents),
  • Guild: Export ROI Report — a shareable markdown table.

Session history is backfilled across all workspaces on startup, so the numbers reflect what actually ran — not just what VS Code happened to observe. Token cost has a reserved slot for when the platform starts reporting token_usage.

Agents that end their final message with a fenced ```guild-metrics block (one flat JSON object of business counters) get business-impact tiles: aggregated metrics on the agent detail page, impact chips in the universe ROI rollup, and a Business impact section in the exported ROI report.

🛠 Act, don't just observe

Re-run a finished session with its original input, Debug with AI (assembles the failure context into a prompt for your editor's AI chat), diagnose failed sessions by clustering shared error reasons, and get alerted on missed schedules (a trigger that silently stopped firing) and week-over-week success-rate regressions.

✍️ The authoring inner loop

Clone any agent with full git history (VS Code's native timeline/diff views show version changes), run it once with a prompt, then save & publish a new version — all without leaving the editor. Pin ★ / hide ✕ workspaces to curate a large universe, and a native getting-started walkthrough onboards new users.

🔔 Live operations

Adaptive polling (3s while sessions run, configurable at rest), completion/failure notifications that include the failure reason, Guild: N running status-bar item, workspace picker, and an onboarding flow when the CLI is missing or logged out.

Install

Install Guild Mission Control from the VS Code Marketplace (search guild-mission-control, publisher SeawolfAI), or:

code --install-extension seawolfai.guild-mission-control

Prefer a specific build? Grab the .vsix from Releases and:

code --install-extension guild-mission-control-<version>.vsix

Prerequisites: the Guild CLI on your PATH (or set guild.cliPath) and guild auth login completed.

Settings

Setting Default Description
guild.cliPath "guild" Path to the Guild CLI executable.
guild.workspace "" Workspace identifier (UUID or owner~name). Empty = the CLI's default.
guild.pollIntervalSeconds 15 Auto-refresh interval. 0 = manual only. Polls at 3s while sessions run. The status bar shows a stale warning when the last refresh is older than twice this interval.
guild.notifyMode "failures" Which session outcomes raise a notification: failures (with the failure reason), all (every finish and failure), or none.
guild.watchAgents [] Only notify for these agents (full owner~name or bare name). Empty = all agents.
guild.notifyOnSessionEnd true Deprecated alias for guild.notifyMode — false → none, true → all. Ignored when notifyMode is set.
guild.valueHourlyRate 75 $/hr used to convert modeled time savings into dollar ROI.
guild.roiImpactMetrics [] guild-metrics keys to headline as business-impact chips in the universe ROI rollup (first two present are shown). Empty = the two largest numeric metrics that are not runs_* counters.
guild.debugAiTool "auto" Where Debug with AI sends the prompt: auto, claude, codex, builtin-chat, clipboard, or custom. Always also copied to the clipboard.
guild.debugAiCommand "" Shell command for debugAiTool: "custom" — {prompt} is replaced with the quoted debug prompt.
guild.openDashboardOnStartup "firstRun" When to open the dashboard automatically: always, firstRun (once, tracked per install), or never. The legacy booleans true/false still work as always/never.
guild.backfillHistory true Backfill session history across all workspaces on startup so stats and ROI include runs that happened while VS Code was closed. Guild: Backfill Session History Now re-runs it on demand.

Build from source

npm install
npm run compile     # typecheck + esbuild bundle
npm test            # pure-logic unit tests (node --test)
npm run package     # produce the .vsix

Press F5 with this folder open to launch an Extension Development Host. CI runs typecheck/tests/build on every push; tagging v* publishes a GitHub Release with the packaged .vsix.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft