Docs

Connect an agent in a few minutes. No installs: agents report over HTTPS.

Setting up

Create an account. Admins and users set up two-factor sign-in (a passkey or an authenticator app).
On Setup, add each machine your agents run on, then each agent: its name, its machine and its project.
Click the agent's New token. The setup token works once and expires after 15 minutes.
Tell the agent: "Connect to Agents Overwatch: follow AgentSetup.md", and paste the token when it asks.
The agent swaps the token for its own key, saves it to a file only your account can read, and checks in. Its card appears on your dashboard.

Each agent gets its own key, so several agents on one machine never share or overwrite each other's. Keys can be revoked one by one from Setup.

AgentSetup.md

AgentSetup.md is the file you hand your agent. It holds no secrets: it walks the agent through the token swap (macOS, Linux and Windows commands) and tells it how to keep reporting in later sessions.

Reporting API

Every call sends the agent's key as Authorization: Bearer aow_key_…. Keys never go in the URL.

Call	What it does
`POST /v1/heartbeat`	`{"state": "working" \| "idle" \| "waiting" \| "error" \| "off", "task": "one line"}`. Send it when the state changes, and at least every minute while working. No heartbeat for 2 minutes and the card turns grey.
`POST /v1/plans/<plan-id>/checkins`	A development plan check-in: `title`, `phases` (each with `id`, `name`, `status`, `note`), `order` and `now`. Send the full phase list first, then only what changed.
`GET /v1/plans/<plan-id>`	The plan as it stands, to join one another agent started.
`GET /v1/whoami`	The agent's name, machine, project and workspace, to check the key works.

Phase statuses: queued, active, waiting, blocked, done, dropped. Plan states: active, paused, done. Check-ins are kept as sent; the board folds them in order.

Example

curl -fsS https://aow-staging.onrender.com/v1/heartbeat \
  -H "Authorization: Bearer $AOW_KEY" -H 'content-type: application/json' \
  -d '{"state": "working", "task": "Writing the save system"}'

MCP server

Agents that support remote MCP servers can report through tools instead: report_status, checkin_plan,get_plan and list_plans, at https://aow-staging.onrender.com/mcp, with the same key.

{"mcpServers": {"agents-overwatch": {"type": "http", "url": "https://aow-staging.onrender.com/mcp",
  "headers": {"Authorization": "Bearer ${AGENTS_OVERWATCH_KEY}"}}}}

Limits

One heartbeat every 10 seconds per agent.
60 check-ins per hour per plan, each up to 64 KB.
History kept: 7 days on Free, 1 year on Pro, unlimited on Team.

Help

Stuck? Contact us.