>
Write better
software.
Artifact gives your product’s purpose, behavior, and decisions a living record,
so people and AI can build from the same understanding.
S-0001A shared understanding
Get everyone (and your agents) on the same page.
Your product takes shape in conversations, sketches, decisions, and questions. Give that thinking a home that people and agents can work from.
Notion, Slack, Linear, Google Docs, Zoom, Word, Excel, Markdown, and loose files connect to one Artifact record. Artifact reads your repo read-only, briefs Claude Code, Cursor, and Codex before they write, and checks what they wrote against the record.
More than a doc.
Artifact reads your codebase and connects it back to documents you, your agents, and tools can actually read, understand, and edit.
Checkout
A customer pays for a full cart without leaving the page. One flow, one receipt.
Rulesanchored to checkout.ts
- 01 A customer cannot check out without a saved address. L3 DRIFTED
- 02 Refunds over $500 need a human to approve them. L8 DRIFTED
- 03 Do not change the pricing page without approval.The pricing page can change without approval. L14 DRIFTED Resolved · agent restored signOff()Resolved · rule 03 now matches the code
Acceptance
- Checkout completes on one screen, phone and desktop.
- The receipt shows items, address, and amount paid.
Decisions
- D-0142026-08-12Stripe stays the only processor. Priya
- D-0192026-09-03Finance signs off on every pricing change. Marcus
Q-007 · OPEN
Does a refund over $500 need one approver or two? Unanswered. Attached to rule 02.
anchored to src/checkout.ts · read-onlylast read 09:41
checkout.ts
agent writingagent done
1import { stripe } from "./pay"
2
3function placeOrder(buyer: Customer) {
4 if (!buyer.address) throw noAddress()
5 return charge(buyer)
6}
7
8function refund(amount: number) {
9 if (amount > 500) return approve()
10 return stripe.refund(amount)
11}
12
13function editPricing(page: string) {
14 if (page === "pricing") publish() if (page === "pricing") signOff()
15 return render(page)
16}
- Connect your repo read-only. Artifact never writes to your code.
- Every sentence is linked to the code that implements it.
- When the code stops matching a sentence, you get told. You decide which one was wrong.
S-0002Plug N' Play
Your agents, with superpowers.
Nothing to switch to. Artifact plugs into the agents you already run.
Works with
GitHub
Anthropic
OpenAI
Cursor
artifact ›
S-0003Product Harness
The layer above your coding agent.
A coding harness keeps an agent on task. A product harness keeps the product on intent. Artifact sits above Claude Code, Cursor, and Codex, not in place of them, and adds two steps to every run: a brief before, a check after. That is the whole change to your process.
Read about the product harness →You and your team decide what the product is for. Features, rules, and decisions go on the record, in plain language.
Before the run, Artifact hands your coding agent a brief: the feature, its rules, its acceptance criteria, and what must not change.
Claude Code, Cursor, or Codex writes the code in your repo, on your model and your plan, with your standards compiled into the session.
After the run, Artifact reads what shipped, read-only, and checks it against everything the product is supposed to be.
Drift comes back to you with the rule it broke. You decide: fix the code, or update the record.
You and your teamDecide what the product is for, and decide on anything that drifts. Artifact never makes that call for you.
Product harnessHolds the record, writes the brief, runs the check. It sits above your coding agent, not in place of it. Open the record, the brief, or the check.
Coding harnessClaude Code, Cursor, or Codex. It keeps the agent on task, and it stays exactly where it is.
ModelWhatever model your agent already runs, on your own plan.
Your repoWhere the code lives. Artifact reads it, read-only. It never writes to your code or keeps a copy.
The recordFeatures, rules, decisions, open questions, and the sources behind them. It lives outside any one agent, so nothing you decided is lost.
The briefCompiled for every run: the feature, its rules, its acceptance criteria, the decisions behind it, and the boundary of what must not change.
The checkWhat shipped, against the whole record. Drift is shown with the rule it broke, and you decide on it.
This is not vibe coding.
Vibe coding scatters decisions across chats and carries them forward inconsistently. Artifact holds them once, on the record. And no, you don't have to stop vibing.
Sound familiar?
Vibe coding vs Artifact, in detail →A memory that isn't a chat.
What your product is supposed to be, on the record: features, rules, decisions, open questions. It lives outside any provider. Switch from Claude to Codex tomorrow and nothing you decided is lost.
Your rules, in every session.
Coding standards, security standards, the CSS you'd actually accept. Compiled into each agent's brief before it writes a line. Your taste and judgment, at machine speed.
A reviewer that reads the whole product.
Every result is checked against what you meant, not just the diff. What changed, what broke, what quietly drifted. Shown in plain language. You decide what to do about it.
The next chapter is yours
Get it in writing.
Explore a different way to make software.
We're inviting early adopters into the conversation.
