How do you stay aware of what your AI coding agents are doing?
I've been running Claude Code, Cursor, and Codex pretty heavily for the last few months and I keep hitting the same loop:
1. Start a task in one agent
2. Switch to something else (Slack, Twitter, another terminal)
3. Come back 30-40 minutes later
4. Agent finished 35 minutes ago. Or worse, it's been waiting for my approval the entire time.
The more agents I run, the worse it gets. There's no unified way to know what's happening across them.
Curious what other people's setups look like:
- Do you just keep terminals visible and check manually?
- Built any custom notification scripts?
- Use something like ntfy or Pushover?
- Just... accept the wasted time?
I've been building something in this space (push notifications + approval flows for AI agents) and I'm trying to understand if everyone's workflow is as janky as mine, or if some of you have figured out something clever.
Would love to hear what's working and what's not.
Replies
It's tough thing to do. I mean just go back and every time remember to go back is a hassle. Maybe at some point it's start mentioned where it need more inputs and informed once the job the done. This may help. !
Pushary
@faisal_2420010
Yeah that's the whole problem. You shouldn't have to remember. The agent should come to you.
That's what I built. Two things happen: it pings your phone when it needs input, and pings again when the job is done. You don't check back. It finds you.
Launching it this week actually. pushary.com/ai-coding if you want to take a look.
this is the same problem but bigger when you're running non-coding agents too. an agent that books meetings or sends emails and you don't know what it did until after the fact is scarier than a coding agent waiting for approval. notifications are table stakes but what I really want is a dashboard that shows me what every agent is doing right now across everything
Pushary
@tina_chhabra
You're right, and that's where this goes. Coding agents are the entry point because the pain is obvious and the feedback loop is tight. But the architecture underneath doesn't care if it's a coding agent or a booking agent or anything else that speaks MCP.
The dashboard piece exists already. Live status, pending approvals, full audit trail. Right now it's scoped to coding agents but the plumbing is agent-agnostic.
Launching this week. pushary.com/ai-coding
The more agents you run, the worse your security blind spot gets. There's no unified way to know what's happening across them, what they changed, what they committed, what env vars they read, what endpoints they called, what they added to your codebase, etc.
It's a security surface area problem.
Startups shipping fast with Claude Code, Cursor, and Codex are moving faster than their security posture can keep up. That gap is where breaches happen.
[Full disclosure: I'm co-founder of Faultline Security, and that's exactly why we built it]
Pushary
@beatriz_albernaz
Valid point. The audit trail side is real and mostly unsolved. Pushary handles the permission layer before execution, not the forensics after. Different problem, same blind spot. Probably complementary honestly.
@aadilghani Exactly 💯. Pre-execution control and post-execution audit are 2 sides of the same problem. You've got the "ask-before-act" layer, we've got the "what did it actually do to your security posture" layer.
Would love to chat sometime
Pushary
@beatriz_albernaz
Of course, feel free to book a slot https://cal.com/aadilghani/coffee
I have the same problem. Starting the agent is easy but remembering to check back at the right time is the messy part. A simple notification when it finishes or needs approval would already help. I'd also want to know whether it actually completed the task or stopped because it needs a decision
Pushary
@busra_seker1
That's exactly why I built this. Three notification types: task done, task failed, task needs your decision. The third one is the killer. Agent wants to run something sketchy? Phone buzzes. Tap approve from your lock screen. It keeps going.
Launching the next version tomorrow actually. Good timing.
https://pushary.com/ai-coding if you want to try it.
running one agent at a time for important tasks avoids confusion, even if it slows overall speed.
Pushary
@malani_willa
Works until it doesn't. One agent at a time is fine today but the whole industry is moving toward parallel agents. At some point you'll want to run three things at once and not lose track of any of them.
Better to solve the visibility problem now than to bottleneck yourself later. pushary.com/ai-coding
in my setup I started treating every agent like a background service that must notify me when state changes. If I do not get a signal I assume nothing happened which is obviously not ideal but it reduces confusion a bit
Pushary
@simran_kumar
That's a solid mental model actually. Treat agents like services, expect signals on state change. The problem is most agents don't emit those signals by default so you're stuck assuming silence means nothing happened when sometimes silence means it's been blocked for 30 minutes.
That's the gap I built for. Every state change hits your phone. Finished, failed, needs a decision. No signal no longer means "nothing happened." It means nothing happened.
Shipping this week. pushary.com/ai-coding
Multi-agent setups are still early. most people are stitching together terminals, logs, and alerts instead of having a proper control system.
Pushary
@susil_kora
Exactly where we are right now. Duct tape and terminal tabs. That's why I'm building a proper control panel for it. Launching this week. pushary.com/ai-coding
Pushary
@tehreem_fatima5
Split terminal is the worst. You're technically not babysitting but you're also not doing anything else because half your brain is watching for movement in the corner of your eye.
The hook intercepts the agent's tool-use event before it executes, checks your permission rules, and if the tool needs approval it routes to your phone as a push notification. You tap approve or deny from your lock screen. Answer flows back, agent continues. Whole round trip is a few seconds.
Launching this week with full details on the hook architecture. pushary.com/ai-coding
Interesting thread. It feels like we're moving from agent execution to agent management. The tools that win may not be the ones building better agents, but the ones helping humans supervise dozens of them effectively.
Pushary
@conrad_n
That's the bet. The agents themselves are getting better fast. The supervision layer barely exists. Someone has to build the control plane.
I am not sure if that could help but I have had the same issue and I am not super happy with tools like Conductor. So I am building this CLI that let's you add a bunch of repo from Github (or Linear) and it monitors your issues and PR.
When I get a new Issue, I just press "w" on the side panel and it starts Claude Code (or Codex) and it injects automatically all the context to start working and start working. Also it detects when the agents needs my input and notify me.
There are many other cool things (what I love is that I keep track on top of the agent of the last command I ran because when you jump from agent to agent, I tend to forget what I even asked!!).
I am using this tool daily for all my agents, makes me so much more productive. I never create a git worktree. I rarely go in Github as I can do everything from the tool.
It's not perfect yet but definitely usable if you want to take a look.
https://github.com/AntoineToussaint/pilot
Pushary
@antoinetoussaint
This is cool. Sounds like you're solving the orchestration side, starting agents, routing context, tracking what you asked each one. Pushary comes at it from the other end: once the agent is running, making sure you know when it finishes or needs a decision without watching the terminal.
Probably complementary honestly. Your tool starts and tracks agents, Pushary handles the push notifications and permission approvals while they run. Would be interesting to plug them together.
@aadilghani yes it also does some of that, it shows when the agent is working, when it's done and when it needs your input. A bit buggy now. But mostly working.
Also, have some feature when it auto-fix CI failure, merge conflict...Also, when you have comments on Github, I show that in the pane and you can select a bunch of comments, you type "w" and it will copy the comments and inject in the agent and start working.
Same thing on Issues, if I tag an issue in Github with "@pilot", it will start working on its own, don't even need to type "w".
So it does quite a lot for people like me who are super lazy!
@aadilghani But yes, having on the phone is pretty cool. I started working on Slack integration but paused it.
Pushary
@antoinetoussaint
Ha the @pilot tag triggering auto-work is a nice touch. That's the dream, agent just picks up issues without you doing anything.
The phone piece is the thing that changed my workflow the most. Not having to be at the computer when the agent needs a decision means I actually leave. Slack integration would be interesting too but push notifications hit different when you're away from the desk.
Good luck with the launch. Shipping something you use daily is the best signal - atleast this is what is going on with me 🚀
@antoinetoussaint i like the tool but it's not easy to configure and guide in README not clear enough, if you don't mind help me in this.
Wish you all the best good idea well design.
@waeils hi Wael, yes, didn't plan to share it just yet, I am working on some readme and docs for dev and users.
What part of the configuration would you want help on? And in terms of docs, etc...any suggestion?
@antoinetoussaint Hi Antoine, i clone the repo in my machine but i can't run it i tried all possible way, so if there's any demo video how to setup will better.