ox works with any tool that orchestrates coding agents — OpenClaw, Factory Droid, custom orchestration. However the session is launched, the integration is identical: the agent primes on startup, Team Context flows in, and artifacts are captured back.
The integration is the same
An orchestrator changes how a session starts, not what ox does inside it. The orchestrator spawns the agent, the agent runs ox agent prime, and from there the prime-work-capture loop runs unchanged.
Because priming is wired into the repo's CLAUDE.md (or the equivalent for other agents), it fires regardless of launch path — terminal, IDE, API, or factory. You don't configure the orchestrator to know about ox; the agent carries the integration with it.
Many agents, one Team Context
When a factory runs several agents in parallel against the same repo, they all prime from the same Team Context. Every agent sees the same conventions, decisions, and domain terms — so parallel work stays coherent instead of drifting apart.
As each agent's session is captured, its decisions feed back into the shared knowledge that future sessions consume. This is the multiplayer loop at scale: more agents working in parallel means the context compounds faster.
Captured artifacts become available to other sessions once committed. Agents running concurrently see each other's work on the next prime, not mid-session — so coordinate parallel agents around natural commit boundaries.
What's next
- How it works — the loop every orchestrated session runs
- Session recording — how captured work becomes shared memory
- Coding agents — which agents orchestrators can drive