[_superposition_]

I think it all comes down to tight, context efficient, deterministic feedback loops. Pre commit hooks work well for this type of thing. Ideally I think a set of those hooks should run on every file edit, however I haven't gotten around to testing something like that yet.

[everforward]

YMMV but I wouldn’t personally reach for either. They’re both out of band so you have to deal with pulling input back into the context and what to do if one side won’t communicate right.

File edits are just tool calls under the hood. If you’re using a decent agent then you should be able to override or extend the filesystem tools. If you’re on ACP, file reads/writes get proxied to your ACP client and you can inject your hooks there.

It’s pretty trivial to implement, this is well within the bounds of things most agents implement (for open source agents anyways, no idea how to extend Claude Code or Codex these days).