For software engineering

Run the models and subscriptions you already have through a durable, evidence-first campaign system that verifies what actually changed, and drive it from the AI harness you already work in.

Who this is for: professional developers and technical teams who need the result to be provable rather than merely reported.

The journey

1. Run campaigns in Auteur Build. Multi-executor campaigns, private, sandboxed workspaces, canonical receipts, and hard spending limits. Whatever the executors report, Build derives what actually happened, ancestry, commits, changed paths, diff validity, and tests, from the record itself. Apply for the Founding Beta, /founding-beta/.

2. Drive it from your harness with Auteur Conductor. Operate authorized Auteur campaigns from the AI client you already use, in natural language, without losing the project or its evidence when you switch tools. Request Invitation, /founding-beta/?track=invite.

What stays true across the journey

An agent will tell you it finished. Build derives what actually happened, independently of the agent's own claim, and stops runaway branches and repeated dead ends before they burn the rest of the budget. Iteration, token, time, and spending limits are hard limits.

Designed for the agent you already use

Bring your own agent. Auteur is an amplification and accountability layer, never a replacement for your harness. Build runs Codex, Claude Code, and other executors under one campaign and evidence contract, and Conductor is designed to connect Claude Code, Codex, Cursor, Grok, Antigravity, OpenClaw, Hermes, and any spec-compliant MCP client, each at its own published compatibility status. See Integrations.

Honest scope

Conductor runs as a local connection; where each harness and deployment mode stands is published on the integrations hub and the deployment truth table.

Take the next step

Apply for the Founding Beta, /founding-beta/. An application to work alongside us; this starts a conversation with us, and seats, when offered, are paid.

Proof

Status source: site_data/product_status_registry.yaml · Claims: BUILD-002, BUILD-003, BUILD-004, BUILD-005, COND-004, COND-005 · Evidence: docs/proof/build_campaign_case/PROOF_DATASET.md · Verified: 2026-08-28.