Customer guide

What Conduit does

Conduit runs in your environment and coordinates the coding agents you already installed. The desktop app and CLI are clients of one engine that owns workspaces, runs, approvals, clarification, review evidence and the shared repository map.

Prompts, source, transcripts and worktrees stay in your environment. The hosted licensing service receives account, billing, organization, device and release-download metadata; it does not receive repository or run content.

You can keep orchestration off and still use the workspace map and paired host tools. Turning orchestration off stops new team work and drains active work; it does not delete runs or workspace knowledge.

Before installation

• Install at least one supported coding agent: Codex, Claude Code, OpenCode, Hermes or OpenClaw.
• Keep the repository on a local filesystem your user can read.
• For writable runs, start from a Git repository with a clean base branch.
• Use the same operating-system account for the desktop app, CLI and coding agents. Conduit uses an owner-only local socket and does not claim isolation between processes owned by the same user.

First start

1. Launch Conduit. The app starts the bundled engine when no healthy engine is running, or connects to an operator-managed engine without taking it over.
2. For the CLI path, attach the operator credential once with conduit client enroll (the desktop app does this itself).
3. Register a workspace from the app or run conduit workspace register <repository path>.
4. Confirm the adapter readiness shown for that workspace.
5. Choose a workspace, select a team and submit a goal. The coordinated team flow runs from the desktop app; the CLI drives runs through run start, attach and the approval verbs.
6. Review the timeline, clarification requests, verdicts, retained worktrees and merge status before approval.

Linux cloud hosts

A customer-managed Linux cloud host is supported for interactive CLI use. Conduit uses Secret Service when it is available. If the host has no Secret Service session, the engine starts with persistent-secret features disabled and offers a manual terminal session for one mutation at a time.

1. Start conduit serve from the same operating-system user that will run the CLI.
2. Add --terminal-session to a supported mutation, for example conduit workspace register --terminal-session <repository path>.
3. Type the exact confirmation phrase shown by the CLI.
4. Repeat the confirmation for each later mutation.

Terminal sessions require an interactive TTY. They cannot be used with JSON output, plugin pairing or MCP. Hosted sign-in and connector credentials also stay disabled without the operating-system credential store. Unattended service operation requires a supported credential backend.

Sign-in and plans

Run conduit license signin or use the desktop sign-in action. Email links and Google sign-in complete through a one-time server transaction; the app stores the session in your operating-system credential store.

Personal Pro checkout is annual. Team is $60 per human seat per year with a five-seat minimum. Checkout shows renewal terms and requires acceptance of the current Terms of Service, EULA and Refund and Cancellation Policy. Enterprise is sales-led: [email protected].

Team setup

The first confirmed Team payment creates the Team organization and makes the buyer its owner. To add a member:

1. Ask the member to sign in to Conduit once. This creates their verified account; it does not assign a seat.
2. Open the Conduit account page.
3. Enter the member email under Team and choose Assign seat.
4. Ask the member to refresh their license in the app.

A verified account belongs to one organization. The owner can raise or lower purchased capacity on the account page; a reduction below the number of assigned members is refused. Each seated member has Team access while the owner's paid Team state is active, with two devices per human seat.

Shared organization policy

An organization policy bundle can carry role constraints, per-role discipline packs and an adapter allowlist. Policy updates apply to later runs, never an active run. An absent or empty adapter allowlist means unrestricted; to restrict adapters, list every admitted one. A custom adapter entry pins the executable digest, so a changed binary is refused even when its name matches.

Clarification and approval

Agents ask the supervisor when a material assumption is not verified; the question parks the task until the answer arrives, and open questions block completion. A review task must submit an explicit verdict. Approved work merges back only when the worktree is clean and Git can merge without conflict; Conduit retains dirty or conflicted worktrees and shows the recovery action instead of claiming the work landed.

Custom adapters

Custom adapters use the versioned local protocol. Installation requires an explicit executable digest; Conduit verifies the manifest, binary path, digest and permissions at startup and refuses names that collide with built-in adapters. A custom process receives the same per-turn confinement and engine-owned environment as a built-in adapter.

Troubleshooting

• Adapter unavailable:run the agent's own sign-in, then restart or reprobe Conduit. Conduit does not copy provider credentials into its data store.
• Policy refused: ask your organization administrator whether a newer bundle was issued and whether the installed custom-adapter digest matches it.
• Member not found: the member must sign in once before the owner assigns a seat.
• Seat change refused: keep at least five purchased seats and never reduce below assigned members.
• Run waiting: open the run details; it may need a clarification answer, review verdict, sandbox permission, quota reset or merge recovery.

Billing or account help: [email protected]. Enterprise, SSO, DPA or AION Bridge: [email protected].