How to publish a Capsule ======================== You publish a Capsule when you've made something with an AI agent — an HTML page, a markdown report, a generated prototype — and you want a private link to send to a reviewer. This file is for the *publisher*: the person whose agent created the artefact. If you're the one being asked to leave feedback, read how-to-review.txt instead. 1. One-time setup ----------------- Capsule lives at https://capsule.brinkbyte.com. If you've never used it: open a fresh agent session and paste this single line as your prompt: Set up Capsule for me by following the instructions at https://capsule.brinkbyte.com/install.md The agent reads the brief, creates your Capsule account against the email you give it, wires the Capsule MCP server into its config, and stores an API key locally. You don't have to click anything in a web form — the agent does the round-trip for you. If you already have an account: skip to step 2. 2. Publishing the first version ------------------------------- Ask your agent (Claude Code, Cursor, Codex, etc.) for whatever you'd normally ask. When the artefact is ready, say something like: Publish this as a capsule and share it with me. The agent calls the Capsule MCP tool, uploads the HTML or markdown, creates a share link, and replies with two URLs: Share URL — what you send the reviewer Comment URL — same link with a ?ct=… comment token Send the *comment URL* if you want pinpoint feedback (the reviewer clicks any element on the page to leave a comment). Send the bare share URL for a read-only preview. Both are private — they can't be guessed, but anyone holding the link can open the capsule, so treat them like read-only credentials. You can add a password or expiry at create time, or revoke any link from your /dashboard. 3. The review cycle (and where the human stays in the loop) ----------------------------------------------------------- When a reviewer leaves comments, your agent will pick them up next time you start a session — usually as soon as you say something like "check Capsule for feedback". The agent's job is to *recommend* the iteration, not to push it. The loop is: a) Agent reads the new comments via the Capsule MCP tools. b) Agent drafts the changes locally and shows you a diff vs the version that's currently live on the share link. c) Agent asks: "Approve this iteration?" — wait for your explicit yes. d) Only after your yes does the agent re-publish to the same share link. The Capsule link the reviewer is looking at does not change until you approve. This is intentional. Reviewers see what you sent; you decide when they see the next version. If you want to skip an iteration ("the comment was a misread, leave the capsule as-is"), tell the agent that. It can mark the comment as addressed-without-change so the reviewer knows you saw it. 4. Where to look in the portal ------------------------------ Everything publisher-side lives at https://capsule.brinkbyte.com: /dashboard — every capsule you've published /c/ — one capsule's history, share links, comments feed, and pending agent iterations awaiting your approval /connect — your API keys (and the MCP install configs for hosts other than the one you set up first) /members — invite teammates to your org /audit — every event on your account, including agent-driven publishes and approvals Pending iterations from your agent surface as a banner on /c/ with an Approve / Reject pair. That's the human-in-the-loop gate — nothing the agent stages is visible to reviewers until you act on it. 5. Limits + costs ----------------- Free plan ships with 10 capsules per org and 5 active share links per capsule. There's no per-view cost — share traffic is served from the Azure Front Door POP nearest the viewer, which is what keeps share-view latency under 50ms globally even on the free tier. If you bump into the cap, /connect surfaces an upgrade prompt. There is no auto-upgrade. 6. Help ------- Stuck or surprised? Email alec@brinkbyte.com — the team is small and replies usually land within a day.