@jeff_weinstein@tempo@stripe "PAYMENT REQUIRED", "402", "SESSIONS", "TEMPO", "STRIPE", "MACHINE PAYMENTS" - love the look + feel of the site. Hope to see you on the 19th π€π°
@steipete@steipete - we're inviting adversarial attacks from agents this Thursday, and will share all of our findings: https://t.co/mv8JKdadhc - or just swing through, I'm sure a few of us could help with the sifting.
@WorkOS@GeoffreyHuntley dropped a line I can't stop thinking about: "Software is clay. Ship it. Reshape it tomorrow." His take: the team that ships 10 imperfect versions beats the one architecting one perfect release. Been doing this for a year without knowing it had a name.
Shared the stage with the legend @GeoffreyHuntley at @OpenAI x CODEX Meetup at the @WorkOS office last night in SF. π @georgepickett for bringing us all together. New projects dropping soon π
@HLOS_AI@GeoffreyHuntley@OpenAI@WorkOS@georgepickett Was there last night. The STAAMP protocol demo blew my mind β giving agents financial identity feels like the future nobody's ready for. Great energy from everyone!
E/acc vs D/acc.
Great conversation last night at the Tower with @VitalikButerin and @beffjezos exploring where these visions for the future overlap - and where they diverge.
Whoβs up next? π
Cool chart showing the ratio of Tab complete requests to Agent requests in Cursor. With improving capability, every point in time has an optimal setup that keeps changing and evolving and the community average tracks the point. None -> Tab -> Agent -> Parallel agents -> Agent Teams (?) -> ???
If you're too conservative, you're leaving leverage on the table. If you're too aggressive, you're net creating more chaos than doing useful work.
The art of the process is spending 80% of the time getting work done in the setup you're comfortable with and that actually works, and 20% exploration of what might be the next step up even if it doesn't work yet.