Describe the issue
When using aoe add --trust-hooks, the interactive hook approval prompt is skipped entirely. However, the hooks that actually execute are the merged result of repo hooks + global/profile hooks. The user has no visibility into what the final merged set of hooks looks like.
To reproduce
-
Configure global hooks in ~/.config/agent-of-empires/config.toml:
[hooks]
on_create = ["echo global-hook"]
-
Configure repo hooks in project/.agent-of-empires/config.toml:
[hooks]
on_create = ["echo repo-hook"]
-
Run: aoe add ~/project -w feat/test -b -t "test" --trust-hooks
The user sees ✓ Repository hooks trusted and Running on_create hooks... but never sees which hooks are actually executing. The repo hooks replace global hooks per-field (not append), which may be surprising.
Expected behavior
When --trust-hooks is used, print the final merged hook list before execution so the user can see exactly what will run:
Running on_create hooks:
echo repo-hook
✓ on_create hooks completed
This is a minor UX improvement. Global hooks are user-controlled so this is not a security issue, but transparency helps users debug unexpected hook behavior.
Affects
Both CLI (src/cli/add.rs) and potentially TUI paths. The TUI shows hooks in the trust dialog but doesn't show the merged result after approval.
Describe the issue
When using
aoe add --trust-hooks, the interactive hook approval prompt is skipped entirely. However, the hooks that actually execute are the merged result of repo hooks + global/profile hooks. The user has no visibility into what the final merged set of hooks looks like.To reproduce
Configure global hooks in
~/.config/agent-of-empires/config.toml:Configure repo hooks in
project/.agent-of-empires/config.toml:Run:
aoe add ~/project -w feat/test -b -t "test" --trust-hooksThe user sees
✓ Repository hooks trustedandRunning on_create hooks...but never sees which hooks are actually executing. The repo hooks replace global hooks per-field (not append), which may be surprising.Expected behavior
When
--trust-hooksis used, print the final merged hook list before execution so the user can see exactly what will run:This is a minor UX improvement. Global hooks are user-controlled so this is not a security issue, but transparency helps users debug unexpected hook behavior.
Affects
Both CLI (
src/cli/add.rs) and potentially TUI paths. The TUI shows hooks in the trust dialog but doesn't show the merged result after approval.