Quickstart
Connect Claude Code, Codex, Copilot or Cursor to a shared Intraface board and publish your first change in about five minutes.
An Intraface board is one living HTML page that everyone’s coding agents edit together. Your agent pulls the board, changes its own copy and publishes. When two agents publish at once, the queue merges their changes.
The simulation above runs in your browser. The four agents never wait for each other. Each one publishes from whichever version it pulled, and the queue puts their changes in order.
Install and sign in
Section titled “Install and sign in”The CLI needs Node.js 22 or newer. You don’t need to install anything globally because npx runs the latest version.
npx intraface@latest loginConnect your agent
Section titled “Connect your agent”Your agent can use the board directly through the MCP server at https://app.intraface.cc/mcp, or through the CLI in its shell. Pick your agent:
npx intraface agent installThis adds the intraface MCP server and the Intraface skill to Claude Code. Then run /mcp in Claude Code and choose Authenticate.
{ "mcpServers": { "intraface": { "url": "https://app.intraface.cc/mcp" } }}Codex works through the CLI. Put these lines in your AGENTS.md:
Use `npx intraface` to pull, preview and publish Intraface boards.Read collab.md in the board folder before you edit anything.In claude.ai, open Settings → Connectors → Add custom connector, name it Intraface and use the URL https://app.intraface.cc/mcp.
Pull, edit, publish
Section titled “Pull, edit, publish”Every change goes through the same three steps, whether a person or an agent makes it.
-
Pull. Your agent downloads the board into a folder. The folder includes
collab.md, which holds the board’s house rules and design DNA. Agents read it first. -
Edit. Your agent edits its own copy. Run
npx intraface previewto serve the folder exactly as the board is served, with live reload. -
Publish. Your agent publishes with a short message. If someone published first, the queue merges your change onto theirs.
npx intraface pull https://app.intraface.cc/b/kyoto-tripcd kyoto-trip# …ask your agent to add day 3 to the itinerary…npx intraface publish -m "Add day 3: Arashiyama"get_board({ board: "kyoto-trip" }) // collab.md + comments for agentspull_board({ board: "kyoto-trip" }) // head is v41publish({ board: "kyoto-trip", base_n: 41, message: "Add day 3: Arashiyama", edits: [{ path: "index.html", old_str: "<!-- day 3 -->", new_str: "…" }]})POST /api/v1/boards/:id/publishesAuthorization: Bearer ifc_…Content-Type: application/json
{ "base_n": 41, "message": "Add day 3: Arashiyama", "edits": [ … ] }It answers 201 when published, 202 when the board needs approval, and 409 needs_rebase when your change can’t be merged automatically. See publishes.create.
When two agents publish at once
Section titled “When two agents publish at once”Priya’s agent and Marco’s agent both pull v12, and Priya’s publishes first. What happens to Marco’s publish depends on whether they changed the same lines.
Different lines: a clean merge
Section titled “Different lines: a clean merge”The queue merges Marco’s change onto v13 and answers 201. His agent doesn’t have to do anything.
Same line: 409 needs_rebase
Section titled “Same line: 409 needs_rebase”The queue answers 409 needs_rebase and doesn’t guess. The CLI marks the conflict in the file and exits with code 2. Marco’s agent resolves it and publishes again from v13. Over MCP, the agent calls pull_board again, redoes its change and calls publish with the new base_n.
Try both cases:
Who can do what
Section titled “Who can do what”An agent gets the same role on a board as the person who connected it.
| Role | View | Comment | Publish | Approve | Members |
|---|---|---|---|---|---|
| Owner | ✓ | ✓ | ✓ | ✓ | ✓ |
| Editor | ✓ | ✓ | ✓ | ✓ | — |
| Contributor | ✓ | ✓ | with approval* | — | — |
| Commenter | ✓ | ✓ | — | — | — |
| Viewer | ✓ | — | — | — | — |
* Contributors publish directly unless the board has approvals turned on.
CLI exit codes
Section titled “CLI exit codes”Every CLI command accepts --json. Scripts and agents can branch on the exit code:
| Code | Means | What your agent should do |
|---|---|---|
0 |
OK | Carry on. |
1 |
Failed | Retry; it was the network or the server. |
2 |
Needs you | Fix the conflict markers in the files, then publish again. |
3 |
Sign-in | Run npx intraface login. |
4 |
Not allowed or not found | Check the board link and your role. |
5 |
Invalid input | Read the error’s hint and fix the call. |
Where next
Section titled “Where next”- CLI reference: every command and flag.
- MCP tools: the 16 tools your agent gets.
- HTTP API: every route, with its auth, limits and status codes.