Documentation unstable
The pages as they stood in the newest build of the default branch. Every link here stays in unstable. The current documentation is elsewhere.
chock run from the command line to the exit code: the session log, devices, getting the work back out of the workspace, cost, the task list, and chock doctor.
what is not built yet, and the faults Chock is known to have. ## Using a session
Using
the 23 tools, what each one asks for, how every call is gated, and provide_tool for a program the session has not got.
nix_eval and nix_build, what a build may fetch while it runs, mirrors, and where your flake inputs come from.
what a session asks a person, how the question reaches them, where an approved apply lands, and what happens when nobody is there.
driving Chock from an editor over the agent client protocol: both versions, what the editor is told, and the four things Chock will not take from one.
spawn_agent, the depth and width limits, the budget slice, and a spawn that waits or carries on.
the notes an agent keeps between sessions, their bounds, and the hazard a writable memory directory is.
the three layers of AGENTS.md, why they are never flattened, and how they differ from a note.
Agent Skills read off disk, the three layers and their defaults, and the four things a skill may never do. ## Configuring a project
Configure
config.zon, provider instances, how much context a model holds, and every block of the project's own chock.zon.
how a rule is read: the fields, the decisions, precedence, wildcards, deny_read, and the ratchet an agent cannot lift.
the reference for every action name a rule can carry, and what Chock ships for each.
the web search engine: the three kinds, the key in the credential store, and the org ceiling over both.
giving a tool call a secret the agent never sees: the mapping, the action every use is asked under, and what the log records.
the org policy bundle, the budget, the subagent limits, and the limits and nix ceilings. ## Security
Security
what the sandbox is built against, one attack walked end to end, and what is not covered.
the layers a tool call runs inside, the workspace, the mount tree, the limits, device passthrough, what macOS gives, and what chock doctor reports.
the red team harness, what two models proved, and the one boundary that moved. ## Running the tooling
Operate
chock daemon, chock serve, the control protocol, and handing a session over with chock detach.
the dev shell, a container image instead, where a compiler writes, and every path in a tool call's mount tree.
chock login, where a credential goes, where a lookup goes, and why there is no argument and no environment variable for one. ## Extending Chock
Extend
tools you supply yourself, as WebAssembly, and how each one is gated.