Auteur is built to seat Cursor

Auteur is designed to seat Cursor while your persistent projects, governed campaigns, verification, and receipts stay underneath. The agent can change; the project, process, authority, and evidence remain.

What Cursor does well

Cursor is a widely used AI-native editor with MCP support and a strong in-editor agent. Developers live in it, which is exactly why a compatible control surface is worth offering.

What it brings to the seat

Cursor brings the editor itself: the place many coders already live. Seated with Auteur, it keeps that role while the project supplies what an editor alone cannot: campaign structure, cross-model review of its diffs, and a memory that carries decisions between sessions. Bring the Cursor plan you already have.

“The Cursor session claimed the tests passed. Did they?”

The question that saves your weekend

“The verification gate says no: 2 of 41 never ran. The seat was failed, the retry is queued, and the receipt shows exactly which two. Your editor stays open; the project stays honest.”

Illustrative exchange. Verification gates and seat receipts are shipped surfaces.

When a provider changes course

News reports say OpenAI is ending its Cursor integration, and that ChatGPT will no longer be available as a coding agent inside Cursor as of November. For Auteur Intelligence™ users, that is a footnote, not a crisis. Connect Auteur Build to your Cursor harness and Cursor keeps orchestrating, while OpenAI Codex (the Sol-generation frontier tier, as of this writing) works your campaigns as a primary coding agent through the platform's own routes, alongside every other agent in your stack. Invisibly, if you like: create a campaign that includes Codex, and it is still in your stack. No harm, no foul.

This is the model-agnostic philosophy earning its keep. When a model becomes unavailable from one provider, the studio plugs it into your code-building campaigns from another route. Your workflow does not change; the wiring underneath it does, and the receipts still balance.

"Create a build campaign with Codex as the primary coder and my Cursor seat as orchestrator, and route around the retired integration."

What Auteur adds

For someone already using Cursor, Auteur would add a persistent project that keeps its own canon and evidence instead of losing them to the session; governed multi-round campaigns; production tools beyond code; and canonical receipts that verify what actually changed independently of the agent's own claim. Cursor stays your interface, Auteur is the amplification and accountability layer behind it.

How it connects

• Client. A configuration form for Cursor exists in the harness registry, so the client path is designed as an MCP control surface over authorized Auteur domains.
• Executor. Cursor would run as a Build campaign seat under an executor profile, headless.
• Direct model. Auteur does not call a Cursor-specific model lane.

Which Auteur products it reaches

By design, a Cursor client connection would address the Auteur domains you are entitled to, writing and story, prep, film, game, learning, and the Build campaign system. Reachability is not entitlement: which domains you can operate depends on what you hold.

What is measurable

Auteur measures the work that runs through it, deriving token and cost accounting from the record of what it ran.

Auteur never invents missing usage data; missing = unknown, never zero. No token or cost figure is ever shown for work performed outside Auteur's visibility.

What this integration does not do

• It does not offer a Cursor-specific direct-model lane.

Security and authority boundary

Connecting Cursor would not grant it wildcard authority over your files, spending, publication, or application changes. The connection is an interface, not a grant of authority, what a connected agent may do stays governed by Auteur, not widened by connecting it.

Current status

Current per-mode status is shown above.

Proof

No published evidence yet. When a natural-language canary is recorded against Cursor, this section will link it. Follow progress on the roadmap.

Set it up

If you work in Cursor and want to be part of the compatibility testing, the invited local connection is the place to start:

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

Affiliation

Auteur is designed to connect with Cursor. No partnership, endorsement, or certification is claimed, and none exists.