frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Open in hackernews

Show HN: Emdash – Open-source agentic development environment

https://github.com/generalaction/emdash
43•onecommit•3h ago
Hey HN! We’re Arne and Raban, the founders of Emdash (https://github.com/generalaction/emdash).

Emdash is an open-source and provider-agnostic desktop app that lets you run multiple coding agents in parallel, each isolated in its own git worktree, either locally or over SSH on a remote machine. We call it an Agentic Development Environment (ADE).

You can see a 1 minute demo here: https://youtu.be/X31nK-zlzKo

We are building Emdash for ourselves. While working on a cap-table management application (think Stripe Atlas + Pulley), we found our development workflow to be messy: lots of terminals, lots of branches, and too much time spent waiting on Codex.

Emdash puts the terminal at the center and makes it easy to run multiple agents at once. Each agent runs as a task in its own git worktree. You can start one or a few agents on the same problem, test, and review.

Emdash works over SSH so you can run agents where your code lives and keep the parallel workflow. You can assign tickets to agents, edit files manually, and review changes.

We also spent time making task startup fast. Each task can be created in a worktree, and creating worktrees on demand was taking 5s+ in some cases. We now keep a small reserve of worktrees in the background and let a new task claim one instantly. That brought task start time down to ~500–1000ms depending on the provider. We also spawn the shell directly and avoid loading the shell environments on startup.

We believe using the providers’ native CLIs is the right approach. It gives you the full capabilities of each agent, always. If a provider starts supporting plan mode, we don't have to add that first.

We support 21 coding agent CLIs today, including Claude Code, Codex, Gemini, Droid, Amp, Codebuff, and more. We auto-detect what you have installed and we’re provider-agnostic by design. If there’s a provider you want that we don’t support yet, we can add it. We believe that in the future, some agents will be better suited for task X and others for task Y. Codex, Claude Code, and Gemini all have fans. We want to be agnostic and enable individuals and teams to freely switch between them.

Beyond orchestration, we try to pull most of the development loop into Emdash. You can review diffs, commit, open PRs, see CI/CD checks, and merge directly from Emdash once checks pass. When starting a task, you can pass issues from Linear, GitHub, and Jira to an agent. We also support convenience variables and lifecycle scripts so it’s easy to allocate ports and test changes.

Emdash is fully open-source and MIT-licensed.

Download for macOS, Linux or Windows (as of yesterday !), or install via Homebrew: brew install --cask emdash.

We’d love your feedback. How does your coding agent development setup look like, especially when working with multiple agents? We would want to learn more about it. Check out our repository here: https://github.com/generalaction/emdash

We’ll be around in the comments — thanks!

Comments

das-bikash-dev•1h ago
How does Emdash handle state management when running multiple agents on the same codebase? Particularly interested in how you prevent conflicts when agents are making concurrent modifications to dependencies or config files. Also, does it support custom agent wrappers, or do you require the native CLI?
esafak•1h ago
> Each agent runs as a task in its own git worktree

If you're talking about shared services, that's another matter.

onecommit•1h ago
Thanks for your questions! You can separate the agents in Emdash by running them on separate git worktrees so they can do concurrent modifications without interfering. We don't support custom agent wrappers currently, interesting. Have you written your own? What is your use case for them over native CLIs?
FiloVenturini•1h ago
Have you considered adding any kind of agent coordination layer, e.g. letting one “orchestrator” agent spawn and direct sub-agents on specific subtasks, rather than having the developer manually assign each task? Or is the explicit human-in-the-loop assignment a deliberate design choice to keep control and avoid runaway costs?
onecommit•1h ago
We've considered it! The way we're seeing it, this is something that the CLIs themselves are getting good at natively, such as Claude Code. We generally consider ourselves to be at a higher abstraction / task level, where the individual CLIs are responsible themselves for breaking down and distributing a larger task across subagents.
selridge•1h ago
Looks cool! Thank you for sharing.
thesiti92•1h ago
i'll have to give it a shot, the market needs an open source cursor right now
onecommit•1h ago
great! send all feedback our way :folded_hands:
ahmadyan•59m ago
Congrats on the launch
redrove•54m ago
Is this another VSCode fork? I can’t tell from the readme.
onecommit•46m ago
Not in its purest sense! We're using the monaco editor for file editor and diffs, but other than that no VScode included. The file editor is really a secondary view inside of Emdash. The focus is on the chat with the coding agent. We'll make this more clear in the readme. Thanks for the feedback!
timsuchanek•49m ago
Let's go! Love that this is a solid OSS alternative to what's already out there!
haimau•39m ago
Been driving my agents (CC, currently testing Pi) for a couple of weeks via Emdash. Finally, got a productive worktree setup working. There were still rough edges when I started, but the team has shipping fast [0] and is vaporizing concerns on the fly. Building on top of the native CLI seems to be the right strategy as well.

[0] https://github.com/generalaction/emdash/releases/

umairnadeem123•32m ago
the worktree-per-agent approach is the right call. we run a similar setup with claude code subagents and the biggest lesson was that filesystem isolation is non-negotiable for parallel agents - even with git branches, agents stepping on each others lockfiles and node_modules was a constant source of weird failures.

the 500ms task startup from pre-warmed worktrees is a nice touch. we found that cold worktree creation was one of those things that felt fast enough in demos but became a real friction point when you are spinning up 5-10 agents per session.

straydusk•23m ago
Pretty sick. How do you compare yourself with Conductor?
onecommit•16m ago
Conductor is definitely in the same space. Main points of differentiation that I am aware of are that we allow you to connect to remote servers via SSH, natively embed many more coding agents (21) with their full functionality, and are open-source.
leondri17•20m ago
LFG!
mccoyb•15m ago
Here's my question:

if agents continue to get better with RL, what is future proof about this environment or UI?

I think we all know that managing 5-10 agents ... is not pretty. Are we really landing good PRs with 100% cognitive focus from 5-10 agents? Chances are, I'm making mistakes (and I assume other humans are too)? Why not 1 agent managing 5-10 agents for you? And so on?

Most of the development loop is in bash ... so as long as agents get better at using bash (amongst other things), what happens to this in 6 months?

I don't think this is operating at a higher-level of abstraction if agents themselves can coordinate agents across worktrees, etc.

onecommit•6m ago
Interesting thoughts - thank you! And directionally agree - given that agents are becoming ever better, they'll take more and more of the orchestration on themselves. Still, we believe that developers need an interface to interact with these agents; see their status and review / test their work. Emdash is our approach for building this interface of the future - the ADE :)
snowhale•10m ago
the worktree pre-warming detail is interesting -- keeping a reserve pool and letting new tasks claim one instantly is the same pattern as connection pool pre-warming in databases. the underlying bottleneck is probably git having to traverse pack files and update the index when you run 'git worktree add'. one thing worth trying if you haven't: sparse checkout on the worktrees can cut that initialization time further, especially in large monorepos where most files are irrelevant to a given agent task.

Show HN: Emdash – Open-source agentic development environment

https://github.com/generalaction/emdash
43•onecommit•3h ago•20 comments

Show HN: Chaos Monkey but for Audio Video Testing (WebRTC and UDP)

https://github.com/MdSadiqMd/AV-Chaos-Monkey
14•MdSadiqMd•1d ago•3 comments

Show HN: ProdRescue AI – Turn Slack war-rooms and raw logs into incident reports

https://www.prodrescueai.com/
2•devrimozcay•34m ago•0 comments

Show HN: Cost per Outcome for AI Workflows

https://github.com/botanu-ai/botanu-sdk-python
3•deborahjacob•39m ago•1 comments

Show HN: Claude Code Canvas

https://github.com/raulriera/claude-code-canvas
3•raulriera•55m ago•1 comments

Show HN: X86CSS – An x86 CPU emulator written in CSS

https://lyra.horse/x86css/
249•rebane2001•18h ago•82 comments

Show HN: enveil – hide your .env secrets from prAIng eyes

https://github.com/GreatScott/enveil
185•parkaboy•16h ago•119 comments

Show HN: Interactive 3D Moon with real NASA data and WebGPU

https://moon.oddurs.com
2•oddurs•1h ago•0 comments

Show HN: Open-Weight Image-Video VAE (Better Reconstruction ≠ Better Generation)

https://www.linum.ai/field-notes/vae-reconstruction-vs-generation
3•schopra909•2h ago•1 comments

Show HN: Ghist – Task management that lives in your repo

https://github.com/unnecessary-special-projects/ghist
12•nxnze•4h ago•0 comments

Show HN: Steerling-8B, a language model that can explain any token it generates

https://www.guidelabs.ai/post/steerling-8b-base-model-release/
308•adebayoj•20h ago•88 comments

Show HN: Babyshark – Wireshark made easy (terminal UI for PCAPs)

https://github.com/vignesh07/babyshark
136•eigen-vector•1d ago•46 comments

Show HN: Cellarium: A Playground for Cellular Automata

https://github.com/andrewosh/cellarium
38•andrewosh•3d ago•1 comments

Show HN: MasqueradeORM – Memory Efficient Node ORM: Just Write Classes

https://github.com/MasqueradeORM/MasqueradeORM
3•masqueradeorm•3h ago•1 comments

Show HN: Sowbot – Open-hardware agricultural robot (ROS2, RTK GPS)

https://sowbot.co.uk/
175•Sabrees•1d ago•46 comments

Show HN: AI Timeline – 171 LLMs from Transformer (2017) to GPT-5.3 (2026)

https://llm-timeline.com/
167•ai_bot•1d ago•58 comments

Show HN: PgDog – Scale Postgres without changing the app

https://github.com/pgdogdev/pgdog
312•levkk•1d ago•57 comments

Show HN: Making an 1800mah e-ink device last up to 6 months

https://trmnl.com/blog/power-efficiency
6•ryanckulp•1h ago•0 comments

Show HN: TTSLab – Text-to-speech that runs in the browser via WebGPU

https://ttslab.dev
2•MbBrainz•5h ago•0 comments

Show HN: Hacker Smacker – spot great (and terrible) HN commenters at a glance

https://hackersmacker.org
3•conesus•2h ago•0 comments

Show HN: CIA World Factbook Archive (1990–2025), searchable and exportable

https://cia-factbook-archive.fly.dev/
484•MilkMp•2d ago•99 comments

Show HN: Awsim – Lightweight AWS emulator in Go (40 services in progress)

https://github.com/sivchari/awsim
3•sivchari•6h ago•0 comments

Show HN: L88 – A Local RAG System on 8GB VRAM (Need Architecture Feedback)

9•adithyadrdo•16h ago•1 comments

Show HN: AI-native SDLC – 156 test docs, 16 skills, 1 human

https://github.com/gpgkd906/auth9
3•gpgkd906•6h ago•1 comments

Show HN: Dicta.to – Local voice dictation for Mac with on-device AI

https://dicta.to/
2•alamparelli•6h ago•0 comments

Show HN: AI phone assistant that became a lifeline for people who can't speak

https://mio.gg/
3•talyuk•7h ago•1 comments

Show HN: A Hacker News–style site focused on European tech

https://techposts.eu
5•davedx•7h ago•2 comments

Show HN: Tessera – An open protocol for AI-to-AI knowledge transfer

https://github.com/incocreativedev/tessera-core
3•kirkmaddocks•7h ago•2 comments

Show HN: WebPerceptor – Enabling AI Mediated Web Browsing

https://github.com/theartofhci/WebPerceptor
2•theartofhci•8h ago•0 comments

Show HN: Claude Copy – Drop-in fix for Claude Code's broken copy-paste

https://github.com/andersmyrmel/claude-copy
2•andersmyrmel•8h ago•0 comments