... waiting time is spent on questions nobody needed to ask. So, two things. How long was yours waiting when you looked, and was the question worth it? I will post the spread in a couple of weeks. [I build Pushary, so I am not neutral about any of this. Asking anyway. The last two threads here taught me more than a month of building did.] Comment from Aadil Ghani(@aadilghani): @julian_ting2 we actually do have this in pushary

... recorded, then together exceed the cap. I'd reserve budget before dispatch and reconcile it after the call. Does Traccia's limit cover a shared budget across concurrent runs, or is it per run today? Disclosure: I build Pushary, on the approval side. Comment from Vijay Poudel(@vijaypoudel1): @mateo_rossi  exactly the problem that we are solving with Traccia. You can enforce policies around the maximum number of retries, tool calls and many more. The agent run gets killed ...

... ones I hate. Which one would you actually leave enabled after a month? I am especially curious about the last permission you missed. Were you away from the computer, or just working in another window? Disclosure: I build Pushary. We are working on the Mac side of this problem now. I am asking before we lock the default, because notification settings are easy to add and hard to make people revisit. Comment from Aadil Ghani(@aadilghani): That makes sense ...

... from Justin Jincaid(@justin2025): I have seen @thibaultll and @marclou launch in public on X with great success. But it's hard to copy because they have a strong follower base. Comment from Aadil Ghani(@aadilghani): Yes, a relaunch Pushary already has a product page; I meant the discussion ahead of our next launch for the Mac notch app. I should've made that clearer. We asked where people wanted an agent's approval request to appear, and the replies ...

... cached reading after the provider underneath it had already failed, and report healthy from it. That is not silence. That is a green result computed from a reading that no longer existed. Aadil found the same collapse in Pushary one layer up. A session that exited cleanly and a session swept for going stale both write offline, and the board files offline under done. His reframing is the sharpest thing anyone has said to me about this ...

... heard to that one is a guess, and the guess is usually "keep waiting", which is how a job sits stalled for six hours and a customer decides your product is broken. [Same disclosure as last time: I build Pushary, which is the ask-a-human part of this, and these days we sell it to other companies to embed as much as to people running agents in their own terminal. Obvious bias, asking anyway. The last thread taught ... ... there's no shared webhooks folder they both sit under. so the glob fix doesn't even apply to the three i have today, they were never colocated in the first place. which proves your enumeration vs

... first" should begin. Genuinely curious how you all handle it. Comment from Stacy Wycoff(@stacywycof83995): I hit this same tension but across businesses rather than terminals. I run more than one venture at once and the babysit versus trust problem shows up constantly, except instead of watching an agent I am watching Slack, email, and four different dashboards trying to catch the one thing that actually needs a decision from me. I ended up building FounderFlow partly to solve this ... ... Same queue, totally different urgency. Telling those two apart automatically is the piece I don't have clean yet. In your setup, how are you deciding which of the 20 percent is allowed to wait for a window versus

... material lives outside, and each task pulls in only its slice. That's the difference between token cost that grows with your whole project versus token cost that stays flat per task. Honest caveat, since I don't want to oversell: this is genuinely more of a your-harness question than a Pushary

... this list: https://www.producthunt.com/cont... My launch is Astrio: https://www.producthunt.com/prod... Comment from Aadil Ghani(@aadilghani): i had my launch scheduled for March 17 wanted to do CRO of my onboarding journey staying out of the competition vs launching safe my priorities are clear finished the CRO, updated the landing page, tested the flows, ranking #1 on google good to go special thanks to claude code, cursor and Pushary