Official command hooks, preserved config
AgentPeek adds only its owned command entries to ~/.qoder/settings.json for prompt, tool start, tool completion, tool failure, and stop events. Existing settings and user hooks stay untouched, and Doctor shows the exact target before repair.
Hooks for activity and approvals, ACP for Direct Chat
Qoder command hooks update session state and tool activity. For known mutating tools, the PreToolUse hook can allow once, deny, or deny with feedback from the notch; reads and unavailable responses return to Qoder's native flow. For Direct Chat, AgentPeek launches qodercli --acp, loads the exact selected session, and relays native ACP permission requests. No usage source is inferred.
Questions
AgentPeek detects the official qodercli executable.
Yes. Supported mutating PreToolUse requests are answerable through owned hooks, and Direct Chat relays native ACP permission requests. Reads and unavailable hook responses stay in Qoder.
Yes. It owns only its exact hook command entries and preserves unrelated settings and user hooks.