Build AR scenes with the AI agent you already use

What you get

• An agent that looks before it reports

  arclip verify catches broken references and scenes nobody can see, arclip render draws the scene on the server without an open editor, arclip playtest runs the scripts and presses every control. The agent sees the result instead of guessing.

• Your scene on your phone, live

  arclip dev prints a QR code. Scan it and the draft opens in the phone's browser — no login, no publishing. The phone offers the new version after every edit, and the terminal re-checks the scene as it changes.

• Your agent, your subscription

  Anything that runs terminal commands or speaks MCP works. arclip link registers the ARClip MCP server for the folder, pinned to one project — and your token never lands in a project file.

• Live with your team

  The scene stays on the platform, so the agent's edits appear in your teammates' editors as they happen, and theirs reach the agent. Nothing to export, nothing to merge.

What arclip link sets up

Run it in any folder — a new one or your existing repository — or start with arclip clone, which also brings the project's scripts and UI cards down as files. Configs you already have are merged, not overwritten.

.arclip/project.json

Which project this folder belongs to. Safe to commit.

CLAUDE.md

Instructions for the agent: build, verify, render, playtest, then report — and never publish unless you asked. Kept if you already have one.

.mcp.json

The ARClip MCP server, started through the CLI and pinned to this project.

.claude/settings.json

Lets the agent read our docs and run the read-only checks without asking. Publishing always asks.

Commands

arclip --help lists them all, and every command has its own --help. The result goes to stdout, diagnostics to stderr.

Scripts and CI

--json makes every result machine-readable, and a failed check exits with code 1. In CI, put a token and a project in the environment — no login needed.

export ARCLIP_TOKEN=arclip_…
export ARCLIP_PROJECT=<projectId>
arclip verify --json
arclip render --view top -o top.png

Honest limits

• Scripts and UI cards live in the folder as files (arclip pull / push); the scene itself stays on the platform, where people edit it together, and is not pulled as files yet.
• arclip render is a fast server-side preview: layout, scale, colours and textures are real, scripts and effects are not. For the exact look, arclip render --real draws the scene with the published runtime in headless Chrome on your machine — 3D and surface scenes; ones that start from a camera need a device.
• arclip playtest and arclip test play the scene in the editor, so the project has to be open in a browser tab — including in CI.
• What an agent may do follows your plan: on Free it can read and check projects, while building, AI generation and publishing come with paid plans. AI generation spends your team's credits, as it does in the editor.
• arclip dev opens the draft in the phone's browser, not yet in the ARClip app. A running AR session offers to reload rather than swapping the scene under you.

Questions