FAQ
Answers about chock: what the labels mean, what the command does and what it cannot do.
Common
What is chock?
A catalog of guardrail policies for AI coding agents, and the engine that turns a picked set of them into one plugin for your agent. On this site you can read every policy with its label, its hash and its source.
Is this a security boundary?
No. It adds friction. It stops common mistakes and makes risky actions visible. A policy's label tells you whether it blocks, asks, warns or only advises.
Do you collect anything about me?
Nothing personal. Your selection lives in the link after the #, which browsers never send to a server. There is no cookie and no account. The site counts a few actions, such as copying a command, and no page views. It stores no IP address or id with them. The Security page lists them. With Global Privacy Control or Do Not Track on, it counts nothing. The chock command line tool sends nothing.
Is it free?
Yes. The engine, the catalog and this site are open source under Apache-2.0.
What are general agents?
Agents that act for a person or a business. We are still designing their guardrails, so there is nothing to install yet.
Coding agents
Which coding agents does this work with?
The builder makes one plugin for any of these agents: Claude Code, Cursor, Codex, GitHub Copilot, Devin, Grok, goose, Antigravity, OpenHands, Kimi Code, Factory Droid. Agents marked tested install with one command. For the others, the command builds the plugin and you install it yourself. See Agents.
What does "blocks / asks / warns / advisory" mean?
It is the policy's label. It says what happens when the policy fires. Blocks: the agent refuses the action. Asks: it stops and asks you. Warns: the action goes ahead with a warning. Advisory: the agent reads the text, and nothing stops a violation.
How do I change or remove the plugin?
To change what is installed, ask first, then re-run chock install --selection YOUR_CODE --apply with a new selection: it replaces the plugin in one step. To remove everything, use your agent's own plugin uninstall and marketplace removal, then delete the build folder. The Install page lists them for each agent.
Can I use the plugins without installing chock?
Yes, with the per-policy marketplace. It carries one plugin per policy and is republished with every chock release. The machine needs Python 3.11+, git and a bash, and no chock. The Agents page links the repository for each agent that has one. Add it, or mirror it into your own git server. Install a policy from one place only, never both: each copy runs its own hook.
What does the command do on my machine?
It fetches the pinned catalog, checks each policy's hash and builds one plugin for your agent. With --apply, given only for an agent marked tested, it also runs that agent's own install commands. Without it, the command prints them for you.
Can my team share one selection?
Yes. The builder makes a share link and a selection file. Anyone running the same command gets the same policies, checked against the same pinned commit.
How do I report a wrong block, or anything else?
Use the Report an issue page. It opens the right GitHub issue form for a wrong policy, an install problem, a site problem or a new policy idea, already filled in. For a vulnerability, report it privately: the page links each repository's private advisory form.