The open-source governed execution layer for AI agents

Give agents access. Keep control of every action.

Your team runs several AI agents against real systems. Conduit holds the credentials, policies, approvals, and records for all of them, outside the model.

The same refund tool can run a routine request automatically and pause a high-value one for approval.

How calls flowYour MCP servers, one governed path
  • Claude Code
  • Cursor
  • Codex
CONDUIT
  • checks policy
  • adds credentials
  • records result
  • GitHub
  • Linear
  • Postgres
  • Stripe
Every tool request passes through Conduit. Conduit checks the policy, attaches the credential, sends the request, and records the result.

Every call follows the same controlled path.

Conduit checks the request, protects the credential, handles approvals, and records the outcome. The same controls apply to every agent, whichever one made the request.

  1. Approve the action, not the tool.

    Risk depends on what an agent is trying to do, not only which tool it selected. Conduit can check the amount, recipient, account, or any other input before the request reaches your system.

    Define simple rules in YAML, or use typed TypeScript when a decision depends on application logic.

    - tool: stripe.*.refund
      when: { input.amount: { gte: 5000 } }
      then: require_approval
      else: allow
    • Example policy based on refund amount
    • $4.00runs automatically
    • $40,000.00waits for approval
    • Same tool. Different request. Different decision.
  2. The secret and the sandbox never meet

    Agent-written code runs in an isolated QuickJS sandbox and calls a tool by name. Conduit resolves the credential outside that sandbox and attaches it only when sending the request. The agent can use the connection without ever receiving its secret. Not filtered out. Never there.

    Access without credential exposure.

    Never receives the credential

    • The model
    • The agent
    • Agent-written code
    • Sandbox memory

    Attaches the credential

    • Conduit, host-side, when it constructs the outbound request
  3. Approvals can wait. The work does not start over.

    When an action needs approval, Conduit saves the execution at that point. Approve it later, even after a restart, and the work continues without repeating calls that already succeeded.

    Completed results are saved and reused. Conduit continues from the first action that has not run.

    1. stripe.getChargecompleted, result saved
    2. postgres.querycompleted, result saved
    3. stripe.refundwaiting for approval
    4. slack.postMessagehas not run

    A paused run is just data.

  4. Know what ran, why it ran, and what happened next.

    Conduit records every requested action, the policy decision behind it, what the tool returned, and how long it took. Credentials are never stored in the trace, and sensitive values can be redacted before export.

    Debug the run. Audit the decision. Explain the outcome.

    conduit
    $ conduit tools search "refund a charge"
    found 1 tool stripe.org.main.refund · require-approval ≥ $50
    $ conduit trace show run_2f91
    run_2f91 0.97s
    stripe.org.main.getCharge 200 212ms
    postgres.org.main.query 200 88ms
    stripe.org.main.refund held: policy over threshold
    $ conduit approvals list
    1 held stripe.refund amount=$240 · policy: over threshold
  5. Connect once. Apply the same controls everywhere.

    Connect your MCP servers once. Every agent that reaches them, and every Conduit client, gets the same policies, the same credential protection, the same approval flow, and the same execution history.

    Connect

    • MCP servers
    One governed path

    Use from

    • AI agents
    • CLI
    • SDK

Useful agents need real access.

Every agent your team adopts wants its own access to the same systems, and each one carries its own settings, its own permissions, and its own record of what it did. Conduit takes that decision out of the agents. One place holds the credentials, decides what each request is allowed to do, pauses what needs a person, and records the outcome.

Give agents enough access to be useful, with enough control to trust the result.

Your integrations grow. The prompt does not.

In Conduit's Code Mode, the model sees one tool instead of every connected tool at once. It searches for what it needs, then loads only the instructions required for the action it wants to take.

Load one schema when needed, not every connected tool on every turn.

Every schema loaded upfront2,000 tools
320,000tokens loaded every turn
Schemas loaded when needed1 tool
990tokens, every tool reachable
Every schema loaded upfront2,000 tools · ~320,000 tok
mergePullRequest()
listWorkflowRuns()
createRelease()
// + 682 more GitHub tools
createRefund()
listDisputes()
capturePayment()
// + 452 more Stripe tools
upsertLead()
runSoqlQuery()
convertOpportunity()
// + 317 more Salesforce tools
queryMetrics()
muteMonitor()
listIncidents()
// + 207 more Datadog tools
createIssue()
moveToCycle()
listProjects()
// + 112 more Linear tools
postMessage()
openModal()
listChannels()
// + 82 more Slack tools
appendBlock()
queryDatabase()
createPage()
// + 72 more Notion tools
query()
explain()
listTables()
// + 52 more Postgres tools
Schemas loaded when needed1 tool · ~990 tok
// the one tool the model ever loads: execute

Run agent-written code in Conduit's sandbox.
Tools are found, described, and called from
inside the code, one schema at a time:

  1. tools.search({ query })
  2. tools.describe.tool({ path })
  3. tools[path](input)

Nothing else enters the prompt until the
code asks for it.

323xless context, every tool still reachable

Estimates vary by schema size and tokenizer. This comparison uses the integrations selected above.

Start locally. Expand when you need to.

Every deployment option is built around the same policies, credential boundary, execution model, and trace.

  • CLI

    Node 20+Available in early access

    Run Conduit as a background service from your terminal. Your integrations, credentials, policies, and traces stay on your machine.

  • Desktop

    Mac, Windows, LinuxNot building yet

    A graphical console over the same local service. We build it when people ask for it.

  • Cloud

    HostedNot building yet

    A managed Conduit endpoint for teams that would rather not run the service themselves. We build it when people ask for it.

  • Self-host

    DockerNot building yet

    The complete server in one container, backed by one SQLite file. We build it when people ask for it.

Questions

What exactly does Conduit do?

Conduit sits between your AI agents and the systems they act on. Every requested action passes through it, where policy is checked, credentials are attached outside agent-written code, approvals are handled, and the result is recorded. The agents decide what to attempt. Conduit decides what is allowed to happen.

Can an agent or model see my credentials?

No. Agent-written code calls a tool by name. Conduit resolves and attaches the credential outside the sandbox when it constructs the outbound request. The credential never enters the model, the agent, the generated code, or sandbox memory. Stored credentials are encrypted at rest.

How does Conduit decide whether an action can run?

Imported API semantics provide a starting point: a read is not a delete, and an MCP tool that declares itself destructive is taken at its word. You can then add rules that inspect the call's actual arguments, including amounts, recipients, accounts, or any other typed input. Any default can be overridden, because these heuristics are useful, not infallible.

What happens when an action needs approval?

Conduit saves the execution and its completed results. After approval, the run resumes without repeating calls that already succeeded, and paused executions survive a service restart. If an approval expires first, that fact lands in the trace like everything else.

What can I connect?

MCP servers today. Any MCP-compatible agent, Claude Code, Cursor, and Codex among them, plus the Conduit CLI and SDK, reaches them through the same governed path. OpenAPI documents are imported and normalized but are not callable yet. GraphQL and custom integrations are on the roadmap, and we will say they work when they do.

Can I run Conduit on my own infrastructure?

Locally, yes. Conduit is Apache-2.0 licensed, and the early-access CLI runs on your machine. A packaged self-host option and a hosted one both exist as designs rather than builds; we start them when people ask.

/ get early access

Give agents real access without giving up control.

Conduit is open source and in active development. Get early access to run it against your own systems and help shape the first release.

Product updates and early-access invitations only.