Chock.sh Build your plugin

Agents

Cline

Cline and chock: install methods and steps, what it can enforce, and the evidence behind it.

Install methods: none. Agentseam tier block, grade best-effort before a tool runs.

Install methods

  • Not wired by chock sync: this agent runs one executable per hook event from a hooks folder, and chock sync writes JSON or TOML hook files, so it needs a dispatcher chock does not ship yet.

Evidence wanted

Chock has not seen this agent run its hooks yet. If you use it, you can help: agentseam issue #178

What it can enforce

Tier
block
Grade before a tool runs
best-effort
Fail mode before a tool runs
open
Basis
vendor-docs
Recorded
2026-10-11

Events

EventCan blockCan rewriteFail mode
pre_toolyesnoopen
post_toolnonoopen
prompt_submitnonoopen
session_startnonoopen
stopnonoopen

Ask support

The engine records no ask claim for this agent.

Hook timeout

The engine records no timeout for this agent.

Test status

  • No row in the engine's list of live tests for this agent.

Known limits

Adapted (D2b): Cline runs one executable per event from .clinerules/hooks/, named exactly after the event, and reads {"cancel": true, "errorMessage"} on stdout as a block. agentseam speaks that cancel object (grammar G7) at PreToolUse only, the one event whose cancel is read before the tool runs on both hosts. The two hosts name the same file differently in the payload: the VS Code extension sends hookName PreToolUse, the CLI/SDK sends its own event name tool_call; both are mapped, and every payload carries clineVersion, which no other vendor sends. Fail-open on both hosts: a hook that times out, crashes or prints something other than JSON is logged and the tool runs. Escalate and transform degrade to a block: hooks cannot ask the user, and the documented contract says a hook cannot modify the tool's parameters. UserPromptSubmit and TaskStart are detect only: the CLI runs them detached, so their cancel is never read there. PostToolUse is detect only: its cancel stops the task after the tool already ran. run_commands' command list arrives as JSON text in preToolUse.parameters and is read as one command per line; apply_patch's target path lives inside the patch text and is not extracted. Install writes .clinerules/hooks/<Event> with a #!/bin/sh shebang and the executable bit, read by both hosts (.cline/hooks/ is read by the CLI/SDK only), and refuses to overwrite a hook file it did not write: Cline runs one file per event name per directory. Hooks must be enabled in the VS Code extension's settings, and run on macOS and Linux only. Tool calls executed inside a provider's own agent loop (Claude Code, Codex as providers) never reach the hook pipeline, per the maintainers on cline/cline#13277. Instruction files reach it through AGENTS.md. Evidence wanted (to test or overturn this row): https://github.com/open-coder-ai/agentseam/issues/178

Built from engine 5a4b6287a46e and catalog 1e60d211c1bb.