feat: ship the grok-bot plugin + gbot-install bin inside the npm package - #47
Closed
ScriptedAlchemy wants to merge 1 commit into
Closed
ScriptedAlchemy wants to merge 1 commit into
ScriptedAlchemy wants to merge 1 commit into
Conversation
🦋 Changeset detectedLatest commit: b444f42 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
…ckage - plugin: package-bound installer `gbot-install` (agent-bundle/install runInstallCli), `agent-bundle prepack` emits plugin/dist as the npm root; bundled deps moved to devDependencies so prepack's AB7014/AB7015 pass - root: files += plugin/dist, bin gbot-install, prepack -> npm run build:plugin (stderr only so `npm pack --json` stays parseable) - CI/release: build the plugin distribution before publint; smoke `gbot-install install cursor` into a scratch HOME after the global install - README: install the plugin from the package instead of a clone
ScriptedAlchemy
force-pushed
the
feat/gbot-install-dist
branch
from
September 15, 2026 06:15
b469294 to
b444f42
Compare
ScriptedAlchemy
added a commit
that referenced
this pull request
Sep 15, 2026
* feat: collapse grok-bot-cli into one root Agent Bundle project (#24) One dispatcher, one CI gate. The generated `gbot` CLI (`dist/bin/gbot.mjs`) replaces the hand-written `src/cli.js`; the nested private `plugin/` project and its `file:..` hatch are deleted. `gbot-install` binds `runInstallCli` to the same npm `dist/` so Codex, Claude Code, and Cursor install the `grok-bot` MCP tools and `talk-to-grok-bot` skill from one package. - Domain JS moves to `src/core/`; #46 exit-code derivation and failure document flattening live in `src/core/codex/contract.js`, and `sendToCodexThread` / `codexStatus` return documents instead of throwing. - `src/cli/**` routes: bots, groups, doctor, history, send, thread (dedicated CLI routes, not MCP projections) and codex status/list-threads/send/queue. - `send`, `codex send`, and `codex status` use `exitCode: 'result'`: one JSON document on stdout with `exitCode`; refusals keep `reason`/`delivery`. - Gateway-backed routes redact thrown error text before the framework prints it, matching the MCP tools and the old `fail()`. - Breaking (pre-1.0 minor): Node >= 22.19.0, command-local options only, `--json` reserved before `--`, failure JSON on stdout, usage errors exit 2. Supersedes #47. * chore: reference #50 in the changeset * fix: address change-risk review of the root collapse - withRedactedErrors keeps the error name and own fields (reason, mode, delivery, envelope) so failure documents still classify; `gbot send` usage refusals report reason "usage" again. - codex list-threads / queue return the flat failure document on stdout (reason "bad-response", "experimental-disabled", ...) instead of letting the framework print a stack trace; shared failureDocumentSchema. - bots list / groups list --json are bare arrays again, as before. - codex queue human output uses the old formatter (formatCodexQueue). - README/changeset: drop the removed --instructions alias, name the on|off narrowing, the `chat` history event, stderr failures for non-send commands, and the gbot vs grok-bot bundle rename. - Tests cover send `--` protection, usage reason, and list-threads bad-response documents. --------- Co-authored-by: Ubuntu <zack@ubuntu-main.local>
Owner
Author
|
Superseded by #50. |
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
1 participant
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.
Summary
npm install --global grok-bot-clinow delivers both halves: thegbotCLI and the Agent Bundle plugin (MCP servergbot_send/gbot_thread+talk-to-grok-botSkill) with a package-bound installer, mirroring cargo-hauler'scargo-hauler-install.plugin/agent-bundle.config.ts:bin: { 'gbot-install': './src/gbot-install.ts' }→runInstallClifromagent-bundle/installbound to the emitted npm root.plugin/package.json:prepack: agent-bundle prepackemitsplugin/dist(artifact + generated manifest +bin/gbot-install.js); bundled deps moved todevDependenciesso the pack gate (AB7014/AB7015) passes;plugin/README.mdadded for the pack inventory.package.json:files+=plugin/dist,bin.gbot-install,build:pluginscript,prepackruns it (stderr-only sonpm pack --jsonstays parseable).publint; after the global install smoke, rungbot-install install cursorinto a scratchHOMEand assert the receipt +plugin.jsonexist.gbot-install; clone-and-build path kept for development.Changeset: patch (additive bin).
Verification
npx agent-bundle prepack --jsoninplugin/→ 0 diagnostics, 22 files validated.npm pack --json→grok-bot-cli-0.3.1.tgz, 36 files; stdout is clean JSON (nested build goes to stderr).publint→ All good.gbot --help,gbot-install --help;HOME=<scratch> gbot-install install cursor --json→state: installed, receipt written;gbot-install doctorexit 0; the installedmcp/mcp-grok-bot-*.mjshandshakes and listsgbot_send, gbot_thread.npm test108/108 (release-config test updated),cd plugin && npm run check11/11.ripwire --quality-delta: regressions 0, gating 0.