Code / incident-commander

incident-commander

TypeScript · 116 files · main @ d215677

Files

  • .github/workflows/
  • src/
  • worker/
  • .env.example
  • .eslintrc.cjs
  • .gitignore
  • .mcp.json
  • .prettierignore
  • .prettierrc
  • .yarnrc.yml
  • components.json
  • next-env.d.ts
  • next.config.ts
  • open-next.config.ts
  • package.json
  • postcss.config.mjs
  • README.md
  • tsconfig.json
  • wrangler.jsonc

README

Incident Commander

AI-assisted production incident investigation built on Cloudflare Agents.

Stack

  • Next.js 15 App Router + React 19
  • Yarn 4
  • Tailwind CSS 4 + shadcn/ui
  • Agent Elements for the chat surface
  • Cloudflare Workers + Agents SDK
  • AIChatAgent + useAgentChat
  • Workers AI using Llama 3.3 70B Instruct
  • Cloudflare Workflows
  • Durable Objects + SQLite
  • Zod + AI SDK

The web UI and the agent Worker are intentionally separate processes. Next.js remains a normal Next application, while the agent Worker owns realtime WebSocket chat, Durable Object state, SQLite memory, Workers AI and Workflows.

Development

corepack enable
yarn install
yarn dev

This starts Next.js on port 3000 and the agent Worker on port 8787. Copy .env.example to .env.local if you need to override the agent host.

Useful commands:

yarn format
yarn lint
yarn typecheck
yarn build
yarn build:agent
yarn check

Agent Elements

The project is shadcn-initialised and checks in Agent Elements as source under src/components/agent-elements.

A project-scoped Agent Elements MCP server is also configured in .mcp.json. Claude Code will ask for approval the first time the project-scoped server is used.

To refresh the chat component manually:

yarn ui:agent-chat

Architecture

Next.js / Agent Elements
        |
        | WebSocket
        v
IncidentCommanderAgent
  |-- Workers AI / Llama 3.3
  |-- tool calls
  |-- Durable Object state
  |-- SQLite memory
  |
  `-- IncidentInvestigationWorkflow
        |-- triage
        |-- deployments
        |-- dependencies
        |-- logs
        |-- hypothesis
        `-- recommendation

The initial telemetry provider is deterministic mock infrastructure so the demo remains repeatable. Real observability providers can replace that boundary later without changing the Agent or UI contracts.