Problem: agent hooks never install or fire (the repo setup only installs git hooks) —— Trove problem library

What you will run into

You run the repo setup as documented, yet the expected agent hooks (e.g. pre-tool-call) never fire — nothing triggers before tool calls and nothing shows in the logs. Re-running setup changes nothing: setup installs git hooks, not agent hooks — two different event systems. Installing git hooks does not hook agent lifecycle events.

Why this happens

Conclusion first: the framework repo setup task only installs git hooks and offers no way to install agent hooks (deftai/directive issue #3732, 2026-08-25).

Chain: you run setup -> git hooks get registered (commit/checkout events under .git/hooks/) -> nobody registers the agent platform tool-call events (pre-tool-call etc.) -> hooks never fire. The break: the two hook families live in different event systems — git hooks attach to Git operations, agent hooks attach to agent platform lifecycle events.

Not reproduced: the agent-hooks chain was not reproduced here (stated honestly); the judgment rests on the setup behavior (git hooks only) plus issue #3732.

Conclusion: when hooks do not fire, first ask "whose event system do they register in": checking .git/hooks/ is only step one; the agent side needs separate registration per platform conventions (MCP/extension mechanisms).

Step by step

1. Tell the two hook families apart — Required

ls .git/hooks/ shows git hooks; agent hooks do not live in that directory — separate the concepts first.

2. Register hooks per the agent platform — Required

Check the hooks-registration docs of the platform (agent with MCP/extension support) and wire in the framework hook entry.

3. Restart the session and verify — Required

After registering, restart the agent session, trigger one tool call, and see whether pre-tool-call executes (logs/callback output).

4. If it still does not fire — Diagnostic

Check hook executable permissions, entry paths, and platform config syntax; attach platform and version info when following the issue.

How to confirm it works

• The hook actually executes before tool calls (visible in logs);
• git-side behavior is unaffected (existing git hooks keep working).

Other environments

• Hook registration differs widely between agent platforms: follow platform docs; do not assume a common mechanism;
• Not reproduced: this environment has no agent-platform hook chain attached (stated honestly);
• Source material: deftai/directive issue #3732 (2026-08-25), anonymous retrieval summary.

Symptom

After running setup as documented, agent hooks (pre-tool-call etc.) do not take effect / cannot be installed.

Cause

The framework repo setup task only installs git hooks and provides no path to install agent hooks (demand sample #3732, 2026-08-25).

Solution

1. Distinguish the two hook kinds: git hooks (what setup installs) versus agent hooks (registered separately per the agent platform conventions).
2. Register the hook config manually per the platform (MCP/extension mechanism) docs.