Notion control plane for agent fleet
The author built AgentOps, a Notion control plane that tracks, queues, logs, and alerts on their 18 OpenClaw agents.
Notion now tracks 18 agents and 78 logged runs; separately, an unsubscribe agent cleared 47 vendor mailing lists in two weeks.
Overview
How it was set up
OpenClaw agents on Lightsail or a Raspberry Pi, connected to four Notion databases (Agent Registry, Task Queue, Run Log, Alerts) through Notion MCP. Status changes in Notion control dispatching.
Worth knowing
The serverless AgentCore variant is described as experimental and not production ready.
A prompt to start from
The source does not show the prompt.
Sources 1
History
- Source published
- 2026-03-07
- Added to Agentic Feats
- 2026-10-13
- Pick
- No
- Markdown copy
- /c/notion-control-plane-for-agent-fleet-openclaw.md
More in ops and IT
20 featsResultProvisioning worked after two fixes. The MCP hid the real errors, so apply ran through Cursor's Run tool, which suggested the fix.
ResultThe author migrated 10+ Lambda functions from Node.js 14 to 20 in one pass and fixed a broken docker-compose file by auto-retrying until clean.
ResultThe author runs 14 containers including Vaultwarden, Immich, Plex, and Readeck, with daily USB and weekly S3 Glacier backups costing about twenty cents per month.