Launching today
AgentManager
Never miss a Claude Code session waiting for your input
83 followers
Never miss a Claude Code session waiting for your input
83 followers
A floating macOS window for every Claude Code session. The moment one needs your input, it surfaces — and hides when all is clear. Jump to the exact terminal in one click. Native Swift, notarized, 7-day free trial.
This is exactly the annoying Claude Code failure mode. The floating session state is useful, but the one-click jump back to the right terminal is the part that makes it feel workflow-native instead of just another alert layer.
Also love the cat room, as long as Simple mode exists for when I need to pretend I am serious.
Custom Browsing History
@aditya_harish_2002
Thank you! And you nailed the design bet — alerts alone just move the problem ("now I have unread alerts"). The jump is what closes the loop, so I spent a silly amount of time on precision: iTerm2 lands on the exact pane, Terminal and Ghostty on the tab, VS Code / Cursor / Zed on the right project window.
And yes, Simple mode exists precisely for screen-sharing-with-your-manager moments 😄 The cats will wait for you.
@umechanhika Great efforts put on the product and its visible! Too good
Custom Browsing History
@aditya_harish_2002
That means a lot — thank you! Enjoy the app, and my DMs are open if anything ever feels off 🙌
A click-to-jump shortcut is great, but it would be even better if I could pin certain sessions to stay visible even when idle, since I often switch between two long-running tasks and lose track of which window belongs to which project.
Custom Browsing History
@senargf3
Good news on half of this: sessions never leave the list while they're alive — idle ones stay right there as grey rows, and every row is labeled with its project folder name. So "which window belongs to which project" is exactly what the list answers: glance, click, and you're in that project's terminal. The window itself is also one ⌥Space away at any moment, even when it's auto-hidden.
The other half — keeping it visible through idle instead of auto-hiding — is a fair ask. Auto-hide is the default because "quiet when nothing needs you" is the app's whole personality, but a pin option for people juggling two long-running tasks wouldn't fight that. Adding it to the list — thanks for the concrete use case, that's the kind that actually shapes the roadmap!
Honestly this looks super useful since I constantly lose track of which Claude session is actually waiting on me. One thing though, would be great if it could play a subtle sound or send a native macOS notification when a session needs input, kind of like how Messages does it. Sometimes the floating window might be hidden behind another app and I would totally miss it otherwise.
Custom Browsing History
@araczeliha97691
Good news — the sound already exists, and it's the app's signature move: a subtle cat meow (~0.35s) the moment a session starts waiting 🐱 It's mutable if meows aren't your office vibe, and if several sessions hit "waiting" at once it's debounced so you get one meow, not a chorus.
On the buried-window worry: the floating window is always-on-top, and it re-surfaces in front the moment any session needs you — so it can't actually get lost behind other apps. Between the meow, the auto-surface, and the live counts in the menu bar, I deliberately skipped Notification Center: banners pile up, get swiped away, and end up as one more inbox to ignore. The window appearing is the notification, and it disappears once you've handled things.
Give the trial a spin and tell me if a waiting session ever actually slips past you — if it does, that's a bug in my book and I want to hear about it.
The local hooks approach is the right tradeoff here. Once an agent has access to repos, terminals, and approval prompts, I want the session monitor to be boring infrastructure: local state, no output scraping, no network dependency, and stable session identity so I can trust the jump target.
Custom Browsing History
@krekeltronics
"Boring infrastructure" is the nicest thing you could call it — that was the design brief, verbatim. A tool that sits between you and approval prompts has no business being clever.
On session identity, since you brought it up: each session is keyed by Claude Code's own session ID, and the hook records the owning claude process's PID plus its start time — so if a PID gets recycled by the OS, a dead session can't masquerade as alive. Sessions whose process vanished without a clean SessionEnd get swept out automatically. And the jump target is captured at hook time, not guessed at click time — e.g. the exact iTerm2 pane GUID is resolved by walking the process tree when the event fires, so the click lands where the session actually lives.
State files are written atomically to a local directory, the app just watches it with FSEvents, and there's no daemon and no network in the loop. If it ever stops being boring, that's a regression 😄
this looks super useful for keeping tabs on multiple sessions, honestly the auto-surfacing is a nice touch. one thing though, it would be great if you could pin certain sessions to stay visible even when nothing needs input, so you can monitor like a long-running build or deploy without it disappearing on you
Custom Browsing History
@sebahat45760404
Thanks! Good news for the build/deploy case specifically: you may not need to watch it at all. The moment a long-running session finishes, it flips to "done" and the window surfaces on its own — completion is treated as an event worth your attention, same as waiting for input. And while it's running, the menu bar keeps a live per-state count, so a glance tells you it's still going without any window open. ⌥Space summons the full list any time you want a closer look.
That said, "keep it visible, I just want to watch" is a fair and different ask — and you're actually the second person requesting a pin option today, which officially moves it up the list 😄 Auto-hide is the default because staying quiet when nothing needs you is the app's whole personality, but an opt-in pin wouldn't fight that. Thanks for the concrete use case!
Love this idea, especially the jump-to-terminal one click since that always trips me up. One thing that would seal the deal for me is per project status icons in the floating window itself, like a little red dot or spinner right next to a project name so I can tell at a glance which session needs me without scanning titles. Would also be great if those icons respected Do Not Disturb or hid when a session is just running a long thinking step versus truly waiting on me.
Custom Browsing History
@dndcltj
On the "which session needs me" part — the state lamps are already there: every row has a colored light next to the project name, and the waiting one is a pulsing amber glow with a stripe down the row's edge, so it catches your eye before you've read anything. Blue with a slow breathing animation means "working, leave it alone." And that thinking-vs-waiting distinction is structural: state comes from Claude Code's own hook events, so a long thinking step or tool call stays blue — amber only fires on explicit signals like a permission prompt or a question to you. No false alarms mid-stream.
But if what you're after is telling which project is which without reading names — like a distinct icon or color per project — that doesn't exist yet, and it's a genuinely good idea. Right now identity is the project folder name plus stable row order (rows never reorder, so muscle memory does a lot). A per-project visual mark would make that instant. Adding it to the list — and tell me which you actually meant, I'm curious now 😄
DND is a good call too: there are no Notification Center banners at all and the meow is mutable, but auto-quieting during a macOS Focus session would be the polished version. Noted!
That's clever. Any plan to support Linux or Windows once Claude Code agents run there?
Custom Browsing History
@dhiraj_patel5
Thanks! Honest answer: no near-term plans. AgentManager is native Swift (SwiftUI + AppKit) on purpose, and the parts that make it feel good are exactly the parts that don't port — the always-on-top panel, FSEvents watching, and the terminal-jump layer built on macOS Automation/Accessibility APIs. A Linux or Windows version wouldn't be a port, it'd be a second app written from scratch.
The one honest caveat: the concept is portable. Detection is just Claude Code hooks writing local JSON, nothing Mac-specific about that half. But as a solo dev I'd rather make one platform genuinely excellent than three platforms mediocre — so for now, Mac gets all of it. If demand elsewhere gets loud enough, that math can change 😄