Hacker Newsnew | past | comments | ask | show | jobs | submit | more onecommit's commentslogin

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.


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!


Judging from the installer sizes it's electron, not tauri?


great! send all feedback our way :folded_hands:


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.


> CLIs themselves are getting good at [agent coordination] natively

But that's not provider-agnostic, which you mentioned earlier as one selling point of Emdash. :-)

Not-so-unrealistic use case, IMO: What if I want my orchestrator model to be, for example, ran locally due to some form of privacy concerns?


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?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: