onecommit

9 ms·

1.
by onecommit 6mo ago
interesting - thanks!
2.
by onecommit 6mo ago
How do models deal with assessing the quality of content and its accuracy/veracity when recommending products currently? What do the providers do to avoid a situation where more content === more traffic? Would love to see links to rele
3.
by onecommit 7mo ago
Yes! By default, every new task runs in its own worktree. In the .emdash.json config (or in the UI on your project page), you can specify setup, run, and teardown scripts -- pnpm install, pnpm run dev, etc. We also inject convenience env va
4.
by onecommit 7mo ago
Thanks! What tools have you been experimenting with? Agreed. That this evolution pushes much of the work into describing desired outcomes and giving sufficient context. To your questions: Emdash helps reduce the setup cost of each environme
5.
by onecommit 7mo ago
We could! Do you use them?
6.
by onecommit 7mo ago
We connect to remote servers via SSH, are provider-agnostic, and open-source. e.g. in Codex you can only run OpenAI models and not Gemini, Amp, you name it. Give it a spin :)
7.
by onecommit 7mo ago
Thank you for flagging! We had a CI bug in v0.4.16 that caused the compilation error that we patched in the latest release (v0.4.17). I created a ticket for the provider detection on remote servers. On it!
8.
by onecommit 7mo ago
On it! Released windows out of beta yesterday. signed version sometime this week
9.
by onecommit 7mo ago
Thank you, and yes!
10.
by onecommit 7mo ago
looking into this! Thanks for flagging
11.
by onecommit 7mo ago
We're figuring our business model out. There're two avenues that we principally think about (1) bundled coding agent subscription and (2)enterprise version with auth, team management, sharing of agent interactions. Admittedly, it&
12.
by onecommit 7mo ago
interesting! hadn't looked into sparse checkout before, but will do now. Initial thoughts are that sparse might be risky if we lose some arbitrary files that might be relevant context for the coding agents. Will look into this!
13.
by onecommit 7mo 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
14.
by onecommit 7mo 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
15.
by onecommit 7mo 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&#
16.
by onecommit 7mo ago
great! send all feedback our way :folded_hands:
17.
by onecommit 7mo 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
18.
by onecommit 7mo 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
19.
Show HN: Emdash – Open-source agentic development environment(github.com)
206 points by onecommit 7mo ago|71 comments
20.
Lix – universal version control system for binary files(lix.dev)
142 points by onecommit 8mo ago|57 comments
21.
Show HN: Emdash – OS UI for parallel coding agents and Linear tickets(github.com)
2 points by onecommit 11mo ago|0 comments