Answer Claude Code permission prompts from the notch.

Inline permission prompts, not buried terminals

Claude is editing src/auth/session.ts · agentpeek-web 47s esc

Permission requested

- export async function createSession(userId: string) {

- const token = generateToken();

- return { userId, token, createdAt: Date.now() };

- }

+ export async function createSession(

+ userId: string,

+ opts: SessionOptions = {}

+ ) {

+ const token = await generateToken(opts.ttl);

+ return {

+ userId,

+ token,

+ createdAt: Date.now(),

+ expiresAt: Date.now() + (opts.ttl ?? DEFAULT_TTL)

+ };

+ }

+12-4session.ts

Deny ⌘N Always Allow ⌥A Allow ⌘A

Claude Code and Codex pause to ask before they run a tool, edit a file, or execute a command. When you have several sessions open, finding the one that is waiting wastes time and breaks flow. AgentPeek opens the prompt inline in the panel, right next to the session it belongs to, with the full detail of what the agent wants to do.

Keyboard shortcuts for allow and deny

Decide fast without reaching for the mouse:

A Deny with feedback button lets you tell the agent why, so it can adjust instead of just stopping.

Approve plans and reviews too

Permission prompts are not the only thing agents wait on. For plan and review prompts the buttons read Approve and Reject, so you can sign off on a plan before the agent starts executing. AgentPeek queues pending prompts and lets you move between them, so nothing waits silently in a background terminal.

You stay in control

AgentPeek only responds when you choose an action. Prefer to keep approvals in the terminal? The prompt-handling setting lets you leave them there and use AgentPeek purely for visibility. Either way, the decision is always yours.

Works across all your sessions

Permission prompts from any Claude Code or Codex session land in the same panel, alongside live session state and token usage. See the full reference in the docs.

Frequently asked questions