Repository navigation
Grok Build support: one source, two tools - #11
Merged
Merged
Conversation
Grok Build loads these plugin folders as they are, since it reads .claude-plugin/plugin.json, but it only finds a marketplace at .grok-plugin/marketplace.json. The script derives that file from the Claude manifest, so there is one source and no hand-kept copy to drift; --check exits 1 when the committed file is stale. Refs: #10
People on Grok Build could read the plugins but had no one-step install from a checkout. --grok keeps --only, --list and --uninstall and swaps the claude calls for grok ones. A local marketplace registers under its directory name, so the script finds it by path; a full --uninstall removes that marketplace, which removes exactly its plugins. Grok uninstalls plugins by name only, and another pack can ship a plugin with the same name, so --uninstall --only skips a name that is also installed from somewhere else rather than remove the wrong copy. Refs: #10
Claude Code CI alone cannot tell us when a plugin stops loading in Grok Build. The new job fails when the generated Grok manifest drifts from the Claude one, runs grok plugin validate on every plugin, and installs them all into a clean GROK_HOME from the checkout. Refs: #10
The README and QUICK_START only told Claude Code users how to install. The README now has an Install in Grok Build block after the Claude one, with the marketplace commands, a direct install of one plugin folder, and ./setup.sh --grok. QUICK_START had no plugin install block, so its short Grok block sits at the end of Step 1 and points to the README for Claude Code. Both warn that libreuiux-hooks is not yet verified in a live Grok session, and the README warns that grok uninstalls by name while 67 names are shared with sibling packs. Refs: #10
The 2.0.0 release fixed a marketplace name that collided with wshobson/agents, three plugins nobody could install, hooks that never ran and missing upstream credit, but the record was spread across the CHANGELOG and commits. LEDGER.md gives each crack one row with its evidence, grade and seal, adds the Grok same-name uninstall crack this branch seals, and lists the cracks still open (#6, #7, #8, the broken link count, the hooks runtime in Grok). The README links it from Feedback. Refs: #10
Records the Grok marketplace and CI job, ./setup.sh --grok, and the kintsugi ledger, so the next release notes start from them. Refs: #10
Grok 1.0.44 registers a marketplace added from GitHub under the repo name, not the manifest name: ServiceNow/sdk (manifest servicenow) installs as plugin@sdk or plugin@ServiceNow/sdk, while plugin@servicenow fails with Unknown marketplace. Claude Code lines keep the manifest name, which is right there. Refs: #10
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.
Stacked on #9; merge that first.
Grok Build reads these plugin folders as they are (it loads
.claude-plugin/plugin.json), but it only finds a marketplace at.grok-plugin/marketplace.json. This PR adds that file, generated from the Claude manifest, plus CI, docs, a--grokinstaller flag and the kintsugi ledger. One source serves both tools; nothing is removed.What changed
scripts/sync-grok-manifest.pywrites.grok-plugin/marketplace.jsonfrom.claude-plugin/marketplace.json(71 plugins);--checkexits 1 when the committed file is stale. Same script as the rest of the wave, unchanged..github/workflows/validate.ymlgains the sharedgrokjob, unchanged: manifest drift check, install the Grok Build CLI,grok plugin validateon every plugin, install all 71 into a cleanGROK_HOMEfrom the checkout. The existingpluginsjob is unchanged.setup.sh --grokinstalls through thegrokCLI instead ofclaude, with the same--only,--listand--uninstallbehavior. A local marketplace registers under its directory name, so the script finds it by path; a full--uninstallremoves that marketplace, which removes exactly its plugins.--grokpasses--trust, and the usage header says so.--scopeis Claude Code only and prints a note.design-masteryis also in design-mastery-claude-code, andgrok plugin uninstall <name>removes one copy by name. In a cleanGROK_HOME, withcode-documentationinstalled from this checkout and then from a game-dev checkout, it removed this pack's copy. So--uninstall --onlyskips a name that is also installed from somewhere else (transcript below), and the README says to remove a pack with./setup.sh --grok --uninstall.### Install in Grok Buildright after the Claude Code install (marketplace commands, a directgrok plugin install HermeticOrmus/LibreUIUX-Claude-Code#plugins/design-mastery,./setup.sh --grok, the shared-name note, and a line thatlibreuiux-hooksuses a format Grok supports but is not verified in a live Grok session). QUICK_START has no Claude Code plugin install block (it starts from a CLAUDE.md template), so its short Grok block sits at the end of Step 1 and points to the README for Claude Code. Everything else stays.LEDGER.md: 16 cracks the 2.0.0 release found and sealed (hallmarked with the release PR and its CHANGELOG line or commits), 1 sealed here, and 5 open: Write the two intermediate examples the README links to #6, Write the two advanced guides the README links to #7, Package the root .claude UI commands and synthesis-master agent as a plugin #8, the 48 broken relative links (Menu atomlink-check-ci), and the hooks runtime in Grok. Linked from the README Feedback section.[Unreleased]: Grok Build support,--grok, the ledger.The direct subfolder install already works against
main.grok plugin marketplace add HermeticOrmus/LibreUIUX-Claude-Codeneeds this merged, sincemainhas no.grok-plugin/yet. For the ledger, the released 2.0.0 was installed from GitHub into a clean Claude Code config again: 71 of 71 enabled.Verification
grok 1.0.44, Claude Code 2.1.286. Every Grok install ran in a fresh
GROK_HOME=$(mktemp -d). Grok also lists the machine's Claude Code marketplaces read-only; that is expected and nothing was written to them. Paths are shortened to<worktree>and$GROK_HOME.Manifest check and grok plugin validate
Clean GROK_HOME install from the worktree, list, details
claude plugin validate, setup.sh --grok (--list, --only, --uninstall)
Same-name skip: --uninstall --only leaves a code-documentation installed from elsewhere alone
Diff scan: em dashes and personal data
Closes #10
🤖 Generated with Claude Code