Compare ·
Scape vs Emdash
Emdash, from General Action, is an open-source agentic development environment for running coding agents in parallel.[1] Here is how it compares with Scape, with a source for every claim about Emdash.
| Feature | Scape | Emdash |
|---|---|---|
| Agents | ||
| Agents | Claude Code, Codex, Copilot, Cursor, OpenCode, pi, omp and Kimi Code, on your own subscriptions. | More than 25, including Claude Code, Codex, Cursor, OpenCode, Amp, Devin, Qwen Code, Droid and Copilot.[1][2] |
| Manager agent (Argus) | Argus reads your mission, starts child agents in their own worktrees, checks on them, and keeps a log table. You choose which agent and model its children run on, and can restart it on another agent without losing them. | No. |
| Agent rooms | Chat rooms where agents and people work one problem together, such as Claude and Codex debating an approach. | No. |
| Messages between sessions | One agent can message or direct another session. | No. |
| Agent review | Adversarial review: a second agent reviews the first one's diff (/scape-codex-review ships with Scape). | No. |
| Watchdogs | Supervisors that spot stuck sessions and auto-answer questions and permission gates (Claude Code). | An auto-approve option skips permission prompts for file operations on supported agents.[3] |
| Automation | ||
| Playbooks | Step-by-step automations that chain shell commands, agent prompts, HTTP calls and Scape tools. Lock one and it runs as a fixed script. | No. |
| Scheduler | A per-project calendar that runs playbooks and messages Argus, once or daily, weekly or monthly, while Scape is open. | Scheduled repeat work.[1] |
| Triggers | Run a playbook or prompt Argus when a webhook arrives, an integration record changes, a table query matches, or a calendar event happens. You arm each one. | No. |
| Working with people | ||
| Flight Plans | One shared, end-to-end encrypted plan for any number of people and their agents. Every open question is a thread; answers land in the doc as decisions and tasks, and you can hand a task straight to an agent. Share it by link and approve each person who asks to join. | No. |
| Encrypted chat | End-to-end encrypted group and one-to-one rooms. Messages are never stored on a server. | No. |
| Sharing | Drag notes, playbooks and tables into an encrypted chat to share them. | No. |
| Workspace | ||
| Notes | Rich-text notes with version history, embedded charts and full-text search, synced through your iCloud. | No. |
| Tables | SQLite-backed tables your agents and playbooks read and write, viewed as a table, kanban or gantt. | No. |
| Charts | Bar, line, area, scatter, pie and KPI charts built from your tables, embeddable in notes. | No. |
| Custom Apps | Small apps built from a JSON spec, kept in your project. | No. |
| Integrations | Jira, GitHub, Slack, Notion, Linear, ServiceNow, Bugsnag, Datadog, or any HTTP source, in your sidebar. | Linear, GitHub, Jira, GitLab and others.[2] |
| Dev tools | ||
| Worktrees | A git worktree per session, with a post-create hook you set per repo or globally. | One worktree and branch per task.[2] |
| Code editor | Monaco, with 60+ languages, a diff view, Vim mode and LSP. | Built-in file editor with tabs, syntax highlighting, find and replace, and language server features such as definitions and diagnostics.[4] |
| Browser | A built-in browser your agents can drive: screenshots, clicks, forms and scraping. | A built-in browser.[2] |
| Dev servers | A live browser preview paired with each server. Cmd+click jumps to the source, and each worktree gets its own port. | Detects a task's running dev server and opens it in the in-app browser; remote dev server ports are forwarded.[5] |
| Spectator mode | Every file an agent edits opens live in the editor, so you can follow along. | The changes panel refreshes automatically as the agent edits, stages or commits files.[6] |
| The basics | ||
| Status | In active development. | Latest release v1.2.10 on 2026-10-30. Emdash 2.0 has an early-access waitlist.[7] |
| Where agents run | On your Mac. Claude Code sessions can also run on a saved SSH host. No hosted agents. | Local-first (SQLite), with remote projects over SSH. It says it doesn't send code or chats to its servers.[2] |
| Platform | macOS. Claude Code sessions can also be driven from the Claude mobile app through Remote Control, opt-in per project. There is no Scape mobile app yet. | macOS, Windows and Linux.[2] |
| Price | 14-day free trial, no account or card. Then Pro at $9.99 a month or $99 a year; you bring your own agent subscriptions. | Free.[1] |
| Open source | No. | Yes, Apache-2.0.[2] |
Agents
- Agents
Scape: Claude Code, Codex, Copilot, Cursor, OpenCode, pi, omp and Kimi Code, on your own subscriptions.
Emdash: More than 25, including Claude Code, Codex, Cursor, OpenCode, Amp, Devin, Qwen Code, Droid and Copilot.[1][2]
- Manager agent (Argus)
Scape: Argus reads your mission, starts child agents in their own worktrees, checks on them, and keeps a log table. You choose which agent and model its children run on, and can restart it on another agent without losing them.
Emdash: No.
- Agent rooms
Scape: Chat rooms where agents and people work one problem together, such as Claude and Codex debating an approach.
Emdash: No.
- Messages between sessions
Scape: One agent can message or direct another session.
Emdash: No.
- Agent review
Scape: Adversarial review: a second agent reviews the first one's diff (/scape-codex-review ships with Scape).
Emdash: No.
- Watchdogs
Scape: Supervisors that spot stuck sessions and auto-answer questions and permission gates (Claude Code).
Emdash: An auto-approve option skips permission prompts for file operations on supported agents.[3]
Automation
- Playbooks
Scape: Step-by-step automations that chain shell commands, agent prompts, HTTP calls and Scape tools. Lock one and it runs as a fixed script.
Emdash: No.
- Scheduler
Scape: A per-project calendar that runs playbooks and messages Argus, once or daily, weekly or monthly, while Scape is open.
Emdash: Scheduled repeat work.[1]
- Triggers
Scape: Run a playbook or prompt Argus when a webhook arrives, an integration record changes, a table query matches, or a calendar event happens. You arm each one.
Emdash: No.
Working with people
- Flight Plans
Scape: One shared, end-to-end encrypted plan for any number of people and their agents. Every open question is a thread; answers land in the doc as decisions and tasks, and you can hand a task straight to an agent. Share it by link and approve each person who asks to join.
Emdash: No.
- Encrypted chat
Scape: End-to-end encrypted group and one-to-one rooms. Messages are never stored on a server.
Emdash: No.
- Sharing
Scape: Drag notes, playbooks and tables into an encrypted chat to share them.
Emdash: No.
Workspace
- Notes
Scape: Rich-text notes with version history, embedded charts and full-text search, synced through your iCloud.
Emdash: No.
- Tables
Scape: SQLite-backed tables your agents and playbooks read and write, viewed as a table, kanban or gantt.
Emdash: No.
- Charts
Scape: Bar, line, area, scatter, pie and KPI charts built from your tables, embeddable in notes.
Emdash: No.
- Custom Apps
Scape: Small apps built from a JSON spec, kept in your project.
Emdash: No.
- Integrations
Scape: Jira, GitHub, Slack, Notion, Linear, ServiceNow, Bugsnag, Datadog, or any HTTP source, in your sidebar.
Emdash: Linear, GitHub, Jira, GitLab and others.[2]
Dev tools
- Worktrees
Scape: A git worktree per session, with a post-create hook you set per repo or globally.
Emdash: One worktree and branch per task.[2]
- Code editor
Scape: Monaco, with 60+ languages, a diff view, Vim mode and LSP.
Emdash: Built-in file editor with tabs, syntax highlighting, find and replace, and language server features such as definitions and diagnostics.[4]
- Browser
Scape: A built-in browser your agents can drive: screenshots, clicks, forms and scraping.
Emdash: A built-in browser.[2]
- Dev servers
Scape: A live browser preview paired with each server. Cmd+click jumps to the source, and each worktree gets its own port.
Emdash: Detects a task's running dev server and opens it in the in-app browser; remote dev server ports are forwarded.[5]
- Spectator mode
Scape: Every file an agent edits opens live in the editor, so you can follow along.
Emdash: The changes panel refreshes automatically as the agent edits, stages or commits files.[6]
The basics
- Status
Scape: In active development.
Emdash: Latest release v1.2.10 on 2026-10-30. Emdash 2.0 has an early-access waitlist.[7]
- Where agents run
Scape: On your Mac. Claude Code sessions can also run on a saved SSH host. No hosted agents.
Emdash: Local-first (SQLite), with remote projects over SSH. It says it doesn't send code or chats to its servers.[2]
- Platform
Scape: macOS. Claude Code sessions can also be driven from the Claude mobile app through Remote Control, opt-in per project. There is no Scape mobile app yet.
Emdash: macOS, Windows and Linux.[2]
- Price
Scape: 14-day free trial, no account or card. Then Pro at $9.99 a month or $99 a year; you bring your own agent subscriptions.
Emdash: Free.[1]
- Open source
Scape: No.
Emdash: Yes, Apache-2.0.[2]
“No” means it isn’t in Emdash’s app or docs: we checked their own site, docs, changelog and repo on , and only count a feature that’s built in and does the same job. If that’s changed, tell us and we’ll update the page.
Why people pick Scape
- Hand an Argus the whole job. Give it the goal and your guardrails. It starts your agents with the routine permissions already granted, checks on them, and only brings you the decisions that are yours to make.
- Solve the problem in front of you. Ask your agents for a Custom App, a playbook or a table that does the job: a morning incident triage, a launch tracker that refreshes itself on a schedule, a report that lands in your notes. Code is only part of the work.
- Let your agents talk to each other. Put Claude and Codex in one room to argue out a fix while you read along, or have one session hand work to another. Any agent, any model, on the subscriptions you already pay for.
- Work with your team, privately. Bring your whole team and everyone's agents into a Flight Plan. Each open question is a thread, the answers land in the doc as decisions and tasks, and a task can go straight to an agent. Talk in end-to-end encrypted rooms: messages aren't stored on a server, and you can run the relay yourself.
- Own your AI setup. Your apps, playbooks and tables live on your Mac, and your notes sync through your own iCloud. Switch the agent or model underneath them whenever you like, and everything you built keeps working.
Where Emdash is stronger
Sources
Facts about Emdash were checked on and may have changed since. Something wrong? Email contact@scape.work and we’ll fix it.