OpenClaw as the foreman
You probably already use a coding agent — Claude Code, Codex, OpenCode, Aider, Cursor's CLI. Each one is great at coding. None of them is great at running your business. They have no Heartbeat, no persistent persona, no Telegram channel, no calendar.
OpenClaw is the layer above. It is the foreman that:
- Hears the request (typed, voice, or scheduled)
- Decides which coding agent to use
- Hands off the precise task with the right context
- Receives the diff and runs the verification
- Reports back through your messaging channel
Why this split is durable
Coding agents change every quarter. OpenClaw's job — orchestration — does not. By treating the coding agent as a swappable Skill, you future-proof your setup against the next-best tool.
The matrix
| Need | Best handoff (Q2 2026) |
|---|---|
| Multi-file refactor with reasoning | Claude Code (Opus) |
| Quick edit / one file / cheap | Codex (GPT-5 small) or OpenCode |
| Local-only, offline | OpenCode + Ollama |
| Test-driven loop, long-running | Claude Code with TDD subagent |
This matrix lives in your Agent file. When it changes (and it will), you update one file.
What we will build
By the end of this chapter, OpenClaw can take a Telegram message — "fix the failing tests in ~/Code/myapp" — pick the right coding agent, pass it the working tree, watch it work, and reply with a summary.