How I Built an Autonomous SRE War Room with Switch AI, OpenCode & Wispr Flow

When a production outage hits at 2 AM, every second counts. I built IncidentRoom — an autonomous SRE war room that turns any team chat channel into a self-coordinating incident response system using Switch AI.

Here's what actually happened during our live demo: a SEV-1 alert fired, three AI agents collaborated in a shared Mattermost room, identified the root cause commit in under 60 seconds, ran real bash commands to prepare a rollback, waited for a single human APPROVE command (voice-dictated via Wispr Flow), executed the fix, and auto-generated a full post-mortem — all in under 2 minutes.

Traditional incident response is chaotic:

MTTR (Mean Time to Resolution) suffers not because engineers are slow — but because coordination is broken.

Switch is an open-source platform that connects AI coding agents (Claude Code, Codex, OpenCode, Cursor, Antigravity) into team chat channels as first-class participants. Agents can read messages, respond to @mentions, run bash commands, hand off context to each other, and await human approval — all inside Mattermost, Slack, Teams, or Discord.

This is the missing piece for incident response.

📢 Alert fires in #incident-war-room │ ▼ @triage-agent ──→ 11 tool calls ──→ Root cause: commit 8f2b31a │ ▼ HANDOFF @sre-agent ──→ npm pack stripe@3.4.0 ──→ "Awaiting APPROVE" │ ▼ Human: "APPROVE" (via Wispr Flow voice) @sre-agent ──→ Rollback executed ✅ │ ▼ @comms-agent ──→ Post-mortem generated 📄 Enter fullscreen mode Exit fullscreen mode The Three Agents @triage-agent — The Incident Detective

Receives the alert via @mention, parses the stack trace, correlates against recent git commits, and isolates the root cause. In our live demo:

triage-agent BOT · Worked for 3m 16s. 11 tool calls. 🔍 TRIAGE — root cause identified: commit 8f2b31a ("feat(payments): upgrade stripe sdk v3.4") Root cause: services/payments/stripe_gateway.js:84 passes a null options object to the Stripe create call; stripe-node v3.4 now unconditionally reads options.idempotency_key, so createSession throws before reaching Stripe. Enter fullscreen mode Exit fullscreen mode @sre-agent — The Remediation Specialist

Receives the handoff, evaluates blast radius, executes real bash commands to prepare the rollback — but never deploys without human approval:

# Actual command run by @sre-agent npm pack stripe@3.4.0 --pack-destination /tmp/opencode/stripe340 Enter fullscreen mode Exit fullscreen mode Then waits. No autonomous deployment. Human-in-the-loop is non-negotiable.

@comms-agent — The Incident Commander & Scribe

Handles stakeholder communication and auto-generates the post-mortem with MTTR, timeline, root cause, and action items.

Here's the detail that makes this truly hands-free: I used Wispr Flow to voice-dictate every incident command without touching the keyboard.

"Alert: Save one HTTP 500 error spike in checkout payment gateway at triage agent. Please investigate the root cause. Commit. Approve, roll back, and notify all stakeholders. @Comms agent generate the postmortem report."

Wispr Flow transcribed this at 100 wpm, 405 total words across the incident session. That's the entire incident — triage, approval, and post-mortem command — dictated hands-free.

Building this, I learned from the community:

The key insight both posts validate: agents need approval gates before any write operation in production. We enforced this strictly — @sre-agent never executes a deployment without an explicit human APPROVE in the room.

git clone https://github.com/swatiicfai/IncidentRoom cd IncidentRoom cp.env.example.env # Add your Switch server URL npm install node src/simulate.js # Trigger a live SEV-1 simulation Enter fullscreen mode Exit fullscreen mode You need:

Built for the Flip the Switch Hackathon by WeMakeDevs × Switch AI.

This post was written with AI assistance (Antigravity/Gemini) during the hackathon session.