agent-kontrol

Agent Kontrol

Agent Kontrol™ by The AIE Network™

One dashboard for the AI coding agents you run: Claude Code, Codex, Grok, Hermes and anything that speaks MCP. See what each is doing, queue work for them, and check whether the backlog is actually shrinking.

curl -fsSL https://raw.githubusercontent.com/mrhinkle/agent-kontrol/main/scripts/quickstart.sh | bash

That starts Agent Kontrol with Docker Compose (or in demo mode on Node 20+ if you have no Docker). Other targets: Vercel with Neon or any Postgres, Fly.io, any Node host. See docs/DEPLOY.md.

What it does

• Fleet view. Live status and history for every agent, from deterministic hooks and watchers, not from the agents remembering to report.
• Task queue. Queue work for any platform; a per-machine dispatcher runs it headless and reports result and cost. Optional cross-vendor review by a second platform.
• Progress board. Net backlog (issues opened minus closed) per repo over time, because a day with many merges can still leave the backlog deeper. Choose the repos in Settings; no redeploy.
• MCP server. Any MCP host can report status, read the fleet, check messages from you and claim tasks. OAuth 2.1 for hosts that support it, or a bearer token.
• Messaging. Send an agent a message from the dashboard; it sees it when it polls and can reply.
• Traces. Step-by-step spans for each agent session, shown as a waterfall. OpenTelemetry-compatible, so any exporter can send to it; the Claude Code hook emits them automatically.
• Usage and Costs (experimental). Paid and included-token cost per account.
• Notes. A small shared table agents can write to and search (substring search). A short structured note (who, where, how long, outcome, tool counts) is written automatically when any agent's session ends, so the next agent can see who worked where.

Claude Code hooks ──┐
Codex watcher ──────┤  POST /api/ingest          ┌──> Dashboard (Fleet / Tasks / Progress / History / Memory)
Grok / dispatcher ──┤──────────────> Postgres ───┤
Cowork cloud ───────┤  MCP /api/mcp              └──> get_fleet_status / recall / claim_task
Hermes ─────────────┘

Tasks page / create_task ──> queue ──> dispatcher (per machine) ──> claude -p | codex exec | grok -p

Agents push; nothing polls vendors. No vendor exposes a "what are my agents doing" API, so every agent reports into a store you own.

Connect your agents

Agent	How	Guide
Claude Code / Cowork (local)	lifecycle hooks	agents/claude-code
Claude Cowork (cloud)	MCP connector with OAuth	agents/cowork-cloud
Codex / ChatGPT Work	session watcher	agents/codex
Grok	dispatcher and MCP	agents/grok
Hermes	MCP and cron heartbeat	agents/hermes
Any machine	dispatcher (runs queued tasks)	agents/dispatcher

Full matrix: docs/AGENTS.md.

Status

Agent Kontrol is in 1.0 beta (release notes). The API, MCP tool surface and schema are meant to stay stable through 1.0; please report anything that breaks them. Experimental: Usage and Costs, and the Notes store (a pluggable memory backend is planned for 1.1). Not yet built: forwarding traces to other OpenTelemetry backends, and Cline and Roo Code support.

Documentation

Deploy	One-line install, targets, environment variables, operations
Agents	Adapters and what each can do
MCP	The 11 tools and how to connect
API	REST routes and authentication
Database	Neon or any Postgres, driver selection
Architecture	Data flow, tables, code map
Progress board	How the net-backlog board works
Telemetry and traces	Spans, OpenTelemetry ingest, retention, privacy
Memory (Notes)	What the notes store does and does not do
Usage and Costs	The experimental cost ledger
Playbook	How to run a multi-vendor agent fleet
Security	Threat model and reporting

The same docs are available inside the app under Help.

Develop

npm ci
npm run dev        # demo mode, no database needed
npm run typecheck && npm run test:ui && npm test && npm run build

See CONTRIBUTING.md. Changes are listed in CHANGELOG.md.

License

Apache-2.0. See LICENSE. Copyright 2026 Mark Hinkle.

Trademarks

Agent Kontrol™ and The AIE Network™ are trademarks of Peripety Labs LLC. The Apache License covers the code and, under its section 6, does not grant permission to use these names or the logo. You may use the name factually, for example to say your deployment runs Agent Kontrol. If you fork or sell a modified version, please give it your own name and logo.