Install

Claude Code Tested

The command:

chock install --selection <code> --client claude-code --apply

Replace <code> with your selection code. Get it from the builder.

With --apply, chock runs these steps for Claude Code:

1. claude plugin marketplace add ~/.chock/marketplace/claude-code

2. claude plugin install chock-guardrails@chock-local

Both commands are safe to repeat. The plugin loads in place from the directory: restart the Claude Code session, or run /reload-plugins in it, to pick up a rebuild.

To remove it:

1. claude plugin uninstall chock-guardrails@chock-local

Delete the build folder ~/.chock/marketplace/claude-code/claude/chock-guardrails: chock bundle status lists a build for as long as its folder exists.

Only if no other chock build for this agent is still installed (every chock build made with the marketplace name chock-local shares it, so removing it takes their registration too): claude plugin marketplace remove chock-local. Otherwise leave it registered.

Problem installing for Claude Code? Report it

Cursor Tested

The command:

chock install --selection <code> --client cursor --apply

Replace <code> with your selection code. Get it from the builder.

With --apply, chock runs these steps for Cursor:

Cursor loads ~/.cursor/plugins/local/chock-guardrails as a local plugin: run "Developer: Reload Window" (or restart Cursor), then check it under Customize. There is no command to run.

To remove it:

Delete the build folder ~/.cursor/plugins/local/chock-guardrails (Cursor loads it from there), then run "Developer: Reload Window" (or restart Cursor). chock bundle status lists a build for as long as its folder exists.

Problem installing for Cursor? Report it

Codex Tested

The command:

chock install --selection <code> --client codex --apply

Replace <code> with your selection code. Get it from the builder.

With --apply, chock runs these steps for Codex:

1. codex plugin marketplace add ~/.chock/marketplace/codex

Then install chock-guardrails from the chock-local marketplace in /plugins, and review and trust its hooks in /hooks: until you do, they do not run.

To remove it:

Uninstall chock-guardrails in /plugins, then delete the folder ~/.chock/marketplace/codex/codex/chock-guardrails.

Problem installing for Codex? Report it

GitHub Copilot Tested

The command:

chock install --selection <code> --client copilot --apply

Replace <code> with your selection code. Get it from the builder.

With --apply, chock runs these steps for GitHub Copilot:

1. copilot plugin marketplace add ~/.chock/marketplace/copilot

2. copilot plugin install chock-guardrails@chock-local

VS Code finds plugins the Copilot CLI installed. Without the CLI, add the plugin folder to your VS Code user settings yourself:

{
  "chat.pluginLocations": {
    "~/.chock/marketplace/copilot/claude/chock-guardrails": true
  }
}

To remove it:

copilot plugin uninstall only disables the plugin (seen in a live run): it removes nothing from disk and leaves the marketplace registered.

1. copilot plugin uninstall chock-guardrails@chock-local

Delete the build folder ~/.chock/marketplace/copilot/claude/chock-guardrails: chock bundle status lists a build for as long as its folder exists.

Only if no other chock build for this agent is still installed (every chock build made with the marketplace name chock-local shares it, so removing it takes their registration too): copilot plugin marketplace remove chock-local. Otherwise leave it registered.

In VS Code, remove the "~/.chock/marketplace/copilot/claude/chock-guardrails" entry from chat.pluginLocations in your user settings (chock does not edit them).

{
  "chat.plugins.enabled": true,
  "chat.pluginLocations": {
    "~/.chock/marketplace/claude-code/claude/chock-guardrails": true
  }
}

Problem installing for GitHub Copilot? Report it

Devin Tested

The command:

chock install --selection <code> --client devin --apply

Replace <code> with your selection code. Get it from the builder.

With --apply, chock runs these steps for Devin:

On Windows, devin plugins install --local creates a symbolic link, so it needs Developer Mode (Settings > System > For developers) or an elevated shell; otherwise it fails with "os error 1314: A required privilege is not held by the client".

1. devin plugins install --local ~/.chock/marketplace/devin/chock-guardrails

The plugin is linked in place: a rebuild applies from the next Devin session.

To remove it:

1. devin plugins remove chock-guardrails --local

Delete the build folder ~/.chock/marketplace/devin/chock-guardrails: chock bundle status lists a build for as long as its folder exists.

Problem installing for Devin? Report it

Grok Tested

The command:

chock install --selection <code> --client grok --apply

Replace <code> with your selection code. Get it from the builder.

With --apply, chock runs these steps for Grok:

1. grok plugin install ~/.chock/marketplace/grok/chock-guardrails --trust

Plugins are off in grok until enabled, and chock does not edit grok's config: run grok plugin list for the name grok gave this plugin (chock expects chock-guardrails, its folder name; the docs do not say how a plugin with no plugin.json is named), then grok plugin enable <name>, or add it to enabled under [plugins] in ~/.grok/config.toml, or press Space on it in the Plugins tab. Re-run the install command after a rebuild.

To remove it:

Run grok plugin list for the name grok gave this plugin, then grok plugin uninstall <name>.

Delete the build folder ~/.chock/marketplace/grok/chock-guardrails: chock bundle status lists a build for as long as its folder exists.

Problem installing for Grok? Report it

goose Tested

The command:

chock install --selection <code> --client goose --apply

Replace <code> with your selection code. Get it from the builder.

With --apply, chock runs these steps for goose:

goose discovers ~/.agents/plugins/chock-guardrails as a user plugin, in every project: start a new goose session. There is no command to run (goose plugin install takes a git URL only). To turn it off, add chock-guardrails to disabledPlugins in ~/.config/goose/settings.json.

To remove it:

Delete the build folder ~/.agents/plugins/chock-guardrails (goose discovers it there), then start a new goose session. chock bundle status lists a build for as long as its folder exists.

Optional tidy-up: delete the chock-guardrails entry in the plugins list of goose's config.yaml. goose works without this step.

Problem installing for goose? Report it

Antigravity Tested

The command:

chock install --selection <code> --client antigravity --apply

Replace <code> with your selection code. Get it from the builder.

With --apply, chock runs these steps for Antigravity:

1. agy plugin install ~/.chock/marketplace/antigravity/chock-guardrails

Antigravity 2.0 and the IDE read plugin folders from ~/.gemini/config/plugins/ instead: copy ~/.chock/marketplace/antigravity/chock-guardrails there. Its hooks name ~/.chock/marketplace/antigravity/chock-guardrails by absolute path (Antigravity documents no plugin-root variable), so keep that folder where it is; re-run the install command after a rebuild.

To remove it:

Close Antigravity, delete the folder ~/.gemini/config/plugins/chock-guardrails, then reopen Antigravity. Checked on Windows.

Optional tidy-up: delete the build copy ~/.chock/marketplace/antigravity/chock-guardrails. Antigravity does not read it.

Problem installing for Antigravity? Report it

OpenHands Untested

Evidence wanted for OpenHands. Chock has not seen OpenHands run the plugin yet. The command still builds the plugin. If you use OpenHands, you can help: run it and share what happens in agentseam issue #181.

The command:

chock install --selection <code> --client openhands

Replace <code> with your selection code. Get it from the builder.

Then, in OpenHands:

OpenHands loads a local plugin when it starts: run openhands --plugin ~/.chock/marketplace/openhands/chock-guardrails, or add "~/.chock/marketplace/openhands/chock-guardrails" to sources under [plugins] in ~/.openhands/config.toml (chock does not edit it). Its hooks name ~/.chock/marketplace/openhands/chock-guardrails by absolute path (OpenHands documents no plugin-root variable), so keep that folder where it is; a rebuild applies from the next start.

To remove it:

Removal steps not verified for OpenHands yet. What you see when you remove it is wanted in agentseam issue #181.

Stop passing --plugin ~/.chock/marketplace/openhands/chock-guardrails, and remove "~/.chock/marketplace/openhands/chock-guardrails" from sources under [plugins] in ~/.openhands/config.toml if you added it (chock does not edit it).

Delete the build folder ~/.chock/marketplace/openhands/chock-guardrails: chock bundle status lists a build for as long as its folder exists.

Problem installing for OpenHands? Report it

Kimi Code Untested

Evidence wanted for Kimi Code. Chock has not seen Kimi Code run the plugin yet. The command still builds the plugin. If you use Kimi Code, you can help: run it and share what happens in agentseam issue #135.

The command:

chock install --selection <code> --client kimi-code

Replace <code> with your selection code. Get it from the builder.

Then, in Kimi Code:

Kimi Code installs plugins from its TUI only, and chock does not drive it: in Kimi Code run /plugins install ~/.chock/marketplace/kimi-code/chock-guardrails, then /reload (or /new). Kimi copies the plugin to $KIMI_CODE_HOME/plugins/managed/chock-guardrails/ and runs that copy, so after a rebuild install it again. The plugin applies to every project you open (Kimi has no project-level plugin scope); /plugins disable chock-guardrails turns it off.

To remove it:

Removal steps not verified for Kimi Code yet. What you see when you remove it is wanted in agentseam issue #135.

Problem installing for Kimi Code? Report it

Factory Droid Untested

Evidence wanted for Factory Droid. Chock has not seen Factory Droid run the plugin yet. The command still builds the plugin. If you use Factory Droid, you can help: run it and share what happens in agentseam issue #184.

The command:

chock install --selection <code> --client factory-droid

Replace <code> with your selection code. Get it from the builder.

Then, in Factory Droid:

Run these from the root of the project the plugin is for: --scope project records it in that project's Droid settings. The marketplace is local to this machine; chock publishes nothing.

1. droid plugin marketplace add ~/.chock/marketplace/factory-droid/chock-local

2. droid plugin install chock-guardrails@chock-local --scope project

Droid names a local marketplace from its source; if droid plugin marketplace list shows a name other than chock-local (a --dest folder named otherwise), install chock-guardrails@<that name>. Droid copies the plugin into its cache: after a rebuild run droid plugin marketplace update and droid plugin update chock-guardrails@chock-local --scope project, then start a new session.

To remove it:

Removal steps not verified for Factory Droid yet. What you see when you remove it is wanted in agentseam issue #184.

Run these from the root of the project the plugin was installed for.

1. droid plugin uninstall chock-guardrails@chock-local --scope project

Delete the build folder ~/.chock/marketplace/factory-droid/chock-local/droid/chock-guardrails: chock bundle status lists a build for as long as its folder exists.

Only if no other chock build for this agent is still installed (every chock build made with the marketplace name chock-local shares it, so removing it takes their registration too): droid plugin marketplace remove chock-local. Otherwise leave it registered.

Problem installing for Factory Droid? Report it