HarnessRouter open-sourced: Grok Bot dispatches tasks to Jev and 24 other agent harnesses

Avi Chawla @_avichawlaOriginally posted 2026.10.24

Open original on X

Insane Grok @bot upgrade! Finally, you can connect Grok Bot to different agent harnesses and run tasks through their native runtimes. Devs just open-sourced HarnessRouter, the infrastructure layer that lets Grok Bot run tasks across: - Codex - Hermes - Claude Code - DeepSeek Harness - System One, powered by Jev - Pi, and 20 more GitHub repo: http://github.com/HarnessRouter/harnessrouter (don’t forget to star it ⭐) With HarnessRouter, each external specialist gets to use its own harness, model, tools, skills, and agent loop while Grok coordinates the project from one conversation. I tested this by asking Grok Bot to turn a support-ticket CSV into an interactive dashboard. Grok Bot assigned the analysis to DeepSeek Harness with Claude Sonnet 5.5, passed the output to Codex with GPT-5.5, and checked the finished dashboard in its browser. This differs from simply creating more Bots. These workers are not additional Grok Bots, and Grok Bot itself does not switch harnesses. Instead, it remains the coordinator while the delegated tasks run inside separate HarnessRouter sessions with the harness of your choice. So for another task, you can use Claude Code, Hermes, Pi, etc., without requiring a separate integration for task execution, sessions, streaming, and generated files. HarnessRouter standardizes all those operations through the Unified Harness Protocol (UHP). UHP handles sessions, streaming, files, cancellation, and failures through the same interface, regardless of which harness runs the task. I shared the GitHub repo above. And if you want to dive deeper into Grok Bot, I wrote about it in full in a masterclass, including the shared computer, memory, skills, routines, and the macOS setup. Read it below.

This post quotes another post: x.com/_avichawla/status/2089657097244024858