Rida Al Barazi

I build agent infrastructure and write about what goes wrong. Mostly what goes wrong.

[Rida Al Barazi @rida]

When you're juggling multiple Claude coding sessions and your local env becomes the bottleneck:

I built something for a safer YOLO mode:

./bin/feature-start oauth

→ Isolated worktree + container + DB + live URL
→ Ready for Claude/Codex
→ 10 seconds

Zero conflicts. /1

[Rida Al Barazi @rida]

I had to restructure my entire workspace folder to optimize it for other models. Split my tasks where 80% is done by MiniMax and GPT and the remaining 20% that’s critical is still using Opus. I’m still spending 2x the Max20 subscription in tokens but it’s a huge improvement from the 20x before.

Pro Tip: Open your workspace and .openclaw folders in Claude code and use Opus to help you do the restructuring.

[Rida Al Barazi @rida]

@robjama @ahmednadar You got me

[Rida Al Barazi @rida]

@ryancarson @DevinAI @openclaw I've been trying to get that working on my own for a while and it's really a pain if you have a complex app with integrations. How easily did it pick up your app stack (db, infra, etc..)? For example, will it be able to test 3rd party integrations with Google, Stripe, etc..?

[Rida Al Barazi @rida]

@rachelnabors Port conflicts are the visible symptom. The silent killer is two worktrees running migrations against the same database in parallel. Portless + per-worktree containers covers both layers.

[Rida Al Barazi @rida]

@kovyrin Same. I tried to use OpenClaw to orchestrate a bunch of Claude Code and Codex sessions in separate worktrees but it was way too clunky.

[Rida Al Barazi @rida]

@andrewmichaelsa @meetblueberry The worktree support is the standout feature here. File-level isolation is step one though. When each worktree needs its own ports, DB, and Docker network, that's where most setups still fall apart.

[Rida Al Barazi @rida]

@dgalarza The .env.local per worktree is solid for DB isolation. Where I ran into trouble was ports and Docker networks. Two worktrees both wanting port 3000, or sharing the same Redis. Ended up wrapping the whole environment in per-worktree containers.

[Rida Al Barazi @rida]

@alexandertweak @aarondfrancis The env var thing kills you silently too. Two worktrees pointing at the same DB, running migrations in parallel. I built isolated containers per worktree with dedicated tunnels for preview. Check it out at https://t.co/qBtksWVtyF

[Rida Al Barazi @rida]

This is the second time I hear about dagger this month. I gotta check it out.

I ended up building https://t.co/h8q0amZElj to solve the same problem. Each worktree gets its own container, ports, DB, tunnel. Right now it’s coupled to dev containers. Dagger sounds like it could be a good alternative

[Rida Al Barazi @rida]

Following the worktrees conversation today. The consensus is clear: worktrees are the way for parallel agent work. But file isolation is just the start.

Agents also share ports, databases, env vars, and Docker networks. That's the collision layer nobody talks about.

[Rida Al Barazi @rida]

@M4XMXM That's exactly what I ended up building BranchBox for. Each worktree gets its own container, ports, DB, tunnel. The file isolation is the easy part, it's everything else that collides.

[Rida Al Barazi @rida]

@nearestnabors @aarondfrancis @joelhooks https://t.co/uckMfkcFlA

[Rida Al Barazi @rida]

@teknopawn We hit the same .env pain. Solved it by auto-mounting dotfiles into each worktree's container. The isolation is in the runtime, not the filesystem. Keeps everything local and fast.

[Rida Al Barazi @rida]

@drewdil @andrewchen That M1 Pro holding up multiple agents is impressive. What are you using for the orchestration layer? I ended up building a CLI that handles worktree + container + DB + tunnel creation in one command.

[Rida Al Barazi @rida]

@garybasin @runaway_vol 'Shifting the problem left' resonates. For me that meant: don't try to coordinate agents on shared state. Give each one a fully isolated environment. The merge is the only coordination point.

[Rida Al Barazi @rida]

@MingtaKaivo @jpschroeder The merge conflict piece is real. What helped me was giving each agent its own container + DB + ports via worktrees, so they can't collide on shared state. File conflicts still happen but are way easier to resolve when the runtime environment isn't also tangled.

[Rida Al Barazi @rida]

@nearestnabors @aarondfrancis @joelhooks I automated this with BranchBox `branchbox feature start` creates the worktree, container, DB, ports, Docker network. One command. The missing piece for me was that worktree file isolation isn't enough.. agents still collide on ports and database state.

[Rida Al Barazi @rida]

Identity management for agents is the thing nobody talks about but everyone hits. You don't notice it until you're 4 agents deep and realize you've spent your afternoon in IAM consoles instead of shipping. First-class concern. Full stop.

[Rida Al Barazi @rida]

This is exactly the problem that pushed me to build BranchBox. Same pattern: worktrees are perfect for parallel agent work until the environment falls apart. We auto-isolate everything: DB, ports, Docker network, even Cloudflare tunnels. Stack-agnostic, so it works for Laravel, Rails, Node, whatever. The setup tax per worktree should be zero.