Skip to content

docs · adapters

goose#

Unreleased: after 0.11.0. This page is on Hekma's main branch and ships in the next release; Hekma 0.11.0 does not have it.

Block's goose exposes an ACP mode through its goose acp subcommand, so it runs under Hekma's built-in acp kind. The mode is experimental upstream; this entry is characterized from upstream documentation and has not been run-verified here.

Register#

hekma agent config set my-goose acp.command "goose"
hekma agent config set my-goose acp.args "acp"
hekma agent register my-goose --kind acp
hekma agent start my-goose

Honesty table#

The pause and interaction levels are the acp kind's own capability declaration — identical for every ACP agent and proven by the conformance kit against a scripted stand-in; they are not per-agent promises. The metering rows are characterized from upstream documentation, not run-verified here.

Surface	Value	Evidence class
`pause`	`guaranteed` (Linux), `guaranteed` (macOS), `best-effort` (Windows)	`contract-validated`
`interaction`	`guaranteed` (all OSes)	`contract-validated`
Metering source	`self-reported`	`contract-validated`
Billing-grade tokens	`—` — no billing-grade usage in the ledger — tiers attempted: observed: not-configured; sentinel: no-lines-seen; no context usage reported (ACP usage_update is context-grain, never billed). No sentinel emission is documented upstream; the engine-observed tier is plausible (goose providers take base URLs) but unproven — wiring it is an experiment, not a documented integration	`characterized`
Context usage	an agent-reported `usage_update` would surface under `acp_context_usage` — context-grain, never billed; whether this agent reports one is unverified here	`characterized`

Validation status. Upstream: experimental (the ACP mode is an experimental upstream feature). Evidence: characterized — upstream documentation, dated 2026-10-23, NOT run-verified here. Nothing pinned.

PATH requirement#

The launch command is the bare word goose, resolved through the PATH of the environment hekma runs in. Hekma does not bundle, install or pin the goose binary — install it yourself, keep it on the PATH, or give an absolute path. A start whose goose cannot resolve fails with the engine's launch-failure diagnostic naming the executable.

Re-validation duty#

An experimental upstream feature can change or disappear in any release; every characterization here is a snapshot by design. Re-validate against the version you install before relying on agent-specific behaviour — Re-validation states the full duty, including the contract duties that no automated kit can prove.

Read next#

Adapter Gallery: the index this entry belongs to.
Run an ACP agent: registration, configuration and prompts for ACP agents.
Meter token usage: what each metering tier counts, and what stays —.