Twitter/X

Nate Berkopec (2026-08-05) is "closely watching orbs" and asserts worktrees…

2026-08-05 · 23:50 UTC ·@nateberkopec ·1 min read

Brief

Nate Berkopec highlights orbs as a preferable alternative to worktrees, citing Tim Culverhouse's account that, after reluctantly adopting orbs on the Amp team, he found worktrees introduced nonobvious friction (parallelization limits, test/CPU contention, orchestrator headaches). Orbs, or a harness-neutral equivalent, remove worktree complexity and let developers focus on the application rather than resource management.

Why it matters

Nate Berkopec (2026-08-05) is "closely watching orbs" and asserts worktrees "always felt like the wrong solution," favoring orbs or a harness‑neutral equivalent as the right approach.

Key details

  • Tim Culverhouse (@rockorager) says he was the last Amp team member to adopt orbs; after forcing himself to use them he discovered worktrees caused subconscious friction—limiting parallelization, creating CPU contention among agents running tests, and requiring orchestrator coordination—while orbs removed that complexity and refocused him on the application.
Source evidence

Closely watching orbs. Worktrees to me always felt like the wrong solution. Orbs (or whatever harness-neutral concept you want to sub in that does the same thing) feels like the right one.

Tim Culverhouse (@rockorager)

I was the last amp team member to go all in on orbs. I thought my local dev flow was good enough. It worked. I was incredibly productive. I didn't need a change.

But I forced myself into orbs. And I found there was a lot of friction that I can't even explain - subconscious stuff - like...I can't parallelize that because of some stupid reason. I don't want to parallelize that because how do I tell the model make a new worktree, but also it's going to suck running tests because you'll fight with 7 other agents over CPU so please run them only in your domain and some orchestrator will run the full thing?

Orbs eliminate the need for worktrees. They let me think more about my application and less about my resources...less about the "how".

— https://nitter.net/rockorager/status/2085079613726753183#m