Current state of orchestrators

It seems that everyone on Twitter is building their own agent orchestrator right now.

GitHub, Codex, and Claude cloud coding are lacking in innovation and not great for moving fast -- so I've been very excited to try some of the new orchestrators.

Orchestrators like Ami, cmux, Jean, and a bunch of side projects seem to be innovating on concepts like tickets, background agents, parallelism, notifications, etc. Hell, I even have 2 of my own orchestrators I've been messing around with for the past 3 weeks (one as a jj-native GitHub replacement and the other focused on my tmux workflow).

But the best one I've tried yet was not one I expected to be an agent orchestrator: OpenClaw (aka Moltbot) (aka Clawdbot) (aka Stophie's stellar reboot into tech totally for fun)

Enter the super-agent: OpenClaw

What makes OpenClaw a great orchestrator is its ability to handoff tasks to background sessions then notify you when it's finished.

This gives it a very simple conversational interface where you can do something like:

user: a user is having a bug in project X <screenshot>
openclaw: i'll start an agent to fix that
<few minutes later>
openclaw: the bug is now fixed
user: make sure there are tests to cover this
openclaw: sends new message to background agent
<few minutes later>
openclaw: 8 tests written and passing
user: push a pr
<a few seconds later>
openclaw: here is your pr link

When you put this together with the OpenClaw gateways (i.e. support for Discord, Slack, Signal, etc), it makes it an incredibly smooth experience switching from your desktop to your phone.

My workflows

Some misc behavior I've found works really well with OpenClaw:

• Git worktrees: tell OpenClaw to always do work in worktrees so you can keep programming in the main folder. Consider giving it access to worktrunk too.
• Audio messages & walks: I now commonly go on long walks and iterate with OpenClaw when working on non-critical tasks or experimental projects (not production code 💀). OpenClaw knows how to pull the Whisper model to run this 100% locally, though the API is faster.
• Tailscale: use Tailscale for accessing dev servers & the OpenClaw dashboard
• Give it your repo paths: tell OpenClaw to update agents.md with paths to common repos so it doesn't have to search your computer every time
• Linear CLI: give it access to your issues, let it rip
• Browser-agent CLI: the fastest browser for agents on the market
• Daylight computer: I work pretty much morning to evening with a break for the gym every day, so I've been working on ways of improving my sleep. OpenClaw gave me an excuse to acquire a Daylight DC-1 so I can now do code reviews & work with OpenClaw while winding down in the evening.

But you're probably holding it wrong

After a few days of using OpenClaw like this, I noticed it was unable to solve some really basic problems that Claude Code should have been able to do without issue -- even when I told it to use Opus 4.5 or GPT 5.2 high. Even weirder, I kept getting errors that the subagent ran out of context -- this never happens with Claude Code or Codex.

Something clicked and I realized -- OpenClaw is trying to act as a coding agent spawning instead of using Claude Code/etc.

OpenClaw has a powerful sessions_spawn tool to orchestrate background sessions. However, the default behavior is to use its own native sessions for coding.

This means that you're missing out on all of the benefits that the Claude Code/Codex/etc harnesses provide.

Coding harnesses matter

The reality is that in 2026, the harness matters almost as much as the model. Without a good harness, you're missing out on:

• better context management
• better compaction
• subagents (exploration and larger tasks)
• fine-tuned system prompt

("harnesses" is just a fancy way of saying a "coding agent cli" instead of using models directly)

Down the rabbit hole: the system prompt & skills

So I cloned OpenClaw to poke around how it's prompted.

Here's the gist:

• src/agents/system-prompt.ts
  • snippet: If a task is more complex or takes longer, spawn a sub-agent. It will do the work for you and ping you when it's done. You can always check up on it.
• skills/coding-agent/SKILL.md
  • description: Run Codex CLI, Claude Code, OpenCode, or Pi Coding Agent via background process for programmatic control.
  • Read about skill descriptions if not familiar
  • Your query must match this description for the agent to load & use the skill for coding agents
  • This skill also includes instructions on how to work with worktrees
  • Bonus: this skill auto-loads if it detects the coding agents in your $PATH, very cool
• docs/tools/subagents.md & docs/concepts/multi-agent.md
  • These need to be read via read tool
  • Likely will never make it into your context, since it needs to explicitly search for relevant terms

This means that:

• The system prompt uses OpenClaw's session_spawn tool for native OpenClaw subagents, instead of coding agents
• It has the ability to orchestrate coding clis, but needs to be explicitly told to use the skill

How to fix it

To fix it, just give OpenClaw this prompt:

Update your AGENTS.md to add this section:

Background Coding Work:

When I ask you to do coding tasks in the background or autonomously:
1. Use the coding-agent skill
2. Prefer Claude Code with Opus 4.5 model
3. Do NOT use sessions_spawn/sub-agents for coding work
For quick in-context edits, you can still code directly.

Now test it with a task like:

create a new tanstack start project that says hello world

Similarities with planner/worker swarm architectures

The cool part about this is this makes OpenClaw able to act as a planner orchestrating multiple tasks together, similar to patterns seen in Cursor's long-running coding agents or most other successfully long-running coding agents.

Current experiment: switching between sync and async coding

This is great for background tasks, but currently it's a bit clunky to switch from background agents to iterating with the agent in the foreground.

I'm currently experimenting with having OpenClaw automatically create a tmux session with nvim + cc open in the session, like this:

tmux new-session -d -s coding -c /tmp/my-task \; \
	send-keys 'nvim .' Enter \; \
	split-window -h -c /tmp/my-task \; \
	send-keys 'claude' Enter \; \
	select-pane -L \; \
	attach

This allows me to switch tmux sessions to jump into synchronous programming

Bonus: openclaw gateway wake as your notification center

If you're not already using this command regularly, you should:

openclaw gateway wake --text "Done: [summary]" --mode now

This command will have OpenClaw wake up, process a command, and send you a message.

I've switched OpenClaw to being my main "notification center." Anything I do in the background now uses this command.

A note on security

Please:

• Sandbox your OpenClaw
• Do not give it access to main on any repos
• Do not give it access to any code that you do not want on the open internet
• Assume all of your tokens you give it can and will be exfiltrated (including GitHub, Anthropic, and OpenAI)

I'm very careful about what I give OpenClaw access to, I find a new attack vector on this thing every few minutes.

Have fun and be careful out there