... 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 Oliver Graf(@oliver_graf1): I like the idea of keeping an eye on how agents use resources, not just which model they use. That can make a real difference in costs. Comment from Vijay Poudel ...

... 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 Siarhei Hamanovich(@siarheihamanovich): @aadilghani  The question ...

... 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 ... ... nothing, the reviewer's normal experience becomes an empty screen, and empty screens train people to expect empty. Whether the one that is not empty gets read properly on day forty is an open question. It still beats the alternative

... 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 which should break into your focus? Comment from Aadil Ghani(@aadilghani): @virko_kask   This made my day, partly because you actually went and rebuilt the thing, and partly because "a file cannot tap my shoulder" is the cleanest one-line ... ... 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

... clearly good. Here's where AgentPays and Pushary slot together cleanly. You own the reasoning capture and the financial guardrail, the agent must justify a transaction and it's bounded by threshold and whitelist. Pushary

... Comment from Aadil Ghani(@aadilghani): @sanath_bhat  I actually did the opposite :) 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