← All IntelClip / OtherDeclaring 'agent bankruptcy'
From Velocity Sickness: What Happens When Your Whole Team Gets 10x Faster — Matt Dailey, Ref. · ≈2:26
“Next morning you come back and it's like walking into just a room of strangers.”
“But like no problem. They're agents so you just like get rid of them and start over again.”
“The problem though is you know, it feels like you're doing a lot of work but you're doing the same work and you're spending tokens twice.”
What’s in it
- Names the 'agent bankruptcy' trap of ditching stale agent sessions
- Explains why restarting a dozen agents burns tokens twice
- Reframes lost agent context as a team-level efficiency problem
Clip transcript
in all sorts of directions. The third problem you might be experiencing is declaring agent bankruptcy. This is a a common pattern I see engineers get into where you know, you're cranking. You have like your 12 terminals open. You're like at the end of the day you're like, "Yeah, I did a lot of work." You step away from your laptop. Uh spend time with your friends and family. Next morning you come back and it's like walking into just a room of strangers. Like, who are these people? What are they doing here? But like no problem. They're agents so you just like get rid of them and start over again. The problem though is you know, it feels like you're doing a lot of work but you're doing the same work and you're spending tokens twice. You're doing the same problems over over again. And if you think about that organizationally, that's your team not being efficient with both their time and their their token resources.
Comments
Sign in to comment.
Loading comments…