claude-plugin README: document installing from a fork (AGENT_BOUNDARY_PACKAGE_SPEC) - #1
Open
berekuk wants to merge 1 commit into
Open
claude-plugin README: document installing from a fork (AGENT_BOUNDARY_PACKAGE_SPEC)#1berekuk wants to merge 1 commit into
berekuk wants to merge 1 commit into
Conversation
…_PACKAGE_SPEC) The plugin and the Python package in the protected runtime are two layers refreshed separately, and bin/bootstrap installs the package from the public repo's pinned revision regardless of which marketplace the plugin came from — so a fork user who only re-points the marketplace still runs upstream code. Name the override (AGENT_BOUNDARY_PACKAGE_SPEC, passed to `uv pip install` verbatim), where to set it so hooks inherit it (settings.json `env`), and how to refresh each layer; note that AGENT_BOUNDARY_SOURCE_DIR is for lockfile- carrying workspaces, not a standalone checkout. Co-Authored-By: Claude Fable 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
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.
Installing the plugin from a fork takes two steps, and the second is easy to miss: re-pointing the marketplace only changes the hook wiring, while
bin/bootstrapkeeps installing the Python package into the protected runtime from the public repo's pinned revision.AGENT_BOUNDARY_PACKAGE_SPECis the override for that, but it was only mentioned in a comment insidebootstrap.This adds an "Installing from a fork" subsection to the plugin README, right after the paragraph that explains where the runtime's package comes from:
/plugin update …vsbin/bootstrap install);AGENT_BOUNDARY_PACKAGE_SPECwithfile://andgit+https://…@branchexamples, and where to set it so hook processes inherit it (theenvblock of usersettings.json; a plain terminal needs it passed explicitly);AGENT_BOUNDARY_SOURCE_DIRstill wins when set and is for lockfile-carrying workspaces, not a standalone checkout.Docs only. Verified the described setup end-to-end on macOS: directory marketplace from a fork checkout + the env var in
settings.json, runtimedirect_url.jsonpointing at the checkout, and a fresh session's shell seeing the variable.🤖 Generated with Claude Code