Welcome to the Arxcode documentation — built content-first with MDX.
Arxcode
ARXCODE

Run your first build

Ship a verified, sealed change with ArxCode Studio — end to end.

This guide walks through a complete Studio build: from describing an outcome to settling a verified result. It assumes you've connected a wallet and hold some $ARX (see the Quickstart).

1. Describe the outcome

Studio works from outcomes, not step-by-step instructions. Describe what you want to be true when the build is done.

arxcode build "Add rate limiting to the public API: 600 req/min per token, return 429 on exceed" \
  --repo ./api-service

2. Review the plan

Before touching anything, Studio produces a plan and an impact summary — the files it intends to change and the risk involved. Review it, then approve.

3. Let the loop run

Studio executes its agent loop inside the sealed boundary — acting, observing tool output, and self-correcting when a gate fails. You'll see progress as steps complete, but the plaintext source never leaves the seal.

Verification is automatic

Studio won't return a result until it builds, passes tests, and introduces no new lint or type errors. A failed gate loops back into the build, not onto you.

4. Review the diff

When the gates pass, Studio returns a diff encrypted to your wallet key. Review it inline, approve the changes you want, and export to your repo.

5. Settle

On approval, the consumed $ARX is burned and the sealed environment is destroyed. Nothing about your code is retained.

Next