Desktop environment that runs coding-agent CLIs in parallel Git worktrees, passes in issues from trackers, and handles diffs, PRs, CI checks and scheduled runs.
Working through tracker issues with diffs, PRs, CI checks and scheduled runs in one desktop app.
Core features
- Sandboxed runsNo
Docs, changelog and repo code were searched for sandbox, docker, container and VM. Agents run directly on the local or SSH machine. Emdash cloud belongs to the unshipped, waitlist-only Emdash 2.0.
- Diff review YesSource
- Agent coordinationNo
Docs, changelog and repo code were searched for orchestrate, delegate, handoff, subagent and spawn. Parallel tasks run independently, and the only subagent mention is chat rendering of the agent's own subagents.
- Scheduled tasks YesSource
- Event triggersNo
Docs, changelog and repo code were searched for webhook and trigger. Automation runs are only cron or manual, and issues are passed to an agent by a person. Starting tasks from Slack, Linear or GitHub is advertised only for the unshipped Emdash 2.0.
- Team collaborationNo
Emdash Classic is a single-user desktop app whose only sharing is project settings committed in .emdash.json. Shared sessions, SSO and roles are advertised only for the unshipped, waitlist-only Emdash 2.0.
- API / CLI controlNo
Docs and repo were searched for CLI, API, MCP server and deep links. Emdash ships no user-facing command or API for starting sessions. Its MCP support only configures servers for agents, and the workspace server is an internal daemon.
Pricing
Free and open source. No paid tier found. A separate Emdash 2.0 for teams is waitlist-only with no published price.
Platforms
macOS, Windows, Linux
Research notes
OFFICIAL DOMAIN: emdash.com. emdash.sh redirects there and the repo homepage is emdash.com, though the README still links emdash.sh. Maker: General Action, Inc. (YC W26). Integration: the repo's AGENTS.md says TUI conversations run through PTY services and structured chat uses ACP, so ACP is a second path. Docs list 35 agent CLIs while the homepage says 25+. BYOK caveat: the API-key sentence is in the homepage FAQ, whose answer sits in JSON-LD and is not in the static visible text, so a checker that strips scripts may miss it. Emdash stores no provider keys for you as far as I read; it relies on each CLI's own auth. EMDASH 2.0 (emdash.com/waitlist) advertises 'desktop, web, mobile, or Slack', shared secrets and spend limits. That is unshipped and may add paid or hosted tiers, so it is not reflected in platforms or pricing. The site mentions cloud environments, but only via your own provisioning scripts, not vendor-hosted execution.