Codex with Artifact

Run Codex today, Claude tomorrow, both on Friday. The truth stays in one place. Artifact doesn't replace Codex. It briefs it before every task and checks what it did after.

The product harness →

Before the run. After the run. Nothing in between changes.

Before: the brief

Codex calls Artifact over MCP and pulls the context bundle for the task: the feature, its rules, its acceptance criteria, the decisions behind it, and the boundary of what must hold. You stop pasting context into the prompt.

During: your rules

Your standards, security rules, and taste are compiled from one rule set into AGENTS.md for a Codex session. Change a rule once; every repo gets it. Codex works a scoped change, not a free roam.

After: the check

What Codex shipped is checked against everything the product is supposed to be, not just the diff. Mismatches are shown with the intent they violate. You decide: regression, or intent that changed.

Add Artifact. Keep working.

  1. 01

    Add Artifact to Codex.

    Add Artifact to Codex's MCP configuration. Codex reads the same operations Claude Code does.

  2. 02

    Artifact serves the operations.

    Orient, context, search, work packet, verify: one operation each, served identically over MCP and HTTP. Codex sees them beside its own tools and calls them when a task needs them.

  3. 03

    Your rules file stops drifting.

    AGENTS.md is compiled from your harness pack instead of hand-maintained per repo. Project overrides where a team needs them. Zero footprint on the repo itself.

  4. 04

    Work as you do today.

    Same prompts, same pull requests, same CI. The brief arrives before the task; the check arrives after. That's the whole change.

Works today: the same operations over MCP; switching between hosts loses nothing, because the record lives outside both.

Artifact MCP
artifact ›

The operations Codex will call, live over a sample project. Try work_packet FEA-0001.

Your tool. Your subscription. Your repo.

Your subscription

All model inference runs on the OpenAI account you already pay for. Artifact's server does deterministic work only. No metered tokens you can't predict.

Your repo

Artifact never writes to it and never keeps a copy. Codex reads in your session; the server keeps an index and a citation, not a codebase.

Your memory, outside the tool

The record lives in Artifact, not in Codex's session. Switch to another host tomorrow and nothing you decided is lost. Export everything, anytime, as plain files.

Things people ask about Codex and Artifact.

Does Artifact replace Codex?

No. It serves it. Codex writes the code; Artifact makes sure it starts from what you decided and checks what it did.

Do I have to change how I prompt?

No. The brief arrives as context Codex pulls itself. You'll find you paste a lot less.

What if Codex touches something outside the packet?

The check compares the result against the whole product, not just the target feature. A change that contradicts a rule elsewhere shows up as a mismatch, with the rule attached.

Can my human developers use the same brief?

Yes. A work packet is the same thing whether an agent or a person builds from it. Same intent, same rules, same done-criteria.

Get it in writing.

Explore a different way to make software.
We're inviting early adopters into the conversation.