205 points by onecommit 5 days ago | 71 comments on HN
| Mild positive Landing Page · v3.7· 2026-02-26 03:15:57 0
Summary Open Access & Digital Participation Advocates
The Emdash repository on GitHub exemplifies open-source principles supporting freedom of expression, information access, and global participation in technical development. The content receives strong positive scores on Articles 13, 19, 26–27 (circulation of information, freedom of expression, education, and cultural participation) but faces persistent structural concerns regarding labor rights (Article 23–24), absolute intellectual property ownership (Article 17), and safeguards against misuse (Article 30). The platform-level GitHub infrastructure provides modest positive support through accessibility features and privacy protections, but behavioral analytics tracking creates privacy tension.
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?
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?
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.
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.
We are experimenting with this kind of development style and from my experience so far this shift a lot of the complexity of building into the story writing and manual testing phases.
As I will need to fully handover the task and let the agent(s) essentially one-shot the implementation I need to be way for specific and clear in giving it context and goals, otherwise I’m afraid it will start build code purely by accumulation creating a pile of unmanageable garbage.
Also changes which requires new UI components tend to require more manual adjustments and detailed testing on the UX and general level of polishing of the experience our users expect at this stage.
I’m starting to develop a feeling of tasks that can be done this way and I think those more or less represent 20 to 30% of the tasks in a normal sprint. The other 70% will have diminishing returns if not actually a negative return as I will need to familiarise with the code before being able to instruct AI to improve/fix it.
From your experience building this, what’s your take on:
1. How do your product helps in reducing the project management/requirements gathering for each individual tasks to be completed with a sufficient level of accuracy?
2. Your strong point seems to be in parallelisation, but considering my previous analysis I don’t see how this is a real pain for a small teams. Is this intended to be more of a tool for scale up with a stable product mostly in maintenance/enhancement mode?
3. Are you imagining a way for this tool to implement some kind of automated way of actually e2e test the code of each task?
I'm going to look into it soon, but since you might be hanging around here, I'll ask: do I have a quick way of telling the system how to actually creating a worktree efficiently?
Here's my problem: I want to do manual testing for several things, especially frontend related ones. However, every worktree needs its own ports, and specific particularities (e.g. so docker volumes don't collide). `git config --worktree` is supposed to help with this (and I'll be looking at it pretty soon), but it seems very primitive.
Is there a way for me to tell Emdash: "Hey, when you create a new worktree, you need to run this script"?
Thanks in advance and, once again, congrats on building something new, clearly in the direction we are going.
I just made an app that read GitHub issues. If they have a specific tag, the agent in the background creates a plan.
If they have another tag, the agent in the server creates a PR considering the whole issue conversation as context (with the idea that you used the plan above - but technically you don't have to.)
If you comment in the PR the agent start again loading your comment as context and trying to address it.
Everything is already in git and GitHub, so it automatically pick up your CI.
It seems simpler, but I am sure I missed something.
Will you add remote / a mobile control plane? I love your approach of using CLI. https://yepanywhere.com/ has a similar approach but it's mainly about access via mobile. [I'm frequently away from my desk]
Ah, actually after looking at your approach, I see you don't use any agent SDK or --json outputs. You just embed a terminal window. That makes mobile interfaces a non-starter. I can see why you are only focusing on desktop, it makes integrating with more providers easier.
Custom AI tools like these have an uphill battle to fight. Automaker[0] from webdevcody is an example of that. He, together with some other folks created an open source Agentic Coding tool (for the lack of a better term), which gained popularity on github. He was advertising/showcasing it on streams etc. A few weeks in, he posted a video[1] where he speaks about why he's not using it himself anymore and went back to Claude Code, which over time receives tools/skills/mcps/whatnot and is in the terminal which we're all familiar with.
I made similar experience. Downloaded all sorts of tools, IDE's for the new era of development. Other than claude code in cli and occasional uses of codex (because have free tokens), nothing else stuck. I can just split my terminal effortlessly how many times I want, write/speak to the terminal with any custom request etc. And once someone comes up with a clever idea on top of what claude has today, I reckon they'll add it one way or another within the next weeks.
bayesian curve meme fits here rather well:
- claude code for everything, custom IDE's/tools, claude code for everything.
The worktree isolation is clever, but I'm curious about the security model when you're running multiple agents in parallel with shell access.
In my experience running CLI-based agents, the biggest risk isn't the agent "going rogue" in the sci-fi sense — it's context window drift during long sessions. Agent compacts its history, loses track of which worktree it's in, and starts editing files in the wrong branch. Or worse, running tests against the wrong database.
Git worktrees help with file isolation, but they share the same .git directory and can still interfere with each other during concurrent operations (rebases, reflog contention). Have you run into this with 5+ parallel agents?
The native CLI approach is smart for staying current with provider features, but it does mean you're trusting each provider's sandboxing. Some are better than others. Claude Code's allowlists are reasonably paranoid; others less so.
Nice to see someone building tooling for this workflow rather than trying to replace the terminal entirely.
I've tried to load tasks that were refined locally, but that turned into a bunch of shell scripts to access the local DB. Will you support that until you provide a way to do the planning phase in the UI?
---
Also I've loaded 78 tasks and the UI is crawling to a halt
If gpl is a blocker for users then offer them a paid license with the exceptions they want. But MIT allows a commercial entity to ingest your code, close source it, and commercialize it .
GPL-3 (with the option of custom commercial licenses) seems strictly superior to MIT in this respect. Can you help me understand why this choice is so popular?
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?
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.
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 :)
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's early and this can change. What won't change is that this UI layer for running multiple coding agents is and will be open-source. Emdash itself is funded by YC. Initially developed as a tool while working on another product, but we weren't funded then.
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 :)
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 environment by allowing you to open an isolated git worktree, copying over env variables and other desired context. And then preserving your conversation per task. That said, you still need to write clear goals and point it in the right direction.
I think it's less about team scale and more about individual throughput. My working mode is that I'm actively working on one or two tasks, switching between them as one runs. Then I have a long list of open tasks in the sidebar that are more explorative, quick reviews, issue creation etc. So for me it's not about one-shotting tasks, but instead about navigating between them easily as they're progressing
Automated e2e testing is tricky, particularly for rendering. I think roborev (https://github.com/roborev-dev/roborev) is moving in the right direction. Generating bug reports synchronously per commit and not just once you create a PR. I also think what https://cursor.com shipped today with computer-use agents testing interfaces is very interesting.
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 vars into every task. For example, $EMDASH_PORT gives each task a unique port, so you can do PORT=$EMDASH_PORT pnpm run dev and never collide on dev servers.
Repository description and code are openly published for global audience; contributors express ideas through code, documentation, and discussion without prior censorship.
FW Ratio: 57%
Observable Facts
Repository is fully public with no access restrictions on viewing code or documentation.
GitHub's issue and discussion systems enable contributors to publish opinions and critiques.
Repository title and description are visible to global audience without content filtering.
Code comments and commit messages enable contributors to express reasoning without editorial review.
Inferences
Public repository structure removes barriers to expression and information dissemination.
Platform-level freedom of speech protections enable open technical discussion.
Open-source licensing explicitly permits reproduction and distribution of ideas.
Open-source licensing model supports freedom of thought by enabling open exchange of ideas without ideological gatekeeping; technical documentation presents information for independent evaluation.
FW Ratio: 60%
Observable Facts
Repository content is publicly accessible for independent review and critique.
GitHub's discussion and issue systems enable open exchange of technical ideas.
No visible censorship or ideological restrictions on code or documentation.
Inferences
Public repository structure supports freedom of thought through transparent code review.
Open-source model presumes intellectual pluralism and independent evaluation.
Repository supports education and technical development through open-source documentation, code examples, and community learning; accessible to global audience for skill development.
FW Ratio: 57%
Observable Facts
Repository description explicitly positions Emdash as development environment supporting learning and skill acquisition.
Code and documentation provide educational resources freely accessible to global users.
GitHub's responsive design and keyboard navigation enable users with diverse abilities to access educational content.
Open-source licensing permits reproduction and distribution of educational materials.
Inferences
Public repository structure democratizes access to technical education without financial barriers.
Platform accessibility features enable equitable educational access.
Open-source model supports right to education through free knowledge-sharing.
Repository is explicitly positioned as participation in cultural and scientific life of community; open-source model enables participation in technological culture.
FW Ratio: 57%
Observable Facts
Repository title frames Emdash as participating in agentic development culture with Y Combinator affiliation.
Open-source licensing enables benefiting from and contributing to collective scientific advancement.
GitHub community enables participation in collaborative technical culture.
Code and documentation enable authors and contributors to share benefits of scientific progress.
Inferences
Open-source structure enables participation in technological and scientific culture.
Platform supports sharing of benefits from technical advancement through knowledge-sharing.
Community-driven development enables contributors to participate in culture.
Repository description frames open-source agentic development as democratizing access to advanced coding tools, implicitly supporting human dignity and equal opportunity in technology development.
FW Ratio: 60%
Observable Facts
Repository title describes 'Emdash' as 'Open-Source Agentic Development Environment' with YC W26 affiliation.
Repository is publicly accessible on GitHub without access restrictions.
Open-source model presumes social and international order respecting rights expressed in UDHR; community norms support collective human rights framework.
FW Ratio: 60%
Observable Facts
Repository operates within GitHub's community guidelines establishing baseline human rights standards.
Open-source licensing framework presumes international legal order respecting intellectual property and freedom.
Global platform structure supports international cooperation on technical rights.
Inferences
Open-source community presumes legal framework supporting UDHR principles.
Platform architecture enables international cooperation respecting human rights.
Repository contributes to social and technical development through open-source knowledge-sharing; access to development tools supports social advancement.
FW Ratio: 60%
Observable Facts
Repository provides free access to development tools and code supporting technical advancement.
GitHub's keyboard navigation and ARIA support enable users with disabilities to access content.
Open-source model enables global access to development knowledge without financial barriers.
Inferences
Open-source distribution supports right to adequate standard of living through free access to technical resources.
Platform accessibility features enable equitable access regardless of ability status.
Repository does not address rest, leisure, or reasonable working hours for contributors; open-source development enables unlimited demands on contributor time.
FW Ratio: 60%
Observable Facts
Repository issues and discussions may generate unlimited demands on contributor time.
No visible mechanisms ensuring contributor rest, vacation, or work-life balance.
Open-source maintenance expectations create potential for overwork.
Inferences
Voluntary contribution structure lacks protections for reasonable working hours or rest.
Platform enables continuous demands on maintainer time without formal limitations.
Repository does not address labor rights, fair wages, or working conditions for developers; open-source contributors may lack formal employment protections.
FW Ratio: 60%
Observable Facts
Repository is maintained through voluntary contribution without visible compensation mechanisms.
GitHub does not provide employment protections or wage guarantees for open-source contributors.
No visible discussion of contributor compensation, working hours, or labor standards.
Inferences
Voluntary contribution model lacks formal labor rights protections for contributors.
Open-source structure enables unpaid labor without workplace protections.
Repository does not visibly address community duties or limitations on rights; open-source model emphasizes freedom without corresponding community responsibilities.
FW Ratio: 60%
Observable Facts
Repository description emphasizes freedom and openness without corresponding articulation of contributor responsibilities.
GitHub community guidelines exist but enforcement appears asymmetrical toward protecting expression over enforcing duties.
No visible discussion of contributor obligations or limitations on rights.
Inferences
Open-source framing emphasizes individual freedoms without balancing community duties.
Platform guidelines reflect rights-protective rather than duty-enforcing orientation.
Repository does not contain safeguards against misuse of rights to abolish human rights; open-source licensing permits use for any purpose including potentially harmful applications.
FW Ratio: 50%
Observable Facts
Repository license (inferred as permissive open-source) does not restrict use for harmful purposes.
GitHub's access model permits download and reuse of code without human rights verification.
No visible safeguards preventing use of code for surveillance, discrimination, or rights violations.
Inferences
Open-source licensing model lacks ethical restrictions on potential misuse of technical tools.
Platform enables unrestricted distribution without human rights impact assessment.
No visible mechanisms to prevent use of agentic development tools for harmful purposes.
GitHub's access_model (+0.12) and editorial_code (+0.08) modifiers indicate platform supports open expression; cached DCP confirms discussion board model enables open participation without gatekeeping.
GitHub's global public access model supports unrestricted movement of information; cached DCP notes access_model modifier (+0.12) affirms open participation.
GitHub's access_model (+0.12) and editorial_code (+0.08) modifiers support participation in open-source culture; platform enables contributors to benefit from scientific and technical advancement.
GitHub's public forum structure enables participants to engage with ideas freely; cached DCP notes editorial_code modifier (+0.08) protects expression within community.
GitHub enables formation of contributor communities through issues, discussions, and pull requests; platform supports voluntary association without mandatory participation.
GitHub's accessibility features noted in cached DCP (+0.15) enable equitable access to repository content; platform design supports standard of living improvements through access to development resources.
GitHub's public repository model enables global participation without gatekeeping, supporting the Preamble's vision of freedom and equality in knowledge-sharing.
GitHub's platform design and cached DCP confirm structural support for rights through privacy protections (+0.1), accessibility (+0.15), and equal treatment (+0.05).
GitHub's community features enable users to access social support and resources; cached DCP notes public discussion board model supports knowledge dissemination.
GitHub platform does not guarantee labor protections, fair compensation, or working conditions for open-source contributors; contributors participate voluntarily without formal employment rights.
GitHub structure does not provide protections for rest or leisure; contributors can be expected to respond to issues without limitation on working hours.
GitHub's terms establish some community expectations through guidelines, but cached DCP notes editorial_code (+0.08) indicates protections for expression exceed enforcement of correspondent duties.
GitHub's platform does not restrict use of code for purposes that might violate human rights; open-source licensing enables unrestricted reuse without ethical guardrails.
GitHub's platform control over content hosting and cached DCP ownership modifier (-0.05) indicate conditional rather than absolute intellectual property rights for users.
GitHub platform provides issue tracking and community reporting mechanisms; cached DCP notes community guidelines establish standards for dispute resolution.
GitHub's democratic issue voting (reactions, stars) provides minimal analog to political participation in technical governance; cached DCP notes platform provides community guidelines for decision-making.
Supplementary Signals
How this content communicates, beyond directional lean. Learn more
Repository description emphasizes 'YC W26' (Y Combinator affiliation) without substantive justification, leveraging institutional prestige to enhance credibility.
loaded language
Term 'Open-Source Agentic Development Environment' combines positive framing ('open-source', 'development') without acknowledging potential governance or safety concerns.
build 1ad9551+j7zs · deployed 2026-03-02 09:09 UTC · evaluated 2026-03-02 11:31:12 UTC
Support HN HRCB
Each evaluation uses real API credits. HN HRCB runs on donations — no ads, no paywalls.
If you find it useful, please consider helping keep it running.