Published · npm latest
Cursor hard write.
Patch over 4.5.6. Project .cursor/hooks.json can deny agent
Write / StrReplace when trusted. Not every Cursor path—
Shell, Tab, and human edits still rely on required CI. No required config migration.
Upgrade
Get 4.5.7
Restart Cursor so .cursor/hooks.json loads (Hooks settings / reload).
Doctor reports hard as unverified until the host trusts the hook.
What changed
In plain English.
Cursor preToolUse hard path
Install writes .cursor/hooks.json with matcher
Write|StrReplace, failClosed: true, and
--hook --hook-repair. Sibling hooks are preserved on merge.
Honest matrix
Cursor is hard-write: true only for listed ops.
Codex and OpenCode stay advisory at local write. Required CI
--strict-merge remains the shared merge boundary.
Repair envelope only
Hooks may emit a repair JSON envelope. Write
updated_input reinjection is not claimed on Cursor—
agent_message + retry is the supported path.
Payload mapping
Hook runtime maps Cursor contents → content and
StrReplace → Edit, then returns
{ permission: "deny", agent_message } on block.
Honesty notes
What did not change
- Write gate and CI fail-closed semantics for value layer edges
- Binary gate—no numeric architecture score, no LLM pass/fail
- No new skill names; no new ArkRules sensors
- Codex / OpenCode remain advisory at local write
-
Shell, Tab, and human IDE edits are not covered by Cursor hard write—keep a
required status running
arkgate-check --strict-merge
Maintainer source: docs/releases/4.5.7.md ↗