Decouple coily and agent-guard #6
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-05-22T13:20:24Z - https://github.com/coilysiren/coily/issues/322
Decouple coily and agent-guard
Problem. coily and agent-guard currently depend on each other, and they should not. coily delegates its PreToolUse hook routing to agent-guard. agent-guard carries a
coilyRoutestable named after coily. coily carriesTestApplyHookHandoffTrim_AlignedWithAgentGuardHookTable, which hand-mirrors agent-guard's table and fails CI if the two drift. The result: a routine coily routing change, like adding thecoily pkg nixpassthrough (coilysiren/coily#320, coilysiren/agent-guard#29), forces an edit to agent-guard.Kai's rule: coily and agent-guard are separate things and must never depend on each other.
Goal. coily owns a fully self-contained routing and recovery surface. agent-guard carries zero coily-specific code. The AGENTS.md "Coily vs agent-guard Framing" section is rewritten to describe the decoupled design.
Fan-out. Build bottom to top:
coilyRoutesand all coily-specific code. Blocked on #323.Note on the in-flight nix change. coilysiren/coily#320 and coilysiren/agent-guard#29 just added a
nixrow to both tables. The coily child must preservenixrouting inside coily's new self-contained surface. The agent-guard child removes the agent-guard copy along with the rest ofcoilyRoutes.This is a tracking issue. It is not dispatched - the children are.