Auteur Conductor

Bring the AI harness you already use; Auteur adds persistent projects, governed campaigns, production tools, verification, and receipts.

The patchbay case, with cables running into every other case: your harness is the console you drive from, and Auteur is what the patches actually reach.

Bring supported models, providers, harnesses, and local compute.

Auteur Intelligence™ lets a supported harness take advantage of supported models from the providers you already hold, by subscription, OAuth, CLI, or API, and of local compute you own. All of them communicate and orchestrate together in one project, with real benchmark receipts and evaluation, and long-term memory of what worked and what did not, regardless of platform. It is a shared project layer across supported models, harnesses, and applications: one place where code, long-form writing, research in any discipline, film, and audio production run with receipts. And because the mixture spans providers, not just models, the mistakes of one lab get caught by the instincts of another. Strength in numbers, confidence in diversity.

Who it's for

Professionals who already work in an AI harness, Claude Code, Codex, Cursor, and want it to operate their Auteur project in natural language without losing the project, process, approvals, or evidence when they switch tools.

“Coordinate several agents across two computers, pause at every approval gate, and resume from the last verified state.”

The conductor's judgment

Bringing many models is only useful if something intelligent decides between them, and that is the layer chat harnesses do not have.

• Capability-aware routing, the studio knows what each seat can and cannot do: which handle video, which handle images, which carry the long context a big build needs, and routes the work accordingly instead of letting a text-only seat fail at a video job.
• Build-time forecasts, campaigns estimate remaining time from prior history, and the forecast updates as rounds land, so you know what an overnight run really means before you start it.
• Stop, switch, resume, when a seat is failing, the build stops before it burns more spend; the work reseats to a different model and resumes from the receipts, not from zero. Fully automatic mid-flight reseating is where this is designed to go.
• Failures remembered, every failure is classified and recorded to the model ledger, so the same mistake is not bought twice: the next build routes around what already went wrong.

What it solves

Changing AI interfaces normally means starting over. Conductor lets a compatible external client discover and operate the Auteur domains you have authorized, so the project and its governance survive the change of harness.

“Seat Codex as the builder and Claude as the reviewer, give them separate worktrees, and wake me only if a gate fails twice.”

How it works

Your harness is the console; the authority stays on the Auteur server. Conductor keeps the tool list scoped to what a job needs instead of flooding the session, and ordinary-language requests reach bounded domain actions across writing, prep, visual work, Resolve, and campaigns.

Workspaces included

• Bring your own harness, configuration for Claude Code, Codex, Cursor, generic stdio MCP, and generic JSON clients under one server authority.
• Dynamic domain packs, a small discovery core that activates task-relevant capabilities instead of exposing the whole platform every turn.
• Call-time authorization, server-side permission checks applied to each request.
• Natural-language production control, ordinary-language requests mapped to bounded, reviewable domain actions.

Embedded from other products

Conductor does not fold another paid product inside it. It is the access mode that lets your harness reach the products you are entitled to, the patch bay, not a second copy of the studio.

Moving up

Conductor is the headline way to drive Build campaigns from your own harness, and it reaches the whole shelf inside Studio.

Where it runs

Conductor runs beside the harness you already use and the Auteur server it drives.

Demonstrated

By 2026-08-28, the local implementation had been tested, and natural-language production control had run across many domains, not yet across the rest.

Current limitations

Visibility is not authority: seeing a tool is not permission to use it, and connecting a harness never expands the authority you already hold, it grants no wildcard control over files, spending, or publication.

Related products

Build · Story · Prep · Film · Game · Learning · Edit · Launch · Studio

Questions

Do I have to move off the tools I already use? No, that is the point. Auteur is built to let you keep working in your existing harness, with your project, approvals, and evidence coming with you.

Which harnesses is Conductor built for? Claude Code, Codex, Cursor, generic stdio MCP, and generic JSON clients are the designed clients; compatibility is published per client rather than claimed for all of them, so each harness page carries its current per-mode state.

Take the next step

Request Invitation, /founding-beta/?track=invite. A small, deliberately limited cohort; this starts a conversation with us, and seats, when offered, are paid.

Proof

Every claim on this page traces to the product status registry, with evidence in SDK tests, harness probes, and the MCP release packet, last verified 2026-08-28. The receipts behind it are claims COND-001–005.