Since I built my own dev tool to allow me to better organize and manage multiple sessions, I've found my flow state hits when I've got agents staggering to completion. Conversation with one, wrap it up, send my response, and another one finishes. I currently have 49 agent sessions open in atrium and when I'm grinding, 5-15 are going at a time. If I get em all onto longer horizon tasks, I start to comb through other sessions to pick up parked conversations.
Honestly, it was about 4-6 hours of hands on keyboard. Bout a day and a half overall with a handful of smaller tweaks/bugfixes since then. I am definitely planning on writing about it. tl;dr this was sort of glorified vibe-coding and intentionally so in order to really see what 4.8 was capable of. But I do have some interesting observations that I made along the way that I'm going to go into more detail about.
Thanks! So the persistence is universal. atrium allows you to instantly pick up where you left off across all of your projects/sessions/etc. Start a conversation, leave it to work on something else, restart, and it auto-resumes so you can pick it up again later. Additionally, your sessions are indexed to allow for FTS and every interaction is stored in a timeline that you can use to easily (re)orient yourself in any project.
Happy to go into more detail, but that's kinda the high-level of the persistence story.
The reality is that there are people that want AI in everything they use and there are people that don't. Google, like almost every other big tech company, is betting that there are more of the former.
And now we have an arms race with benefits nobody knew they needed and consequences nobody asked for.
Essentially :( I recently built a tool for managing many agents simultaneously and decided to focus 100% on CLI-first cause I saw that coming.
It's a massive bait & switch, honestly. I can't imagine how many hours/tokens were spent collectively building SDK-based tools on the premise of subscription pricing.
Super interesting mental model here. I'm building a tool, called atrium, that set out to solve similar problems, but I landed on a pretty different model -- workspace > room > stack > pane. I'm really curious to understand more about your concept of topologies, though. How exactly does it manifest in practice? Are they essentially organized units of collaborative work that your agents are executing? Has this unlocked different ways to solve problems for you than you were doing before or is it primarily organizational sugar?
At any rate -- really cool concept. Wish you the best of luck with it!
lol @ at the uber-emdash. anything AI can do, we can do better!
"fair pushback". ez solution though that's enabled by this feature. "exclude AI-generated" filter. I'm actually incredibly surprised that isn't a thing, yet, tbh.
I bet if sites just added a "likely AI-generated" badge next to UGC, 99% of people would stop doing this. Problem is, without public shaming, many people will continue to take advantage of anything that requires them to do/think less.
Gemini CLI is so incomprehensibly bad. I can only hope dedicated focus on agy will be the difference maker. It'd be nice to actually be able to integrate Gemini models into my workflows because they offer genuinely unique approaches to problems that complement Claude/Codex really well.
You can, and sometimes that's the right answer. Where it gets hard: security CVEs that need patching but the fix is only in the new major, transitive deps that bump and bring incompatibilities, hiring a contractor who doesn't know your locked version. None of those are insurmountable, but they're real tax.
Fair counter, and that's the right stance. The tax I'm pointing at is the implicit social one: feeling like you owe a response. Plenty of publishers get burned out before they figure out your model.
Different angle from the developer side: Apple's a11y API at the OS level is genuinely good. It's the WebKit-embedded-in-native gap that breaks. Shipped a Tauri app where Monaco editor lived inside WKWebView and found out the hard way that VoiceOver's `accessibilitySupport: auto` mode silently breaks backward text selections in Monaco — only setting it to "off" gave us correct selections. Which meant choosing between functional text selection or VoiceOver support, and the answer was selection.
Rock-solid in AppKit/UIKit. Falls over at the embedded-WebView seam where most modern desktop apps actually live.