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.
Claude Code sessions that need input mid-task is real pain, especially when you're juggling multiple things. Does it support notifications on iOS or just Mac desktop alerts?
Custom Browsing History
@abdurrahman_fakhrul
Mac only, and honestly it's likely to stay that way for a while. The app is built around a strict "nothing leaves your Mac" rule — no server, no network, session state is just local files. Pushing notifications to an iPhone would mean routing your session activity through some backend, and that's a privacy tradeoff I don't want to make casually.
It's also a slightly different problem: AgentManager is built for the at-your-desk case — you're juggling sessions and other work on the same machine, and it surfaces the one that needs you. If you're away from the Mac entirely, a blocked session usually isn't something you can act on anyway (the terminal's back at your desk!). That said, if "know before I walk back" is a real need for you, I'd love to hear the scenario — it'd have to be designed carefully, but I'm listening.
Really I'm here for the cat sounds. Though I'd want per-session pitch, so I know which one is meowing.
Custom Browsing History
@aidan_codefox
Finally, someone here for the right reasons 😄
And honestly… that's not even a joke to me. The meow is procedurally synthesized (no audio files), so giving each session its own pitch is genuinely doable — your refactor session as the deep old tomcat, the test runner as the anxious kitten. Adding it to the list, and I can't believe this is now a roadmap item. Thank you.
The native Swift choice really shows here — having a floating window that just appears and disappears instead of fighting with another Electron app is such a relief.
Custom Browsing History
@ege_karama27779
Thank you — that's exactly why it had to be native. An app whose job is to appear and vanish dozens of times a day, while living permanently next to your real work, has no business shipping a browser runtime with it. Swift + AppKit keeps the panel instant and the footprint tiny, so it earns its spot as a resident instead of competing with your actual tools for resources.
(Also, pixel-art cats deserve to be rendered natively. It's a matter of principle 🐈)
Finally something that solves the constant tab-switching annoyance with Claude Code. The auto-surfacing when input is needed feels genuinely native, not bolted on.
Custom Browsing History
@erengilsed11978
Thank you! "Not bolted on" is exactly what I was going for — the app only speaks up when a session actually needs you, and gets out of the way the rest of the time.
And "native" goes all the way down: it's Swift (SwiftUI + AppKit), the whole download is ~2.5 MB, and everything runs locally on your Mac. The tab-switching tax was the whole reason I built it, so it's great to hear it lands.
Finally something that solves the "which Claude session is stuck" problem. The floating window just appearing when input is needed is exactly the kind of low-key native touch I want from a Mac utility.
Custom Browsing History
@ozandenizm84853
Thank you! "Low-key" is the highest compliment for this app — the bar I set was that a good Mac utility should feel like part of the OS: show up exactly when needed, disappear the moment it's not, and never ask for attention it hasn't earned. That's also why there are no Notification Center banners — the window appearing quietly is the notification.
Hope it keeps your stuck sessions from hiding on you 🐈
Mostly Claude Code as the daily driver, with Codex CLI as the second seat and Aider for quick one-off edits. Codex is the one I d want next since it has a hooks/notify config, so a small state-writer there would slot straight into your FSEvents watcher without you inventing anything new. Aider s the weak link: no real lifecycle events, so it d be exactly the guess-from-output case you re right to refuse.
hooks in ~/.claude/settings.json is the robust call — the seam is that it's one shared file. the other claude code watchers on this page register there too, and an uninstall leaves a stale path still firing on every event.