01
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.
02
Native approval ownership
CodeBuddy hooks report activity but do not provide AgentPeek a response socket. Approval and question hints can enter Focus Inbox, while the actual decision stays in CodeBuddy. No usage or selected-session follow-up transport is inferred.