Engineering
Grok Bot as coordinator; HarnessRouter farms Codex/Claude/Hermes/etc.
Multi-agent setups become either one mega-bot or a pile of disconnected tools.
What hurt
@BrianRoemmele keeps a long-lived Grok Bot coordinator, then delegates via open-source HarnessRouter (UHP) to Codex, Claude Code, Hermes, DeepSeek, Pi, Grok Build, etc. Recurring light work stays as Grok Bot routines; heavy lifts go out. Self-host example: docker run harnessrouter on localhost:3000. Tip/method; keys stay on your infra. Not affiliated with xAI.
What to install or create
Self-host HarnessRouter → coordinator picks harness_id → specialists return via one contract.
Bots
Coordinator bot
Breaks work into steps and calls HarnessRouter with a harness_id.
Plugins
Browser
Optional
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/BrianRoemmele/status/2114128789349490731 (credit @BrianRoemmele).
- 2On a machine you control, run his docker example for HarnessRouter (localhost only).
- 3Add provider keys in the HarnessRouter console; generate an API key.
- 4Point your Grok Bot coordinator at the Responses endpoint with harness_id metadata.
- 5Keep light routines on Grok Bot; delegate heavy coding/analysis to the matching harness.
Approval fence
You control keys and where HarnessRouter runs; approve any spend or external publish.
What to tweak
Steal the split: one conversation interface; external harnesses keep native strengths.
Source
Brian Roemmele @BrianRoemmele · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.