docs · adapters
Crush#
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.
Charm's Crush has no native ACP mode (upstream ACP support was still an open issue with draft PRs as of 2026-10-23); it integrates through an unofficial third-party crush-acp adapter binary that speaks the protocol on its behalf. Hekma ships no such adapter — treat the adapter as its own supply-chain decision, with the unofficial status on top.
Register#
The adapter binary below is the unofficial third-party wrapper, not Crush itself and not anything Hekma distributes:
hekma agent config set my-crush acp.command "crush-acp"
hekma agent register my-crush --kind acp
hekma agent start my-crushPass whatever additional arguments your chosen adapter documents via acp.args.
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, 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 (Crush supports custom providers) — a hypothesis, unproven here | characterized |
| Context usage | an agent-reported usage_update would surface under acp_context_usage — context-grain, never billed; whether the adapter reports one is unverified here | characterized |
Validation status. Upstream: third-party adapter, unofficial (Crush's own ACP support is still an open upstream issue, and the adapter is an independently maintained wrapper outside Hekma's). Evidence: characterized — upstream documentation, dated 2026-10-23, NOT run-verified here. Nothing pinned.
PATH requirement#
The launch command is the bare word crush-acp, resolved through the PATH of the environment hekma runs in. Hekma does not bundle, install or pin the adapter (or Crush) — install whichever adapter you choose, vet it yourself, keep it on the PATH. A start whose crush-acp cannot resolve fails with the engine's launch-failure diagnostic naming the executable.
Re-validation duty#
An unofficial adapter over an upstream without native ACP support is the least stable integration in this gallery; every characterization here is a snapshot by design. Re-validate your adapter + Crush combination 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
—.