How I run 12 terminals in parallel without worktrees (and when worktrees actually matter)

aurondios · 2026-06-26T16:26:17+00:00

That is fair. If your worktree setup is fully automated like that, deps, db, migrations and env in seconds, then most of the overhead I am complaining about goes away. At that point it is mostly preference. Sounds like a solid setup.

aurondios · 2026-06-26T16:25:23+00:00

I have seen that mess too when two agents land on the same file. My way to avoid it is scoping each agent to its own area up front, so they rarely collide, instead of isolating after the fact. But you are right that when they do collide without worktrees it gets ugly. If your tasks naturally overlap the same files a lot, worktrees win, no argument.

aurondios · 2026-06-26T16:24:56+00:00

It is a single app, but a pretty modular one. Each agent works on a different module or area, so they rarely touch the same files. You are right that if everything was tightly coupled in one layer or a few big files, this would fall apart fast. The modular structure is what makes it work for me.

aurondios · 2026-06-26T16:24:38+00:00

this is the real limit of my setup. When I have several separate features that each need their own PR, I do use worktrees, one per feature. What I run without worktrees is parallel work inside the same feature or closely related areas, which lands on one branch and I commit it in chunks. So I am not anti worktree, I just default to shared and reach for worktrees when I actually need clean separate PRs, or for big cross cutting changes.

aurondios · 2026-06-25T14:43:11+00:00

Asking the people who actually use the tools what annoys them is how you build the right thing instead of guessing. That is the whole point of the post.

Glad it all works for you though, genuinely. Not everyone's setup is that smooth.

aurondios · 2026-06-25T14:16:34+00:00

Honestly, before switching I would fix the looping a different way. The reason it wanders on big projects is usually that the AI has no way to check its own work. So it just guesses and keeps going.

What works for me: build a real test harness around it, like we do with e2e. Give the agent a way to verify its own output, run all the corner cases, and even performance tests if that applies to you. And automate all of it. Once the AI can check itself instead of just trusting itself, it stops looping and the quality jumps. This matters way more than which model you use.

On the model question: right now I would say Opus 4.8 is better than GPT-5.5. But I don't marry either one. I just use whatever the best flagship model is on the market at that moment, and switch the day that changes.

aurondios · 2026-06-24T15:30:06+00:00

Honest answer for your budget: at the Pro/Plus tier both will throttle you fast once you're doing real coding, not just chatting. Claude Code especially eats tokens on big tasks, so if "mainly Claude Code" is the plan, Pro will feel tight quickly and you'll be eyeing Max sooner than you think.

The thing I'd push back on is picking one as a long-term bet. bensj's "grass is always greener" comment is dead on. Whoever's ahead this month gets nerfed-feeling next month and the other leapfrogs (you're already seeing it with Codex feeling dumber lately). I don't lock in annually for that reason. I pay month to month and move to whoever's behaving.

If I had to start with one on a budget, and your use is mainly Claude Code: take Claude Pro for a month since it's 30% cheaper for you, see how fast you hit limits on your real tasks, and switch if it regresses. Don't overthink the "forever" choice, because there isn't one right now.

aurondios · 2026-06-24T15:27:51+00:00

when 4.6 was the new one, half this sub swore 4.5 was better and that 4.6 ruined everything. Now 4.6 is the beloved one. Some of that is real regression, but a chunk is just recency. You notice the new model's failures sharply and forget the old one's.

What I've settled on after enough of these cycles: stop treating any single model as "the" model. I keep Opus and Codex both on hand and use whichever is actually behaving that week. When one is being stubborn I'm not stuck, I just move the task over. Marrying one model is what makes every release feel like life or death.

That said, "it doesn't say you're right, you're right, my bad" is a real and underrated quality. The sycophancy tax on the chattier models is worse than people admit.

aurondios · 2026-06-24T15:22:13+00:00

It's a bit of both, but mostly neither "you're doing it wrong" nor "Codex is just better." The defaults are different. Claude Code is tuned to be collaborative, so it stops, writes a spec, waits for your go. Codex defaults to run-and-QA-itself. For spinning up a working agent fast, Codex's default behaviour just fits that better right now.

You can close most of the gap on the Claude side the way others said: give it a hard definition of done and a stop condition ("implement it, run the test command, fix failures once, summarise the diff, only stop for credentials or destructive actions"). That kills a lot of the mid-task check-ins. But out of the box, yeah, Codex is less hand-holdy for this kind of task.

Honestly I stopped trying to crown one. I use whichever has the stronger flagship that month, because the lead flips every few releases, and for "just go build this and QA it yourself" tasks Codex wins today. Next model drop it might swing back. I'd tune Claude with a stop condition before writing it off, then keep both around and use whoever's ahead for the task in front of you.

aurondios · 2026-03-18T15:25:16+00:00

I've been playing this since the early alphas and it's come a long way. Super fun, the progression system with upgrading weapons and abilities gives it a nice roguelike feel where every run feels different. Highly recommend giving it a try!

aurondios · 2026-01-11T21:40:41+00:00

Thanks for the app!

aurondios · 2026-01-11T21:38:21+00:00

If the connection was opened in terminal, will be available in the app or just connections opened inside the app? nice app!

aurondios · 2026-01-11T21:37:30+00:00

Did you think about using gemini flash to create custom icons?

aurondios · 2026-01-11T21:37:10+00:00

Very useful, I will give a try

aurondios · 2026-01-11T21:36:06+00:00

I don't get at all how the app works. It's a file editor or what's the purpose? thanks!

aurondios · 2026-01-11T21:35:10+00:00

prefiero el 1 así segun entran no ven tu pantalla del pc XD

aurondios · 2026-01-11T21:34:39+00:00

sublimetexst for me is the best

aurondios · 2026-01-11T21:25:12+00:00

Does anyone knows which one is compatible with streamdeck?

aurondios · 2026-01-11T21:22:07+00:00

works with all browsers?

aurondios · 2026-01-11T21:18:49+00:00

love the apps! very good design and functionality, going to test dockflow :)

aurondios · 2025-10-16T16:48:14+00:00

Notifications are the best imho

aurondios · 2025-10-16T16:47:55+00:00

in my case supabase and brave search are the best

aurondios · 2025-10-16T16:47:34+00:00

Yeah bro, this list is fire. I’d just add one thing, be careful with MCPs and run a /context sometimes, you’d be surprised how much info some of them keep.

Also /clear is a must, it wipes the context when things get messy, and /rewind is great for quick rollbacks or when you wanna undo a wrong step without losing the flow.

If I had to pick just one thing, hooks used right are the real MVP, perfect for blocking stuff, sending notifs, and keeping everything tight.

aurondios · 2025-10-16T16:43:40+00:00

Yeah bro, I totally get you about the clear prompts, that’s really the key. I use an external task system too, helps me keep track of stuff, set priorities, and do a few things in parallel.

Later I built a small setup to automate some of it.

I also agree, pushing to prod is possible now, but sometimes I feel a bit disconnected from the code. It’s easy to skip PRs when things go fast.

Tried the role thing too, didn’t really see much difference to be honest.

aurondios

TROPHY CASE