[MeharPro]

What

A developer who wants only the open-source parts (no account, no token, nothing sent) had three stories that disagreed: the README quick start (which creates a dashboard token by default), a nine-step hand-edit prompt on genclass.dev/start/open-source, and an agent link that init could not write. Now it is two commands, everywhere:

npx @genclass/runtime@beta init --no-telemetry --agent   # the runtime (observe), the dev-only overlay and agent link; no token
npx -y @genclass/mcp@0.2.1 init                           # the MCP server and the genclass skill for Claude Code

• init --agent (bin/lib/plan.mjs, edit.mjs, init.mjs): writes the dev-only agent link next to the devtools line, the same shape for every framework (if (<dev>) import("@genclass/runtime/agent").then((a) => a.connectAgent(genclass)); one if block in the files created for Next.js; plain HTML gets a module script after the tag that loads dist/agent.js from the script URL's directory on localhost and connects GenClass.runtime). remove recognises it, wrapped by a formatter or not, and refuses an edited one. --agent --no-devtools still binds the runtime. Tests: test/install/cli.test.ts "init --agent" (Vite, Next 16, Nuxt 4, Astro, plain HTML, formatter-wrapped removal).
• Docs: an "Open source only, no account" block in both READMEs' quick start, INSTALL.md "How do I set up the open-source parts only?" and the --agent, --sync, --no-network rows, a FAQ entry, AGENT.md, the MCP README; the MCP server's init and genclass_setup now lead with the one command; INSTALL.md is on the current line (beta.5, 0.2.3); docs/adoption/listings/skills.md says where the genclass skill gets listed.
• genclass.dev/start/open-source (telemetry-worker/src/pages.ts): the prompt is the two commands plus the dev-server check (4 steps, 591 words; was 8 steps, 853), every choice is an init flag, and the page says what the developer will see. The site's embedded copy: genclass-dev/genclass-site PR 15.

Checks

• npm run typecheck -w @genclass/runtime and npm run build -w @genclass/runtime pass
• unit tests pass in packages/runtime (1270 passed, 15 skipped), telemetry-worker (361) and packages/mcp (152; INSTALL.md and FAQ.md joined the pinned-launcher sync list)
• no packages/runtime/test/review-*.test.ts was edited
• no model-visible text changed (situation-v2.3); nothing under packages/runtime/src changed
• packages/runtime/CHANGELOG.md "Unreleased (0.3.0-beta.6)" has the entry
• a correct app is not made worse: the agent link is dev-only and inert off loopback hosts, as before; observe is unchanged
• sim/ and demos/ authors did not read each other's code
• no dependency change

Notes for the reviewer

Sequencing. The published beta CLI (0.3.0-beta.4 and beta.5) rejects --agent (unknown option), so the README and the site must not name it before 0.3.0-beta.6 is on npm. Plan: push the pending v0.3.0-beta.5 tag, run its post-publish pins, then merge this PR with the version bumped to 0.3.0-beta.6 and tag it. Draft until then.

Not run: the browser model suite, the install suite's real-framework builds (test/install/frameworks.sh), anything on Azure. A fresh-eyes review (five walkthroughs, two judges) and an adversarial review of this diff ran in the session; the latter's findings, if any, will be pushed here.

---

Generated by Claude Code

🤖 Generated with Claude Code

[MeharPro]

CI note on 4eb75d7: the @genclass/sv e2e job failed once ("guard kit-ts": page.waitForFunction timed out after 20 s waiting for the runtime's fetch wrapper in the SvelteKit fixture) in run 41499482262, while the same job on the same commit passed in run 41499494158. This PR touches nothing under packages/sv (the diff is the runtime CLI's bin/lib, docs, the MCP server's setup text and the worker's start page), and the sv e2e installs the runtime through pnpm and loads it in Chromium against the network, so this is the harness's timing, not the change. Re-ran the failed job once; no fix to port.

---

Generated by Claude Code