GitHub Copilot

GitHub Copilot CLI sessions, watched from the notch

Live state, prompts, and answers for every copilot run, without hunting terminals.

Download for FreeFree 3-day trial · Apple silicon

Copilot in the corner of your eye

Run copilot in any terminal and the session appears in the notch with live state, current activity, tool calls on the timeline, and subagents under their parent. When a turn completes or errors out, the state flips where you can see it, and notifications can tell you even when you're elsewhere.

Approvals answered in place

Copilot permission requests surface in the notch with the command laid out: allow with ⌘ A, deny with ⌘ N, or deny with feedback that goes back to Copilot as the reason. When Copilot needs input mid-run, the session is flagged for attention, and the composer sends follow-up prompts into resumable sessions.

Setup, and a straight answer on usage

Hooks install to ~/.copilot/hooks/agentpeek.json, with Doctor repair, and Quick Routes opens the Copilot hooks, config, and session-state folders. One honest limitation: Copilot exposes no stable local usage store, so AgentPeek shows Copilot sessions without usage numbers rather than fabricating a gauge.

Questions, answered.

Does AgentPeek work with GitHub Copilot CLI?

Yes. Copilot CLI sessions appear in the Mac notch with live state, tool activity, and subagents, permission prompts are answered with a keystroke, and the composer sends follow-up prompts into resumable sessions.

Can AgentPeek approve Copilot tool calls?

Yes. Copilot permission requests surface in the notch with the command laid out. Press Cmd A to allow or Cmd N to deny, and denial feedback is forwarded to Copilot as the reason.

Can AgentPeek track GitHub Copilot usage limits?

Not today. Copilot exposes no stable local usage data AgentPeek can read, so Copilot sessions appear without usage numbers instead of a fabricated gauge. Session monitoring, permissions, and follow-up prompts all work.

Your agents, one glance away.