Agents
Two instances, seven sub-agents
OpenClaw runs as two independent instances -- Max and Eva -- on separate physical machines, operated by different people. Each instance has its own set of specialized sub-agents for specific tasks.
Agent Topology
Machine 1
Max
mainmail-readerkickoff-codingbridge-readerbridge-voiceMachine 2
Eva
mainbridge-readerMax
Dedicated Mac, 8GB RAM
mainCentral orchestrator. Handles Telegram commands, task delegation, system management.
mail-readerIsolated email processing. Exec in allowlist mode, only mail-extract script authorized.
kickoff-codingWeb project deployment. Receives client briefs, generates code, deploys to hosting.
bridge-readerDisposable sanitizer for inter-agent messages. Zero tools, 60s timeout, rewrites everything.
bridge-voiceHandles voice messages from the bridge. Transcription + processing in isolation.
Eva
Dedicated Mac, 8GB RAM
mainCentral orchestrator. Handles Telegram commands (@EVAJool_bot), task management.
bridge-readerDisposable sanitizer for inter-agent messages. Same zero-trust pattern as Max.
| 07:00 | Weather briefing |
| 07:05 | News digest |
| 07:10 | Email processing |
| 2x/day | Memory distillation |
| 2x/day | Autonomous reflections |
| Every 3h | Memory shepherd cycle |
| Hourly | Memory extraction + reindex |
A monitoring daemon (imsg-watcher) continuously polls the iMessage database. Each incoming message spawns a fresh one-shot sub-agent with minimal permissions and a strict 300-second timeout. The sub-agent processes the request, responds, then terminates. No persistent sessions exist between messages.
One message = one agent = one session. Complete isolation.
ACP dispatch is disabled on both instances. All routing is handled through direct skills and cron jobs.