Auteur Conductor

Bring the AI harness you already use; Auteur adds persistent projects, governed campaigns, production tools, verification, and receipts. Conductor is the harness-agnostic control surface that lets a compatible external AI client discover and operate the Auteur domains you have authorized, in natural language.

Bring your own harness

Change AI interfaces without losing the project, process, approvals, or evidence. Conductor supports configuration for the harnesses professionals already use, Claude Code, Codex, Cursor, generic stdio MCP, and generic JSON clients, while preserving one server authority. Per-harness compatibility is published for each named client rather than as a blanket claim.

Within that authority boundary, work stays inside approved authority, review gates remain visible, and unwired verbs are removed rather than left to fail quietly.

Visibility is not authority

Connecting an AI interface does not grant wildcard authority over files, spending, publication, or application changes. A tool can stay visible in a stale client list, but authorization is decided at call time, not at connection time, so a connected tool is limited to the authority it currently holds.

Only the capabilities the job needs

Auteur loads the capabilities needed for the job instead of flooding every AI session with the entire platform. Conductor keeps the external harness tool list scoped to the work at hand rather than exposing the full platform every turn.

Honest accounting across the boundary

As an editorial rule, this site does not present a usage figure a provider did not report, and does not show an unverified number in its place.

Every harness at parity

No harness is featured over its peers. Each is built to connect through the same server authority and carries its own per-mode compatibility state.

The integrations hub carries the current state for every named harness, each on its own page.