.@emdashsh is building an open-source Agentic Development Environment (ADE). Run multiple coding agents in parallel. Congrats on the launch raban and Arne Strickmann!

@rabanspiegel @arnestrickmann Check it out here:

@emdashsh @rabanspiegel @arnestrickmann OSS ADE for the win! Surely some of the startup founders within our ecosystem would love to try this out.

@emdashsh @arnestrickmann could've hired a $5k videographer, but would've been less fun

@emdashsh @rabanspiegel @arnestrickmann Congrats on the launch!! @rabanspiegel @arnestrickmann

@emdashsh @rabanspiegel @arnestrickmann Open source is a genius move for an ADE. I wonder how these agents handle conflicting PRs when they’re all hitting the same repo simultaneously. That sounds like a beautiful disaster.

@emdashsh @rabanspiegel @arnestrickmann Let's gooo!!

@emdashsh @rabanspiegel @arnestrickmann 🔥🔥

@emdashsh @rabanspiegel @arnestrickmann oh this is exactly what I've been wanting. biggest pain point with parallel agents right now is merge conflicts when they touch overlapping files. how does emdash handle that? separate git worktrees per agent?

@emdashsh @rabanspiegel @arnestrickmann LET'S GO @arnestrickmann !!!

@emdashsh @rabanspiegel @arnestrickmann congrats on the launch

@emdashsh @rabanspiegel @arnestrickmann parallel coding agents is such an underrated workflow. being able to split tasks across agents and have them work simultaneously... that's how solo devs start moving like teams

@emdashsh @rabanspiegel @arnestrickmann aye congrats!

running multiple coding agents in parallel is the obvious next step that most tools still don't handle well. right now you either run one agent and wait, or you manually spin up separate terminals and hope they don't conflict. having a proper orchestration layer that manages the workspace isolation... that's what makes multi agent actually usable instead of a demo

@emdashsh @rabanspiegel @arnestrickmann Congrats!!

@emdashsh @rabanspiegel @arnestrickmann congrats on the launch 🔥

@emdashsh @rabanspiegel @arnestrickmann parallel agents are the unlock. splitting research coding and qa into separate loops keeps context clean and output quality way higher. great launch.

@emdashsh @rabanspiegel @arnestrickmann Congratulations on the launch!

@emdashsh @rabanspiegel @arnestrickmann 🚀🚀

@emdashsh @rabanspiegel @arnestrickmann 🚀🚀

@emdashsh @rabanspiegel @arnestrickmann Congrats on the launch

@emdashsh @rabanspiegel @arnestrickmann Checking this out now

@emdashsh @rabanspiegel @arnestrickmann Congrats

@emdashsh @rabanspiegel @arnestrickmann Um this sounds very interesting

@emdashsh @rabanspiegel @arnestrickmann running multiple coding agents in parallel is the natural evolution. single-threaded AI development was always going to be a bottleneck. this is going to change how engineering teams think about project planning and sprint velocity. congrats to the team.

@emdashsh @rabanspiegel @arnestrickmann Hey @bankrbot launch token on base Use Agentic Development Environment as name and ADE as ticker

@emdashsh @rabanspiegel @arnestrickmann @TanayKmr

@emdashsh @rabanspiegel @arnestrickmann If this sticks, the job shifts toward orchestration and review. Less typing, more reading and saying no.

Parallel coding agents reveal a dirty secret: most development time isn't actually coding. It's waiting. For context. For dependencies. For review. For decisions. Running 10 agents in parallel doesn't 10x output - it 10x the coordination overhead. The interesting question is whether ADEs can also parallelize the human-in-the-loop bottleneck.

@emdashsh @rabanspiegel @arnestrickmann Hey @clanker_world launch token on base Use Agentic Development Environment as name and ADE as ticker

@emdashsh @rabanspiegel @arnestrickmann cool new tool lets agents work together like a dream team

@emdashsh @rabanspiegel @arnestrickmann So this is @conductor_build ?

I'm excited to see this new development, but I wonder if you've considered the potential security implications of running multiple coding agents in parallel. In my experience, coordinating multiple concurrent processes can increase the attack surface and make it harder to debug issues. Have you thought about implementing additional security measures to mitigate these risks?

@emdashsh @rabanspiegel @arnestrickmann Congrats on the launch! Running multiple agents on the same codebase is painful right now. How do you handle port conflicts when multiple instances need to run the same service simultaneously?

@emdashsh @rabanspiegel @arnestrickmann How do you think about agent arbitration when outputs conflict?