Your agents, one coordinated team
Bring Codex, Claude Code, OpenCode, Hermes Agent, OpenClaw or a custom agent. Assign each one a role, keep a human in control and let every agent retain its own tools and model access.
Conduit turns Codex, Claude Code, OpenCode, Hermes Agent, OpenClaw and custom agents into one coordinated development team. Keep your existing agent subscriptions, assign clear roles and carry shared repository context across supported harnesses. The engine runs entirely in your environment, on a workstation or an interactive cloud host, and the work stays there.
Agent subscriptions and model-provider usage remain billed by their providers. Signed installers publish at general availability; Linux ships first.
One coordination layer
Conduit coordinates the handoffs, questions and review points that separate a set of agent sessions from a working team.
Bring Codex, Claude Code, OpenCode, Hermes Agent, OpenClaw or a custom agent. Assign each one a role, keep a human in control and let every agent retain its own tools and model access.
Keep project context, task decisions and handoffs together. Supported agent harnesses can use the same repository map, so changing agents does not mean rebuilding the project picture from the beginning.
Choose which agent handles planning, execution and review. Reserve higher-cost agents for the decisions that need them, set role budgets and inspect cost with measured, estimated or unavailable provenance.
Agents pause when a material assumption needs confirmation. Supervisors and operators can answer, review outcomes and approve or reject work before Conduit reports it complete.
Runs in your environment
Use the desktop app where developers work or run the CLI beside your agents in an interactive session on a customer-managed cloud machine. The engine runs on your infrastructure: prompts, responses, source and worktree content never leave it. Infivector's hosted service handles account, licensing and release metadata; it never receives your work.
Linux uses Secret Service when it is available. On a host without it, each manual CLI mutation requires a short-lived terminal confirmation. Plugin pairing, hosted sign-in and unattended service operation remain off until the host has a supported credential backend.
01
Use supported coding agents with the subscriptions and provider accounts you already maintain.
02
Build one repository map for supported harnesses. Keep it available even when managed orchestration is turned off.
03
Set roles and budgets, answer questions and require review before work is accepted.
Conduit is separate from AION Enterprise, with its own license and release channel. The optional AION Bridge can connect agent roles to verified provider usage and cost evidence for enterprise deployments. Conduit does not require AION.
A Conduit subscription covers coordination. It does not include the agent tools or model-provider usage it coordinates. Those charges remain with each provider. Naming a tool here describes interoperability, not endorsement.