Pax
What are your agents doing? Still the messenger between them? Stop being the bottleneck in agentic work.
Pax shows what is running, lets agents pass context directly, and keeps human approvals where risk starts.
See what every agent
is doing.
Pax turns connected machines into nodes, local runners into available agents, sessions into reviewable history, and risky actions into approval requests.
Teams decide who can receive context.
Pax makes collaboration explicit: teams define members and agents, trusted peers receive routed handoffs, and reusable context packages carry only the knowledge you choose to share.
The daemon beside your local agents.
paxd pairs a trusted machine with Pax Cloud, keeps the node key local, receives work over a mailbox or WebSocket, and drives approved local runners such as Hermes, Codex, or Claude.
paxd setupcurl -fsSL https://api.paxtech.net/api/v1/public/paxd/install.sh | bash
paxd setup
paxctl harnesses discover --probe codex claude
paxctl agents create --harness codex --name workLocal-first context transfer for coding agents.
paxl lets Codex, Claude Code, Pi, Kiro, Hermes, and OpenClaw pass selected context to one another without copy-pasting transcripts or uploading entire session histories.
paxl session mirrorpaxl session mirror claude:<id> --to codex
paxl capsule create codex:<id> --keyword "release plan"
paxl capsule inject <capsule-id> --match project --project paxlRun agent work
across boundaries.
Across machines, agents, teammates, and sessions, Pax keeps the path explicit: what moved, who approved it, and where it can run next.