Emdash is an open-source desktop app for running multiple coding agents in parallel; one place to monitor sessions, review diffs, and turn issues into PRs.
@natalia_iankovych yes, you can! Emdash launches the 'real' Claude CLI in a terminal per task, so each new task inherits whatever account you're logged into globally. To switch, you claude logout / claude login and your next task picks up the new account
Report
The git worktree isolation per agent is the right call.. running multiple agents on the same working directory is a disaster waiting to happen. I've thought about this exact problem building multi-agent systems with LangGraph, and file-level conflicts between parallel agents are subtle and annoying to debug. Curious how you handle MCP server config sync across agents though.. if each agent gets the same MCP tools but they're writing to shared state like a database or vector store, does Emdash enforce any coordination or is that left entirely to the developer?
Report
The parallel diff review UI is genuinely clever. Monitoring multiple agent sessions without window switching solves a real pain. We've been running separate coding agents for different services and the context switching overhead adds up fast. How do you handle merge conflicts when two agents modify the same file simultaneously? Does Emdash queue operations, lock files, or surface conflicts for manual resolution?
Report
Running multiple agents with a unified diff view is a genuinely clever approach. The hardest part of parallel agent workflows isn't spawning them, it's knowing what changed and why. Building RetainSure, we've hit this exact problem managing concurrent coding sessions. How do you handle session isolation? Do agents share a filesystem or get containerized workspaces to prevent cross-contamination?
Congrats on the launch! How would you describe emdash to be different from other projects in this space? For which kind of users is emdash the best product?
@marc_klingen thank you Marc! Langfuse has been a big inspiration to us, especially on open-source and 'docs are product'. Though admittedly our docs need more love. 😀
I think the main difference is flexibility.
You can use the provider you want, with the issue tracker you use, on the OS you’re on. Agents can run locally or on your own machines over SSH.
Another critical differentiation (particularly with last weeks policy updates from Anthropic): We run the actual CLIs in our terminal emulator. So you get the real Claude Code, Codex, Gemini, OpenCode, etc. experience, with the latest models. ✨
Emdash is best for engineers and teams who already code nearly exclusively with coding agents nearly exclusively, and want a cleaner way to run them across providers and machines with a deep git integration and easy way to review changes.
Nice. That can make my life much easier. What features that come up in the next few weeks are you most excited about? Can you share a bit more about the roadmap?
@mikemahlkow wow, thank you! Big fan of Fastgen here!
We're really excited about remote development in general. With coding agents more than ever it makes sense to move development to the cloud for (1) session persistence, (2) scale (not eating all your RAM while running 10+ agents), and (3) accessibility across devices. That way you can access session from desktop, web, and mobile. We'll launch lots in that direction next :)
Congrats on the launch! Parallel agent sessions with a unified diff view is exactly where the workflow needed to go. The PR-from-issue flow is particularly smart for async teams. What's the mental model for context isolation between sessions?
@tonyspiro thanks Tony! Each task has its own git worktree so the code changes in sessions/tasks are fully isolated. Ports, dbs, and node_modules e.g. are still shared across tasks on a given device. We make that easy to handle with convenience variables to give you different ports per task e.g. and we'll launch more complete isolation soon! :)
Can I run multiple Claude Code licenses (accounts) and split tasks between them?
Emdash
@natalia_iankovych yes, you can! Emdash launches the 'real' Claude CLI in a terminal per task, so each new task inherits whatever account you're logged into globally. To switch, you claude logout / claude login and your next task picks up the new account
The git worktree isolation per agent is the right call.. running multiple agents on the same working directory is a disaster waiting to happen. I've thought about this exact problem building multi-agent systems with LangGraph, and file-level conflicts between parallel agents are subtle and annoying to debug. Curious how you handle MCP server config sync across agents though.. if each agent gets the same MCP tools but they're writing to shared state like a database or vector store, does Emdash enforce any coordination or is that left entirely to the developer?
The parallel diff review UI is genuinely clever. Monitoring multiple agent sessions without window switching solves a real pain. We've been running separate coding agents for different services and the context switching overhead adds up fast. How do you handle merge conflicts when two agents modify the same file simultaneously? Does Emdash queue operations, lock files, or surface conflicts for manual resolution?
Running multiple agents with a unified diff view is a genuinely clever approach. The hardest part of parallel agent workflows isn't spawning them, it's knowing what changed and why. Building RetainSure, we've hit this exact problem managing concurrent coding sessions. How do you handle session isolation? Do agents share a filesystem or get containerized workspaces to prevent cross-contamination?
Langfuse
Emdash
@marc_klingen thank you Marc! Langfuse has been a big inspiration to us, especially on open-source and 'docs are product'. Though admittedly our docs need more love. 😀
I think the main difference is flexibility.
You can use the provider you want, with the issue tracker you use, on the OS you’re on. Agents can run locally or on your own machines over SSH.
Another critical differentiation (particularly with last weeks policy updates from Anthropic): We run the actual CLIs in our terminal emulator. So you get the real Claude Code, Codex, Gemini, OpenCode, etc. experience, with the latest models. ✨
Emdash is best for engineers and teams who already code nearly exclusively with coding agents nearly exclusively, and want a cleaner way to run them across providers and machines with a deep git integration and easy way to review changes.
Fastgen
Nice. That can make my life much easier. What features that come up in the next few weeks are you most excited about? Can you share a bit more about the roadmap?
Emdash
@mikemahlkow wow, thank you! Big fan of Fastgen here!
We're really excited about remote development in general. With coding agents more than ever it makes sense to move development to the cloud for (1) session persistence, (2) scale (not eating all your RAM while running 10+ agents), and (3) accessibility across devices. That way you can access session from desktop, web, and mobile. We'll launch lots in that direction next :)
Cosmic
Congrats on the launch! Parallel agent sessions with a unified diff view is exactly where the workflow needed to go. The PR-from-issue flow is particularly smart for async teams. What's the mental model for context isolation between sessions?
Emdash
@tonyspiro thanks Tony! Each task has its own git worktree so the code changes in sessions/tasks are fully isolated. Ports, dbs, and node_modules e.g. are still shared across tasks on a given device. We make that easy to handle with convenience variables to give you different ports per task e.g. and we'll launch more complete isolation soon! :)