demobite 1.0.0 → 1.0.2

package/README.md

@@ -11,7 +11,8 @@ npx demobite
 ```
 
 That one command checks your setup, installs the recorder skill for
-[Claude Code](https://claude.com/claude-code), and wires the DemoBites
+your coding agent — [Claude Code](https://claude.com/claude-code), Cursor,
+or Codex — and wires the DemoBites
 management MCP so your agent can also run your Update Center and Demo Center.
 Sign-in happens through your own browser — no passwords in the terminal, ever.
 Then you just ask your agent:
@@ -30,12 +31,59 @@ The agent storyboards the flow, films it in a real Chrome, and stages the take
 for your approval inside DemoBites. You approve in the product; the platform
 does the rest.
 
+## Manage DemoBites from your agent (MCP)
+
+Recording is half the story. The same package wires the **DemoBites management
+MCP** — a control plane your agent uses to run your Update Center and Demo
+Center. Your customers' agents read your centers; your agent runs them.
+
+```bash
+npx demobite mcp
+```
+
+Claude Code is registered automatically. Any other MCP client works over
+Streamable HTTP: point it at `https://app.demobites.com/api/mcp` with the
+`Authorization: Bearer <key>` header the command prints (in Cursor, add both
+under Settings → MCP). Then talk to your agent like a teammate:
+
+> "Create a release with my latest bites, add Spanish, and publish it."
+
+> "What's on our Demo Center? Swap the checkout bite for the onboarding one."
+
+### What it can do — 19 tools
+
+| Group | Tools |
+|---|---|
+| Connect | `get_started` · `connect_demobites` · `check_connection` · `get_recording_options` |
+| Read | `get_status` · `list_bites` · `list_releases` · `get_release` · `list_languages` |
+| Draft & edit | `create_release` · `update_release` · `assign_bites_to_release` · `update_center_settings` · `add_language` · `update_demo_center` |
+| Publish — with your approval | `publish_release` · `unpublish_release` · `remove_language` · `publish_demo_center` |
+
+The server describes itself: any client's `tools/list` returns every tool with
+its full input schema, straight from the running code.
+
+### You stay in charge
+
+Draft work executes directly, exactly like clicking around the product. But
+anything that touches a **public** page is two-phase: the tool returns a
+human-readable preview plus a single-use confirmation token, your agent shows
+you the preview, and only your go-ahead executes it. Tokens expire in ten
+minutes, are bound to the exact action and arguments, and every management
+call lands in an audit log.
+
+### Plans
+
+Connecting and reading are open. Managing requires the **Grow** plan.
+Recording works on every plan.
+
+Full guide: [Manage from your agent](https://www.demobites.com/docs/bites/manage-from-your-agent)
+
 ## What's in this repository
 
 | Directory | What it is |
 |---|---|
 | `launcher/` | The `npx demobite` entry — environment checks, skill install, login |
-| `skill/` | The DemoBites recorder skill for Claude Code (staging, preview, approval flow) |
+| `skill/` | The DemoBites recorder skill for coding agents (staging, preview, approval flow) |
 | `recorder/` | The open recorder — same filming engine, no account, ends at a polished `demo.mp4` |
 | `scripts/` | The shared engine: filming, clock calibration, cutting |
 
@@ -43,7 +91,7 @@ does the rest.
 
 The `recorder/` directory is a standalone skill: the same real-browser filming,
 hover-anchor clock calibration and camera work, delivering a finished, styled
-`demo.mp4` on your disk — no account, no upload. Point Claude Code at it and
+`demo.mp4` on your disk — no account, no upload. Point your coding agent at it and
 film. When you want narration, zooms, an editable timeline and hosting, the
 sibling skill in `skill/` is one login away.
 
@@ -57,7 +105,7 @@ is cryptographically tied to a public commit in this repository.
 ## Requirements
 
 - Node 18+
-- [Claude Code](https://claude.com/claude-code) — the recorder is agent-driven
+- A coding agent — [Claude Code](https://claude.com/claude-code), Cursor, or Codex; the recorder is agent-driven
 - Google Chrome (recommended; films with the real browser) — otherwise
   Chromium is downloaded on first take
 - ffmpeg (`brew install ffmpeg` on macOS)

package/launcher/index.mjs

@@ -49,8 +49,8 @@ if (chromePaths.some((p) => fs.existsSync(p)) || hasBin("google-chrome")) ok("Go
 else warn("Google Chrome not found — the recorder will download Chromium on first take");
 if (hasBin("ffmpeg")) ok("ffmpeg");
 else warn("ffmpeg not found — install it (macOS: brew install ffmpeg) before recording");
-if (hasBin("claude")) ok("Claude Code (the agent that drives the recorder)");
-else warn("Claude Code not found — install it from https://claude.com/claude-code, the recorder is agent-driven");
+if (hasBin("claude")) ok("Claude Code (drives the recorder; MCP registers automatically)");
+else warn("Claude Code not found — using Cursor or Codex? They drive the recorder too; MCP setup prints below");
 
 // ── 2. Install / update the skill ──────────────────────────────────────────
 const skillsDir = path.join(os.homedir(), ".claude", "skills");
@@ -139,7 +139,8 @@ Publishing always shows you a preview to approve first.
 const cfg = readCfg();
 if (cfg?.api_key) registerMcp(cfg, { quiet: true });
 console.log(`
-Ready. Everything is agent-driven — open Claude Code in your project and ask:
+Ready. Everything is agent-driven — open your coding agent (Claude Code,
+Cursor, Codex) in your project and ask:
 
     "Record a demo of <your flow> and upload it to DemoBites"
     "Create a release with my latest bites and add Spanish"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "demobite",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "The DemoBites agentic recorder \u2014 you prompt, it films a real browser, and DemoBites turns the take into an editable demo bite.",
   "bin": {
     "demobite": "launcher/index.mjs"