AgentPeek - Your coding agents, in the Mac notch
by•
You're running more coding agents than ever, but you can't keep up with them. That's where AgentPeek comes in. It pulls every session up into your Mac notch, live. Glance up, approve a prompt, watch token usage and manage the entire flow without pausing your YouTube video. All local, all yours.
Replies
The notch placement is smart — babysitting Claude Code/Codex runs is exactly the dead time I want back without alt-tabbing to a terminal. How does AgentPeek actually read session state: is it tailing the local CLI logs/JSONL transcripts on disk, or hooking the process, and does any of that session content ever leave the Mac? For a tool watching my coding-agent output, fully-local with nothing phoned home is the dealbreaker either way.
AgentPeek
@hi_i_am_mimo Native hooks!
cool concept. i run a few Claude Code sessions in parallel and lose track fast. does it total up usage across all of them or just show each session separately? a combined view would be the killer feature for me
AgentPeek
@omri_ben_shoham1 ooooo right now separately on their session cards, but that will definitely be in an update soon 👀 Thank you for the idea :)
@brenhuber makes sense, per-session is still useful on its own. will keep an eye out for the combined view, that's the thing that'll make me actually trust the token budget instead of guessing
AIQRHub
Congrats on AgentPeek — the notch/menu bar angle for Claude Code is really clever.
Saw two r/ClaudeCode threads today that match what you're building:
1) User on 5x sub sees usage around 40%, then gets locked at 100% with almost no warning — classic "usage meter you can't trust" pain.
2) Desktop SSH dev works fine, but UI stuck on "Reconnecting to root@..." — people think the session is broken when it isn't.
Worth a glance if you're looking for early users venting about session/usage visibility. Happy to share the links if useful.
The permission-prompt piece is the part I'd care about most. I lose track when Claude Code is waiting while another agent is still running. Curious if you plan to show blocked vs still executing as separate notch states?
reading sessions is the easy half — tail the jsonl, token counts fall out. approving a prompt from the notch is the sharp part: a write path back into the agent's permission gate, not just log-watching.
It would be great to have something like a notification bell that rings when Claude Code finishes generating)