bug: agents ignore hooks instructions

[anteqkois]

What happened?

The claude code (and also antigravity) agens everytime ignore the hooks. And then when I ask if the don't forget sth, they appologase and say that they recive hook at session start "MUST i do not ask for confirmation" but the start doing job and forget.

I can't setup this to work. I don't have anythink special in prompt or AGNETS.md or CLAUDE.md, it's simple genric instruciton not related to graf

Minimal reproduction

No response

Plugin version

2.7.5

Platform / client

Claude Code (CLI)

OS + Node version

macOS M1 Sooma 14.5 (23F79); node v24.13.0

Primary language of the analyzed project

TypeScript

Approximate file count of the analyzed project

1000

Relevant logs

[zycaskevin]

I took a quick look at this on the current repo state and I think there are two different failure modes worth separating.

What the plugin currently does:

• hooks/hooks.json has a SessionStart hook and a PostToolUse hook.
• When the graph is stale / a commit is detected, the hook prints an instruction like:
  Knowledge graph is stale. You MUST read .../hooks/auto-update-prompt.md ... Do not ask the user for confirmation — just do it.
• The hook does not itself run the update logic; it relies on the host agent/model to follow that printed instruction.

I reproduced the hook trigger condition with a tiny git repo containing:

.understand-anything/config.json      # {"autoUpdate": true}
.understand-anything/meta.json        # old gitCommitHash
.understand-anything/knowledge-graph.json

and the SessionStart command does emit the expected “MUST read ... Do not ask for confirmation” message.

So the next diagnostic split is:

1. If you do not see that [understand-anything] ... message at session start / after git commit: likely hook installation, plugin-root, event support, or the autoUpdate/metadata conditions are not being met.
2. If you do see the message but Claude Code / Antigravity continues without running the update: the hook is firing, but the implementation is relying on a prompt instruction as the enforcement mechanism. That is inherently weaker than making the hook/command do the deterministic preflight work itself.

For a minimal repro, the most useful extra data would be:

cat .understand-anything/config.json
git rev-parse HEAD
cat .understand-anything/meta.json
# then: whether the `[understand-anything] Knowledge graph is stale...` hook message appears in a fresh session

No secrets needed — just redact project names/paths if necessary.

My current root-cause hypothesis: this is not a missing Do not ask for confirmation sentence; it is that the auto-update path currently depends on agent compliance with hook stdout. If the hook message appears but is ignored, a robust fix would move more of Phase 0 / Phase 1 into an actual hook-side script or command, and only ask the LLM/agent for the token-costly analysis phase after deterministic checks prove it is needed.

[anteqkois]

Teh hook is triggering, but it is ignored by aget. This is a problem. I tried may times, simple instruciton on session start to don't distrupt, questioning if they dont forget sth (an d then they tell that it see hook but the ignore it because XYZ and always skip the hook instruction)