Lifecycle and subagent visibility
AgentPeek recognizes codebuddy and cbc, then projects CodeBuddy hook events into session state, tool activity, failures, compaction, and subagent rows. Managed entries live in ~/.codebuddy/settings.json without replacing user hooks.
Permission decisions
CodeBuddy’s current PermissionRequest hook carries a decision response. AgentPeek can approve once, deny, or deny with feedback; CodeBuddy exposes no always-allow decision on that hook. Questions and follow-up input stay in CodeBuddy, and no usage source is inferred.