Repository navigation
@genclass/mcp 0.2.2: the agent waits for a yes, the runtime is pinned, GenClass.init() is behind the dev check - #167
Merged
Conversation
…, GenClass.init() is behind the dev check The skill (the plugin's, the root copy and the one `init` writes) and the server's instructions now show each action and wait: running or adding what genclass_setup prints (the tool's answer opens with that step), npx playwright install chromium, hosted: true, and a fix or a test when the user only asked what broke. The regression test is offered, not added. genclass_scan's "Next" line and its missing-Chromium message say the same, and the skill's terminal line passes --local, so it stops instead of falling back to the hosted check. buildwithclaude's maintainer reads the skill at the pinned commit and closed #636, #627 and #490 over these steps. genclass_scan's npx and genclass_setup's install line name the exact runtime, as do the skill, llms-install.md and this package's READMEs: RUNTIME_VERSION in src/clients.ts, written by `npm run sync` from packages/runtime/package.json (the build the e2e runs), checked by test/manifests.test.ts, with release-mcp.yml stopping if npm does not serve it. What a server runs or an agent copies pins like a script tag; the text still names the line, and the runtime's own docs keep @beta for people. genclass_setup printed `const rt = GenClass.init();` outside the development check, so following it put the runtime in production builds, sending anonymous diagnostics from public hosts by default. It now prints both lines inside the check, and a production build drops the runtime (a test bundles the printed lines with esbuild; Vite and Next.js 15 in RESULTS.md section 26). The READMEs, llms-install.md and AGENT.md show the same block, and say what moving GenClass.init() out of the check would do. Version bump with `npm run sync -w @genclass/mcp`, and the workspace entry in package-lock.json (it still said 0.2.0). Checked: typecheck, build, vitest 162 passed (12 files); the agent-loop e2e in Chromium on this repository's runtime and on the published 0.3.0-beta.5 tarball (agent.js and index.js byte-identical); the built server's genclass_scan through the pinned npx with and without Playwright; `init` in a fresh project; the tarball and the assembled plugin repository; plugin validate --strict and the MCP bundle. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e, and note the pinned runtime in AGENTS.md Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…o longer says fix unasked Without Playwright the scan's command also runs npm i -D playwright, which edits package.json and the lockfile, so the skill, the instructions, the scan's message and the docs say so. The report's next step makes the fix conditional on the user having asked for one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
genclass_setupprints,npx playwright install chromium,hosted: true, and a fix or a test when the user only asked what broke.initwrites the same skill.genclass_scan's npx andgenclass_setup's install line name the exact runtime this release was tested with (RUNTIME_VERSION, kept equal topackages/runtimebynpm run sync). The runtime's own docs keep@beta. A runtime version bump now fails the next MCP CI run until someone runs sync; AGENTS.md says so.GenClass.init()is now printed behind the development check, so a production build drops the runtime (RESULTS.md section 26).release-mcp.ymlstops a release if npm does not serve the pinned runtime.@genclass/mcp0.2.2, synced.Why
buildwithclaude's maintainer reads the skill at the pinned commit and closed #636, #627 and #490 over these steps. Someone who only asked a question should not get a changed project.
What this costs
Plugin installs no longer put the runtime in production, so they no longer produce production diagnostics or dashboards unless someone chooses that. The waits are instructions to the agent, not code locks.
Checked
Typecheck, build, vitest 162 passed. Agent-loop e2e on this repo's runtime and on the published 0.3.0-beta.5 (explore 5/6 on the buggy page, no race on the fixed page).
genclass_scanthrough the pinned npx,init, the tarball, the assembled plugin repo,plugin validate --strict.Not run: Turbopack; the runtime's vitest, since only its README changed there.
🤖 Generated with Claude Code