Emdash
Open-source desktop app for Mac, Windows and Linux. Agents run on your computer or on your own server.
Product websiteemdash.com Compare with others Missing or wrong data?
- Desktop app
- Mac, Windows and Linux
- Browser
- No
- Phone
- No
- Command line
- No
- Agents
- Claude Code, Codex, Cursor Agent, OpenCode, Pi, Grok and Antigravity
- Your subscription
- Works with your own plan
- Agents run
- On your computer and on your own server
- Laptop closed
- Keeps going
- Isolation
- Worktree
- Parallel agents
- Yes
- Scheduled runs
- Yes
- Coordinator agent
- No
- Built-in issues
- No
- Pull requests
- Yes
- Review screen
- Yes
- Team
- No
- Self-hosting
- Yes
- Licence
- Apache-2.0
- Price from
- Free
- How it charges
- Bring your own key
- Paid plans from
- Not listed
Measured by ADEMark
ADEMark ran the same tests on 15 ADEs. Results for Emdash 1.2.10, measured up to 12 November 2026 on a Mac mini M4, 16 GB, macOS 27 · Claude Opus 5.5, effort high. Data CC BY 4.0, shown unchanged.
Speed
- Cold start
- 4.25 s10th of 12median of 6 runs, 3.98 s to 4.31 s · Bare CLI 0.69 s
- New thread, ready to type
- 183 ms1st of 10median of 6 runs, 171 ms to 187 ms · Bare CLI 375 ms
- First word on screen
- 811 ms7th of 11median of 6 runs, 757 ms to 836 ms · Bare CLI 220 ms
- Typing lag, 5 agents streaming
- 83 ms11th of 111 run · Bare CLI 79 ms
- Open a 2,000-message thread
- 160 ms10th of 11median of 5 runs, 159 ms to 160 ms · Bare CLI 203 ms
Weight
- Memory at rest, 5 threads
- 2.28 GB12th of 121 run · Bare CLI 0.99 GB
- Idle CPU
- 2.34%9th of 131 run · Bare CLI 0.37%
- Memory under load
- 3.45 GB10th of 101 run · Bare CLI 1.86 GB
Tokens
- Tokens to answer “hi”
- 77K tokens13th of 13median of 3 runs, 38K tokens to 122.1K tokens · Bare CLI 38.2K tokens
- Tokens for one real question
- 165.3K tokens9th of 131 run · Bare CLI 168.3K tokens
Build
- Team build: hidden tests passed
- Not measured
Place counts only apps with a value; lower is better except passed tests. ADEMark publishes no overall score and treats close medians as ties, so read places as an order, not a verdict. The Bare CLI is Claude Code in a terminal, run as an unranked control. Method and every test on ademark.dev · Imported data · How we use it
Receipts
- Checked
- · oldest answer 2026-11-07
- Findings
- 35 published · 21 cross-checked by a second agent · read them all
- Sources
- 28 public pages on 3 sites: github.com, emdash.com, emdash.sh
- Screenshot
- emdash.com, retrieved · first party docs · shows appearance, not capability
- Data
- /products/emdash.json · .md
- Method
- Same rules for all 103 researched ADEs. How we check · Report wrong data
What it does
Where you use it
Emdash Classic supplies desktop clients and SSH remote workspaces. The scoped open-source application has no released browser or native phone client; the in-app browser is a preview pane.
Source and scope for Where you use itAgents it runs
Classic has a fixed list of 35 coding-agent CLI adapters, including Claude Code, Codex, OpenCode, Cursor, Pi, Grok and Antigravity. The complete provider table and pinned registry omit Gemini CLI and Aider.
Source and scope for Agents it runsAccounts and subscriptions
Emdash runs the provider CLIs the user installs and signs in to. For Claude Code it accepts either an ANTHROPIC_API_KEY or the CLI's own signed-in account, including an OAuth subscription login. Per-provider plan terms were not checked.
Source and scope for Accounts and subscriptionsWhere agents run
Classic executes locally or on the user SSH machine. The scoped source supplies no vendor-managed execution backend; Emdash 2.0 early access is outside this release.
Source and scope for Where agents runHow work is kept apart
Classic creates task worktrees or uses an existing checkout. It does not implement container or VM workspace provisioning.
Source and scope for How work is kept apartParallel work
Classic documents parallel coding agents in separate worktrees.
Source and scope for Parallel workScheduled runs
Scheduled prompts run on project machines and retain reviewable history.
Source and scope for Scheduled runsGit and pull requests
Classic supports staging, commits, pushing and pull request creation inside its diff interface.
Source and scope for Git and pull requestsPrice
Classic is free Apache-2.0 desktop software using user-installed agent accounts, subscriptions and provider keys; Claude Code can authenticate with ANTHROPIC_API_KEY. Hosted Emdash 2.0 remains early access with no public complete pricing table.
Source and scope for PriceTyped filters
Every value links to its receipt below. Read plan and surface restrictions before using a filter to decide.
| Filter | Value |
|---|---|
| Desktop OS: macOS | Yes |
| Desktop OS: Windows | Yes |
| Desktop OS: Linux | Yes |
| Web client | No |
| Phone access: Native iOS | No |
| Phone access: Native Android | No |
| Phone access: Phone browser | No |
| CLI | No |
| Coding agents: Claude Code | Yes |
| Coding agents: Codex | Yes |
| Coding agents: Cursor Agent | Yes |
| Coding agents: Gemini CLI | No |
| Coding agents: OpenCode | Yes |
| Coding agents: Pi | Yes |
| Coding agents: Grok | Yes |
| Coding agents: Aider | No |
| Coding agents: Antigravity | Yes |
| Use my subscription | Yes cross-checked |
| Where agents run: On your computer | Yes |
| Where agents run: On your own server | Yes |
| Where agents run: In the vendor's cloud | No |
| Workspace isolation: Git worktree | Yes |
| Workspace isolation: Container | No |
| Workspace isolation: VM or microVM | No |
| Parallel runs | Yes cross-checked |
| Coordinator | No |
| Native issue tracking | No |
| Unattended triggers | Yes cross-checked |
| Shared prompting | No |
| Team roles | No |
| SSO | No |
| Pull request workflow | Yes cross-checked |
| Review interface | Yes cross-checked |
| Product license: Apache-2.0 | Yes. Apache-2.0 cross-checked |
| Product license: MIT | No. Apache-2.0 cross-checked |
| Product license: GPL-3.0 | No. Apache-2.0 cross-checked |
| Product license: GPL-3.0-or-later | No. Apache-2.0 cross-checked |
| Product license: AGPL-3.0 | No. Apache-2.0 cross-checked |
| Product license: AGPL-3.0-or-later | No. Apache-2.0 cross-checked |
| Product license: Elastic License 2.0 | No. Apache-2.0 cross-checked |
| Product license: Custom terms | No. Apache-2.0 cross-checked |
| Product license: Proprietary | No. Apache-2.0 cross-checked |
| Self-hosting | Yes cross-checked |
| Telemetry opt-out | Yes cross-checked |
| Free access | Yes cross-checked |
| Starting price: Free | Yes. Free cross-checked |
| Starting price: Up to $20/month | No. Free cross-checked |
| Starting price: $21–40/month | No. Free cross-checked |
| Starting price: $41–100/month | No. Free cross-checked |
| Starting price: Over $100/month | No. Free cross-checked |
| Starting price: Contact for pricing | No. Free cross-checked |
| Pricing model: Free, no paid plan | Unknown |
| Pricing model: Free plan | Unknown |
| Pricing model: Subscription | Unknown |
| Pricing model: Per seat | Unknown |
| Pricing model: Usage-based | Unknown |
| Pricing model: Per machine or compute | Unknown |
| Pricing model: Bring your own key | Yes |
| Pricing model: One-time purchase | Unknown |
| Paid plans from: No paid plan | Unknown |
| Paid plans from: $10 or less/month | Unknown |
| Paid plans from: $11–20/month | Unknown |
| Paid plans from: $21–40/month | Unknown |
| Paid plans from: $41–100/month | Unknown |
| Paid plans from: Over $100/month | Unknown |
| Paid plans from: Contact sales | Unknown |
| Lifecycle status: Active | Unknown |
| Lifecycle status: Sunsetting | Unknown |
| Keeps going with laptop closed | Yes cross-checked |
| Open-source license | Yes. Apache-2.0 cross-checked |
| Any desktop app | Yes |
| Paid plan up to $20/month | Unknown |
| Paid plan up to $40/month | Unknown |
| Any phone client | No |
Filter receipts
Desktop OS: macOS: Yes
Desktop OS: macOS
Typed value: Yes.
Emdash Classic supplies desktop clients and SSH remote workspaces. The scoped open-source application has no released browser or native phone client; the in-app browser is a preview pane.
- Desktop os: macOS, Windows and Linux packages.
- Notifications: Lifecycle-hook notifications vary by agent.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: Names 35 detected CLI integrations, with provider-specific hooks, resume and model/effort options; remote CLIs must be installed and authenticated remotely.
Desktop OS: Windows: Yes
Desktop OS: Windows
Typed value: Yes.
Emdash Classic supplies desktop clients and SSH remote workspaces. The scoped open-source application has no released browser or native phone client; the in-app browser is a preview pane.
- Desktop os: macOS, Windows and Linux packages.
- Notifications: Lifecycle-hook notifications vary by agent.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: Names 35 detected CLI integrations, with provider-specific hooks, resume and model/effort options; remote CLIs must be installed and authenticated remotely.
Desktop OS: Linux: Yes
Desktop OS: Linux
Typed value: Yes.
Emdash Classic supplies desktop clients and SSH remote workspaces. The scoped open-source application has no released browser or native phone client; the in-app browser is a preview pane.
- Desktop os: macOS, Windows and Linux packages.
- Notifications: Lifecycle-hook notifications vary by agent.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: Names 35 detected CLI integrations, with provider-specific hooks, resume and model/effort options; remote CLIs must be installed and authenticated remotely.
Web client: No
Web client
Typed value: No.
Emdash Classic supplies desktop clients and SSH remote workspaces. The scoped open-source application has no released browser or native phone client; the in-app browser is a preview pane.
- Mobile apps: No iOS or Android client in the scoped desktop source.
- Browser: No released ADE browser client in the desktop application.
- Mobile browser: No phone-browser ADE work client in the scoped release.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
Phone access: Native iOS: No
Phone access: Native iOS
Typed value: No.
Emdash Classic supplies desktop clients and SSH remote workspaces. The scoped open-source application has no released browser or native phone client; the in-app browser is a preview pane.
- Mobile apps: No iOS or Android client in the scoped desktop source.
- Browser: No released ADE browser client in the desktop application.
- Mobile browser: No phone-browser ADE work client in the scoped release.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
Phone access: Native Android: No
Phone access: Native Android
Typed value: No.
Emdash Classic supplies desktop clients and SSH remote workspaces. The scoped open-source application has no released browser or native phone client; the in-app browser is a preview pane.
- Mobile apps: No iOS or Android client in the scoped desktop source.
- Browser: No released ADE browser client in the desktop application.
- Mobile browser: No phone-browser ADE work client in the scoped release.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
Phone access: Phone browser: No
Phone access: Phone browser
Typed value: No.
Emdash Classic supplies desktop clients and SSH remote workspaces. The scoped open-source application has no released browser or native phone client; the in-app browser is a preview pane.
- Mobile apps: No iOS or Android client in the scoped desktop source.
- Browser: No released ADE browser client in the desktop application.
- Mobile browser: No phone-browser ADE work client in the scoped release.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
CLI: No
CLI
Typed value: No.
The scoped Classic application has no standalone product-owned user CLI. Provider CLIs and the SSH Workspace Server are dependencies of its desktop workflow.
- Cli: No installed command interface for users to control the ADE; provider CLIs and internal workspace processes are separate.
- Source review and pinned implementation inspection only; no installed-product, account or multi-user scenario was executed. Unanswered atomic questions remain open.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
Coding agents: Claude Code: Yes
Coding agents: Claude Code
Typed value: Yes.
Classic has a fixed list of 35 coding-agent CLI adapters, including Claude Code, Codex, OpenCode, Cursor, Pi, Grok and Antigravity. The complete provider table and pinned registry omit Gemini CLI and Aider.
- Model providers: Model and effort controls are shown where the selected CLI supports them.
- Session integration: CLI launches with provider-specific hooks and resume support.
- CLI model, effort, hooks and resume behavior vary by provider; no live coding session was run.
-
Finding: Names 35 detected CLI integrations, with provider-specific hooks, resume and model/effort options; remote CLIs must be installed and authenticated remotely.
Coding agents: Codex: Yes
Coding agents: Codex
Typed value: Yes.
Classic has a fixed list of 35 coding-agent CLI adapters, including Claude Code, Codex, OpenCode, Cursor, Pi, Grok and Antigravity. The complete provider table and pinned registry omit Gemini CLI and Aider.
- Model providers: Model and effort controls are shown where the selected CLI supports them.
- Session integration: CLI launches with provider-specific hooks and resume support.
- CLI model, effort, hooks and resume behavior vary by provider; no live coding session was run.
-
Finding: Names 35 detected CLI integrations, with provider-specific hooks, resume and model/effort options; remote CLIs must be installed and authenticated remotely.
Coding agents: Cursor Agent: Yes
Coding agents: Cursor Agent
Typed value: Yes.
Classic has a fixed list of 35 coding-agent CLI adapters, including Claude Code, Codex, OpenCode, Cursor, Pi, Grok and Antigravity. The complete provider table and pinned registry omit Gemini CLI and Aider.
- Model providers: Model and effort controls are shown where the selected CLI supports them.
- Session integration: CLI launches with provider-specific hooks and resume support.
- CLI model, effort, hooks and resume behavior vary by provider; no live coding session was run.
-
Finding: Names 35 detected CLI integrations, with provider-specific hooks, resume and model/effort options; remote CLIs must be installed and authenticated remotely.
Coding agents: Gemini CLI: No
Coding agents: Gemini CLI
Typed value: No.
Classic has a fixed list of 35 coding-agent CLI adapters, including Claude Code, Codex, OpenCode, Cursor, Pi, Grok and Antigravity. The complete provider table and pinned registry omit Gemini CLI and Aider.
- Harnesses: The complete supported-provider list includes the existing mapped harnesses and omits Gemini CLI and Aider.
- CLI model, effort, hooks and resume behavior vary by provider; no live coding session was run.
-
Emdash Classic complete supported providers
Finding: The complete Classic supported-provider list contains 35 coding-agent CLIs, including Antigravity, Pi and Grok, and omits Gemini CLI and Aider. The pinned registry registers the same fixed provider implementations; this is distinct from a list of example model names.
Coding agents: OpenCode: Yes
Coding agents: OpenCode
Typed value: Yes.
Classic has a fixed list of 35 coding-agent CLI adapters, including Claude Code, Codex, OpenCode, Cursor, Pi, Grok and Antigravity. The complete provider table and pinned registry omit Gemini CLI and Aider.
- Model providers: Model and effort controls are shown where the selected CLI supports them.
- Session integration: CLI launches with provider-specific hooks and resume support.
- CLI model, effort, hooks and resume behavior vary by provider; no live coding session was run.
-
Finding: Names 35 detected CLI integrations, with provider-specific hooks, resume and model/effort options; remote CLIs must be installed and authenticated remotely.
Coding agents: Pi: Yes
Coding agents: Pi
Typed value: Yes.
Classic has a fixed list of 35 coding-agent CLI adapters, including Claude Code, Codex, OpenCode, Cursor, Pi, Grok and Antigravity. The complete provider table and pinned registry omit Gemini CLI and Aider.
- CLI model, effort, hooks and resume behavior vary by provider; no live coding session was run.
-
Emdash Supported providers; Feature support; Remote agents
Finding: Classic names Pi and Grok among its 35 CLI providers. Auto-approve skips file-operation permission prompts for the providers that support it; resume/hooks vary by provider. Credentials and installation must exist on the execution machine; per-agent/machine model and effort preferences are remembered.
Coding agents: Grok: Yes
Coding agents: Grok
Typed value: Yes.
Classic has a fixed list of 35 coding-agent CLI adapters, including Claude Code, Codex, OpenCode, Cursor, Pi, Grok and Antigravity. The complete provider table and pinned registry omit Gemini CLI and Aider.
- CLI model, effort, hooks and resume behavior vary by provider; no live coding session was run.
-
Emdash Supported providers; Feature support; Remote agents
Finding: Classic names Pi and Grok among its 35 CLI providers. Auto-approve skips file-operation permission prompts for the providers that support it; resume/hooks vary by provider. Credentials and installation must exist on the execution machine; per-agent/machine model and effort preferences are remembered.
Coding agents: Aider: No
Coding agents: Aider
Typed value: No.
Classic has a fixed list of 35 coding-agent CLI adapters, including Claude Code, Codex, OpenCode, Cursor, Pi, Grok and Antigravity. The complete provider table and pinned registry omit Gemini CLI and Aider.
- Harnesses: The complete supported-provider list includes the existing mapped harnesses and omits Gemini CLI and Aider.
- CLI model, effort, hooks and resume behavior vary by provider; no live coding session was run.
-
Emdash Classic complete supported providers
Finding: The complete Classic supported-provider list contains 35 coding-agent CLIs, including Antigravity, Pi and Grok, and omits Gemini CLI and Aider. The pinned registry registers the same fixed provider implementations; this is distinct from a list of example model names.
Coding agents: Antigravity: Yes
Coding agents: Antigravity
Typed value: Yes.
Classic has a fixed list of 35 coding-agent CLI adapters, including Claude Code, Codex, OpenCode, Cursor, Pi, Grok and Antigravity. The complete provider table and pinned registry omit Gemini CLI and Aider.
- CLI model, effort, hooks and resume behavior vary by provider; no live coding session was run.
-
Emdash Antigravity support at v1.2.11
Finding: Emdash Classic v1.2.11 detects agy or antigravity and builds runnable Antigravity commands with initial prompts, models, permission flags and conversation resume.
Use my subscription: Yes cross-checked
Use my subscription
Typed value: Yes.
Emdash runs the provider CLIs the user installs and signs in to. For Claude Code it accepts either an ANTHROPIC_API_KEY or the CLI's own signed-in account, including an OAuth subscription login. Per-provider plan terms were not checked.
- Agent subscriptions: Emdash runs the installed provider CLI with its own sign-in; for Claude Code it detects a signed-in OAuth account through the CLI's auth status, so a subscription login applies. Not tested; plan terms not checked.
- Api accounts: For Claude Code an ANTHROPIC_API_KEY in the environment counts as authenticated. Source inspection at v1.2.11.
- Vendor account requirement: Provider CLIs may need their own account authentication before Emdash can run them; Emdash itself holds no model credentials.
- Source inspection and docs only; no installed-product test. Subscription reuse was inspected for Claude Code only; other providers rely on their own CLI sign-in as documented.
-
Emdash Claude Code auth status check
Finding: Emdash treats Claude Code as authenticated when ANTHROPIC_API_KEY is set or when the installed claude CLI reports a signed-in account through its own auth status, including an OAuth account; Emdash holds no model credentials of its own.
-
Finding: Emdash detects installed provider CLIs on PATH; some CLIs need their own account authentication before Emdash can run them, and on remote machines the user installs and authenticates the CLI there.
Where agents run: On your computer: Yes
Where agents run: On your computer
Typed value: Yes.
Classic executes locally or on the user SSH machine. The scoped source supplies no vendor-managed execution backend; Emdash 2.0 early access is outside this release.
- Local: Local desktop execution.
- Byo remote: Workspace Server on a machine reached by SSH.
- Payer: User supplies the remote machine.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: The remote Workspace Server handles repos, agents, terminals and scheduling over SSH; local credentials are not automatically copied.
Where agents run: On your own server: Yes
Where agents run: On your own server
Typed value: Yes.
Classic executes locally or on the user SSH machine. The scoped source supplies no vendor-managed execution backend; Emdash 2.0 early access is outside this release.
- Local: Local desktop execution.
- Byo remote: Workspace Server on a machine reached by SSH.
- Payer: User supplies the remote machine.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: The remote Workspace Server handles repos, agents, terminals and scheduling over SSH; local credentials are not automatically copied.
Where agents run: In the vendor's cloud: No
Where agents run: In the vendor's cloud
Typed value: No.
Classic executes locally or on the user SSH machine. The scoped source supplies no vendor-managed execution backend; Emdash 2.0 early access is outside this release.
- Managed cloud: No managed vendor execution service in Classic source; only local and SSH machine workspaces.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
Workspace isolation: Git worktree: Yes
Workspace isolation: Git worktree
Typed value: Yes.
Classic creates task worktrees or uses an existing checkout. It does not implement container or VM workspace provisioning.
- Checkout: Existing workspace or root checkout can be selected; isolation can be disabled with a warning.
- Branch: Separate branch by default.
- Worktree: Separate Git worktree by default.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Tasks select branches, issues or PRs, choose an agent and create a worktree by default. Existing workspaces and root checkout are also available.
Workspace isolation: Container: No
Workspace isolation: Container
Typed value: No.
Classic creates task worktrees or uses an existing checkout. It does not implement container or VM workspace provisioning.
- Container: No container isolation backend in the scoped workspace provisioning runtimes.
- Vm: No VM isolation backend in the scoped workspace provisioning runtimes.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
Workspace isolation: VM or microVM: No
Workspace isolation: VM or microVM
Typed value: No.
Classic creates task worktrees or uses an existing checkout. It does not implement container or VM workspace provisioning.
- Container: No container isolation backend in the scoped workspace provisioning runtimes.
- Vm: No VM isolation backend in the scoped workspace provisioning runtimes.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
Parallel runs: Yes cross-checked
Parallel runs
Typed value: Yes.
Classic documents parallel coding agents in separate worktrees.
- Concurrent sessions: Multiple coding agents can run at once.
- Concurrent tasks: Separate task worktrees.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
Coordinator: No
Coordinator
Typed value: No.
Classic launches user-selected agent sessions and renders provider-native subagents. The scoped implementation does not supply a coordinator-agent role and cross-session delegation tools.
- Orchestration owner: No product coordinator-agent role in the scoped manifests and APIs; underlying provider subagents remain separate.
- Source review and pinned implementation inspection only; no installed-product, account or multi-user scenario was executed. Unanswered atomic questions remain open.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
Native issue tracking: No
Native issue tracking
Typed value: No.
Classic persists workspaces and conversations linked to external tracker issues. It has no separate native issue/backlog entity with its own state; creating a task launches an agent workspace.
- Create: Creation starts a workspace and agent rather than saving an independent issue.
- Task session separation: Workspace/conversation entities and linked external issues do not form a native issue store.
- Durable states: No product-owned native issue state machine in the app database/runtime API.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
Unattended triggers: Yes cross-checked
Unattended triggers
Typed value: Yes.
Scheduled prompts run on project machines and retain reviewable history.
- Schedules: Cron schedules.
- Recurring tasks: Recurring agent prompts.
- Scheduler location: Project machine; Workspace Server for remote projects.
- Client independence: Remote schedules do not need desktop connectivity unless desktop-backed services are required.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Cron prompts run on the project machine. The remote Workspace Server schedules without a connected desktop, except steps needing desktop services. Runs link to tasks and expose errors.
Shared prompting: No
Shared prompting
Typed value: No.
Classic is a local desktop/SSH application with no multi-user shared prompting service in its scoped source. Hosted team early access is a separate component.
- Coprompting: No distinct human membership/input-channel model for one shared agent in Classic.
- Source review and pinned implementation inspection only; no installed-product, account or multi-user scenario was executed. Unanswered atomic questions remain open.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
Team roles: No
Team roles
Typed value: No.
Classic has no application organization roles or enterprise SSO. SSH authentication applies to the remote machine, not product team membership.
- Organization roles: No human organization-role model in Classic.
- Sso: No enterprise SSO implementation in Classic.
- Source review and pinned implementation inspection only; no installed-product, account or multi-user scenario was executed. Unanswered atomic questions remain open.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
SSO: No
SSO
Typed value: No.
Classic has no application organization roles or enterprise SSO. SSH authentication applies to the remote machine, not product team membership.
- Organization roles: No human organization-role model in Classic.
- Sso: No enterprise SSO implementation in Classic.
- Source review and pinned implementation inspection only; no installed-product, account or multi-user scenario was executed. Unanswered atomic questions remain open.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
Pull request workflow: Yes cross-checked
Pull request workflow
Typed value: Yes.
Classic supports staging, commits, pushing and pull request creation inside its diff interface.
- Worktrees: Separate task worktrees.
- Pull requests: Create pull requests.
- Ci response: Inspect check status; automated response was not established.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
Review interface: Yes cross-checked
Review interface
Typed value: Yes.
Task diffs and browser previews are documented.
- Diffs: In-app change viewer.
- Previews: Task browser with local and forwarded remote URLs.
- Persistence: Browser tabs and last URL restore; general artifact retention remains unverified.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Documents file staging, diffs and Git workflow actions.
-
Finding: Task browser previews can forward remote ports and restore saved tabs/profiles. It does not reuse system-browser profiles or extensions.
Product license: Apache-2.0: Yes. Apache-2.0 cross-checked
Product license: Apache-2.0
Typed value: Yes. Apache-2.0.
Classic repository is Apache-2.0.
- Client license: Apache-2.0, subject to component notices.
- Source visibility: Public source.
- Source revision: 9346e9130902a0eac126c1cc37aa10b125eea99b
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Product license: MIT: No. Apache-2.0 cross-checked
Product license: MIT
Typed value: No. Apache-2.0.
Classic repository is Apache-2.0.
- Client license: Apache-2.0, subject to component notices.
- Source visibility: Public source.
- Source revision: 9346e9130902a0eac126c1cc37aa10b125eea99b
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Product license: GPL-3.0: No. Apache-2.0 cross-checked
Product license: GPL-3.0
Typed value: No. Apache-2.0.
Classic repository is Apache-2.0.
- Client license: Apache-2.0, subject to component notices.
- Source visibility: Public source.
- Source revision: 9346e9130902a0eac126c1cc37aa10b125eea99b
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Product license: GPL-3.0-or-later: No. Apache-2.0 cross-checked
Product license: GPL-3.0-or-later
Typed value: No. Apache-2.0.
Classic repository is Apache-2.0.
- Client license: Apache-2.0, subject to component notices.
- Source visibility: Public source.
- Source revision: 9346e9130902a0eac126c1cc37aa10b125eea99b
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Product license: AGPL-3.0: No. Apache-2.0 cross-checked
Product license: AGPL-3.0
Typed value: No. Apache-2.0.
Classic repository is Apache-2.0.
- Client license: Apache-2.0, subject to component notices.
- Source visibility: Public source.
- Source revision: 9346e9130902a0eac126c1cc37aa10b125eea99b
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Product license: AGPL-3.0-or-later: No. Apache-2.0 cross-checked
Product license: AGPL-3.0-or-later
Typed value: No. Apache-2.0.
Classic repository is Apache-2.0.
- Client license: Apache-2.0, subject to component notices.
- Source visibility: Public source.
- Source revision: 9346e9130902a0eac126c1cc37aa10b125eea99b
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Product license: Elastic License 2.0: No. Apache-2.0 cross-checked
Product license: Elastic License 2.0
Typed value: No. Apache-2.0.
Classic repository is Apache-2.0.
- Client license: Apache-2.0, subject to component notices.
- Source visibility: Public source.
- Source revision: 9346e9130902a0eac126c1cc37aa10b125eea99b
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Product license: Custom terms: No. Apache-2.0 cross-checked
Product license: Custom terms
Typed value: No. Apache-2.0.
Classic repository is Apache-2.0.
- Client license: Apache-2.0, subject to component notices.
- Source visibility: Public source.
- Source revision: 9346e9130902a0eac126c1cc37aa10b125eea99b
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Product license: Proprietary: No. Apache-2.0 cross-checked
Product license: Proprietary
Typed value: No. Apache-2.0.
Classic repository is Apache-2.0.
- Client license: Apache-2.0, subject to component notices.
- Source visibility: Public source.
- Source revision: 9346e9130902a0eac126c1cc37aa10b125eea99b
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Self-hosting: Yes cross-checked
Self-hosting
Typed value: Yes.
Classic operates on local or user-operated machines.
- Self hosting: User-owned local/SSH execution.
- Vendor dependencies: Agent providers are separate dependencies. Full account-independent use was not tested.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: The remote Workspace Server handles repos, agents, terminals and scheduling over SSH; local credentials are not automatically copied.
Telemetry opt-out: Yes cross-checked
Telemetry opt-out
Typed value: Yes.
Classic documents allowlisted default-on PostHog telemetry and opt-out; agent provider policy remains separate.
- Code data: Normal events exclude code, prompts and file contents; diagnostic errors may include exception text.
- Prompts: Normal usage telemetry excludes prompts, messages and command text; diagnostics may include exception text.
- Logs: Error events may include exception messages and stack traces for diagnostics.
- Subprocessors: PostHog is named for analytics; a complete subprocessor list is not established.
- Telemetry disclosure: PostHog and allowlisted usage/error events.
- Telemetry defaults: Enabled in production by default.
- Telemetry controls: Settings toggle or TELEMETRY_ENABLED=false.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Production telemetry defaults on, uses allowlisted PostHog events, can attach account identity after sign-in, and has settings/environment opt-out.
Free access: Yes cross-checked
Free access
Typed value: Yes.
Classic is advertised as free; agent and machine costs remain separate.
- Ongoing free: Free desktop application.
- Self host cost: User supplies agents and remote machines. Their costs are not zeroed.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: The Emdash Classic page answers that Emdash is open source and free to use. This covers the application, not agent subscriptions or remote machine costs.
Starting price: Free: Yes. Free cross-checked
Starting price: Free
Typed value: Yes. Free.
Classic is advertised as free; agent and machine costs remain separate.
- Ongoing free: Free desktop application.
- Self host cost: User supplies agents and remote machines. Their costs are not zeroed.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: The Emdash Classic page answers that Emdash is open source and free to use. This covers the application, not agent subscriptions or remote machine costs.
Starting price: Up to $20/month: No. Free cross-checked
Starting price: Up to $20/month
Typed value: No. Free.
Classic is advertised as free; agent and machine costs remain separate.
- Ongoing free: Free desktop application.
- Self host cost: User supplies agents and remote machines. Their costs are not zeroed.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: The Emdash Classic page answers that Emdash is open source and free to use. This covers the application, not agent subscriptions or remote machine costs.
Starting price: $21–40/month: No. Free cross-checked
Starting price: $21–40/month
Typed value: No. Free.
Classic is advertised as free; agent and machine costs remain separate.
- Ongoing free: Free desktop application.
- Self host cost: User supplies agents and remote machines. Their costs are not zeroed.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: The Emdash Classic page answers that Emdash is open source and free to use. This covers the application, not agent subscriptions or remote machine costs.
Starting price: $41–100/month: No. Free cross-checked
Starting price: $41–100/month
Typed value: No. Free.
Classic is advertised as free; agent and machine costs remain separate.
- Ongoing free: Free desktop application.
- Self host cost: User supplies agents and remote machines. Their costs are not zeroed.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: The Emdash Classic page answers that Emdash is open source and free to use. This covers the application, not agent subscriptions or remote machine costs.
Starting price: Over $100/month: No. Free cross-checked
Starting price: Over $100/month
Typed value: No. Free.
Classic is advertised as free; agent and machine costs remain separate.
- Ongoing free: Free desktop application.
- Self host cost: User supplies agents and remote machines. Their costs are not zeroed.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: The Emdash Classic page answers that Emdash is open source and free to use. This covers the application, not agent subscriptions or remote machine costs.
Starting price: Contact for pricing: No. Free cross-checked
Starting price: Contact for pricing
Typed value: No. Free.
Classic is advertised as free; agent and machine costs remain separate.
- Ongoing free: Free desktop application.
- Self host cost: User supplies agents and remote machines. Their costs are not zeroed.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: The Emdash Classic page answers that Emdash is open source and free to use. This covers the application, not agent subscriptions or remote machine costs.
Pricing model: Bring your own key: Yes
Pricing model: Bring your own key
Typed value: Yes.
Classic is free Apache-2.0 desktop software using user-installed agent accounts, subscriptions and provider keys; Claude Code can authenticate with ANTHROPIC_API_KEY. Hosted Emdash 2.0 remains early access with no public complete pricing table.
- Model cost: User-provided agent credentials include native subscriptions and an ANTHROPIC_API_KEY route; API usage is billed by the provider.
- Classic provider-key authentication does not establish current hosted Emdash 2.0 commercial plans.
-
Emdash Claude provider-key authentication
Finding: Classic detects authenticated Claude Code from the user ANTHROPIC_API_KEY environment variable before querying native CLI authentication. Model API billing remains with the user provider account; the ADE does not resell the key usage.
Keeps going with laptop closed: Yes cross-checked
Keeps going with laptop closed
Typed value: Yes.
Optional tmux preserves terminal processes/history across view closure or SSH loss, with host reboot excluded.
- Client disconnect: Closing Emdash or losing SSH does not stop a tmux-managed process. Local Windows sessions do not use tmux; SSH sessions can use tmux on the remote host.
- Service restart: Host reboot does not preserve tmux processes.
- Transcript reload: tmux keeps terminal history on the execution host; Chat UI history has a separate lifetime.
- Process reconnect: Reattach to the running tmux session.
- Manual repair: tmux ls/attach can inspect and reconnect on the host; tmux must be installed and already enabled for that session.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Tmux persistence needs tmux on the session host and does not apply to local Windows sessions.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Optional tmux retains terminal/TUI processes across app disconnects, but not reboot. Local Windows sessions do not use tmux.
Open-source license: Yes. Apache-2.0 cross-checked
Open-source license
Typed value: Yes. Apache-2.0.
Classic repository is Apache-2.0.
- Client license: Apache-2.0, subject to component notices.
- Source visibility: Public source.
- Source revision: 9346e9130902a0eac126c1cc37aa10b125eea99b
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
Any desktop app: Yes
Any desktop app
Typed value: Yes.
Emdash Classic supplies desktop clients and SSH remote workspaces. The scoped open-source application has no released browser or native phone client; the in-app browser is a preview pane.
- Desktop os: macOS, Windows and Linux packages.
- Notifications: Lifecycle-hook notifications vary by agent.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: Names 35 detected CLI integrations, with provider-specific hooks, resume and model/effort options; remote CLIs must be installed and authenticated remotely.
Any phone client: No
Any phone client
Typed value: No.
Emdash Classic supplies desktop clients and SSH remote workspaces. The scoped open-source application has no released browser or native phone client; the in-app browser is a preview pane.
- Mobile apps: No iOS or Android client in the scoped desktop source.
- Browser: No released ADE browser client in the desktop application.
- Mobile browser: No phone-browser ADE work client in the scoped release.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
All public findings
Findings may summarize a source. They are not presented as verbatim statements.
emdash:ACC-01: Emdash Classic supplies desktop clients and SSH remote workspaces. The scoped open-source application has no released browser or native phone client; the in-app browser is a preview pane.
emdash:ACC-01
Emdash Classic supplies desktop clients and SSH remote workspaces. The scoped open-source application has no released browser or native phone client; the in-app browser is a preview pane.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the cited atomic facts are established. No configured product, account, billing or multi-user scenario was run; remaining atomic answers stay unknown.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: Tasks select branches, issues or PRs, choose an agent and create a worktree by default. Existing workspaces and root checkout are also available.
-
Finding: Names 35 detected CLI integrations, with provider-specific hooks, resume and model/effort options; remote CLIs must be installed and authenticated remotely.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
emdash:ACC-02: Classic has a fixed list of 35 coding-agent CLI adapters, including Claude Code, Codex, OpenCode, Cursor, Pi, Grok and Antigravity. The complete provider table and pinned registry omit Gemini CLI and Aider.
emdash:ACC-02
Classic has a fixed list of 35 coding-agent CLI adapters, including Claude Code, Codex, OpenCode, Cursor, Pi, Grok and Antigravity. The complete provider table and pinned registry omit Gemini CLI and Aider.
- CLI model, effort, hooks and resume behavior vary by provider; no live coding session was run.
-
Finding: Names 35 detected CLI integrations, with provider-specific hooks, resume and model/effort options; remote CLIs must be installed and authenticated remotely.
-
Emdash Supported providers; Feature support; Remote agents
Finding: Classic names Pi and Grok among its 35 CLI providers. Auto-approve skips file-operation permission prompts for the providers that support it; resume/hooks vary by provider. Credentials and installation must exist on the execution machine; per-agent/machine model and effort preferences are remembered.
-
Emdash Antigravity support at v1.2.11
Finding: Emdash Classic v1.2.11 detects agy or antigravity and builds runnable Antigravity commands with initial prompts, models, permission flags and conversation resume.
-
Emdash Classic complete supported providers
Finding: The complete Classic supported-provider list contains 35 coding-agent CLIs, including Antigravity, Pi and Grok, and omits Gemini CLI and Aider. The pinned registry registers the same fixed provider implementations; this is distinct from a list of example model names.
emdash:ACC-03: Emdash runs the provider CLIs the user installs and signs in to. For Claude Code it accepts either an ANTHROPIC_API_KEY or the CLI's own signed-in account, including an OAuth subscription login. Per-provider plan terms were not checked. cross-checked
emdash:ACC-03
Emdash runs the provider CLIs the user installs and signs in to. For Claude Code it accepts either an ANTHROPIC_API_KEY or the CLI's own signed-in account, including an OAuth subscription login. Per-provider plan terms were not checked.
- Source inspection and docs only; no installed-product test. Subscription reuse was inspected for Claude Code only; other providers rely on their own CLI sign-in as documented.
-
Emdash Claude Code auth status check
Finding: Emdash treats Claude Code as authenticated when ANTHROPIC_API_KEY is set or when the installed claude CLI reports a signed-in account through its own auth status, including an OAuth account; Emdash holds no model credentials of its own.
-
Finding: Emdash detects installed provider CLIs on PATH; some CLIs need their own account authentication before Emdash can run them, and on remote machines the user installs and authenticates the CLI there.
emdash:ACC-04: Install an agent CLI locally or on the selected remote machine before starting work. cross-checked
emdash:ACC-04
Install an agent CLI locally or on the selected remote machine before starting work.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Tasks select branches, issues or PRs, choose an agent and create a worktree by default. Existing workspaces and root checkout are also available.
-
Finding: Names 35 detected CLI integrations, with provider-specific hooks, resume and model/effort options; remote CLIs must be installed and authenticated remotely.
emdash:ACC-05: The scoped Classic application has no standalone product-owned user CLI. Provider CLIs and the SSH Workspace Server are dependencies of its desktop workflow.
emdash:ACC-05
The scoped Classic application has no standalone product-owned user CLI. Provider CLIs and the SSH Workspace Server are dependencies of its desktop workflow.
- Source review and pinned implementation inspection only; no installed-product, account or multi-user scenario was executed. Unanswered atomic questions remain open.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
emdash:ACC-06: The Library manages reusable prompts, skills and per-machine MCP configuration. cross-checked
emdash:ACC-06
The Library manages reusable prompts, skills and per-machine MCP configuration.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Reusable prompts, skills and MCP configuration are managed in the Library.
-
Finding: Library saves reusable prompts for new or existing conversations, installs/creates skills and configures MCP servers. Remote configuration is scoped to that machine and is not automatically copied from the laptop.
emdash:ACC-07: Classic desktop uses Electron. cross-checked
emdash:ACC-07
Classic desktop uses Electron.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: The documented desktop client uses Electron.
emdash:PLAN-01: Tasks accept branch, external issue or PR context. cross-checked
emdash:PLAN-01
Tasks accept branch, external issue or PR context.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: Tasks select branches, issues or PRs, choose an agent and create a worktree by default. Existing workspaces and root checkout are also available.
emdash:PLAN-04: Classic stores reusable prompts, skills and MCP configuration with explicit machine scope. cross-checked
emdash:PLAN-04
Classic stores reusable prompts, skills and MCP configuration with explicit machine scope.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Reusable prompts, skills and MCP configuration are managed in the Library.
-
Finding: Library saves reusable prompts for new or existing conversations, installs/creates skills and configures MCP servers. Remote configuration is scoped to that machine and is not automatically copied from the laptop.
emdash:PLAN-06: Classic persists workspaces and conversations linked to external tracker issues. It has no separate native issue/backlog entity with its own state; creating a task launches an agent workspace.
emdash:PLAN-06
Classic persists workspaces and conversations linked to external tracker issues. It has no separate native issue/backlog entity with its own state; creating a task launches an agent workspace.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Tasks select branches, issues or PRs, choose an agent and create a worktree by default. Existing workspaces and root checkout are also available.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
emdash:COORD-01: Classic documents parallel coding agents in separate worktrees. cross-checked
emdash:COORD-01
Classic documents parallel coding agents in separate worktrees.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
emdash:COORD-03: Classic launches user-selected agent sessions and renders provider-native subagents. The scoped implementation does not supply a coordinator-agent role and cross-session delegation tools.
emdash:COORD-03
Classic launches user-selected agent sessions and renders provider-native subagents. The scoped implementation does not supply a coordinator-agent role and cross-session delegation tools.
- Source review and pinned implementation inspection only; no installed-product, account or multi-user scenario was executed. Unanswered atomic questions remain open.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
emdash:COORD-04: Scheduled prompts run on project machines and retain reviewable history. cross-checked
emdash:COORD-04
Scheduled prompts run on project machines and retain reviewable history.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Cron prompts run on the project machine. The remote Workspace Server schedules without a connected desktop, except steps needing desktop services. Runs link to tasks and expose errors.
-
Emdash Create an automation; Review runs
Finding: Scheduled runs select name, project, cron, prompt, agent and workspace. History shows timing, status and errors with associated task/conversation links. Runs can become regular tasks. Pausing stops future schedules.
emdash:COORD-05: Provider hooks expose attention needs and resumable sessions. cross-checked
emdash:COORD-05
Provider hooks expose attention needs and resumable sessions.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Names 35 detected CLI integrations, with provider-specific hooks, resume and model/effort options; remote CLIs must be installed and authenticated remotely.
-
Finding: Cron prompts run on the project machine. The remote Workspace Server schedules without a connected desktop, except steps needing desktop services. Runs link to tasks and expose errors.
emdash:COORD-07: Classic automations let users choose the agent, provider options, prompt and workspace for scheduled runs.
emdash:COORD-07
Classic automations let users choose the agent, provider options, prompt and workspace for scheduled runs.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Emdash Create an automation; Review runs
Finding: Scheduled runs select name, project, cron, prompt, agent and workspace. History shows timing, status and errors with associated task/conversation links. Runs can become regular tasks. Pausing stops future schedules.
emdash:RUN-01: Classic executes locally or on the user SSH machine. The scoped source supplies no vendor-managed execution backend; Emdash 2.0 early access is outside this release.
emdash:RUN-01
Classic executes locally or on the user SSH machine. The scoped source supplies no vendor-managed execution backend; Emdash 2.0 early access is outside this release.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: The remote Workspace Server handles repos, agents, terminals and scheduling over SSH; local credentials are not automatically copied.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
emdash:RUN-02: Classic creates task worktrees or uses an existing checkout. It does not implement container or VM workspace provisioning.
emdash:RUN-02
Classic creates task worktrees or uses an existing checkout. It does not implement container or VM workspace provisioning.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Tasks select branches, issues or PRs, choose an agent and create a worktree by default. Existing workspaces and root checkout are also available.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
emdash:RUN-03: Optional tmux preserves terminal processes/history across view closure or SSH loss, with host reboot excluded. cross-checked
emdash:RUN-03
Optional tmux preserves terminal processes/history across view closure or SSH loss, with host reboot excluded.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Tmux persistence needs tmux on the session host and does not apply to local Windows sessions.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Optional tmux retains terminal/TUI processes across app disconnects, but not reboot. Local Windows sessions do not use tmux.
emdash:RUN-04: Remote previews have explicit port forwarding and manual collision guidance. cross-checked
emdash:RUN-04
Remote previews have explicit port forwarding and manual collision guidance.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Task browser previews can forward remote ports and restore saved tabs/profiles. It does not reuse system-browser profiles or extensions.
emdash:RUN-06: Automation history and PR checks expose timing, status and errors. No operational consistency fixture was run.
emdash:RUN-06
Automation history and PR checks expose timing, status and errors. No operational consistency fixture was run.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Cron prompts run on the project machine. The remote Workspace Server schedules without a connected desktop, except steps needing desktop services. Runs link to tasks and expose errors.
-
Emdash Viewing checks; Refreshing check runs; Requirements
Finding: Checks display pass/fail/pending/skipped, source, timing and links for the PR current head commit; opening Checks or a new head refreshes GitHub data. PR comments appear below checks. Requires a selected GitHub account, PR and configured checks.
emdash:TEAM-01: Classic is a local desktop/SSH application with no multi-user shared prompting service in its scoped source. Hosted team early access is a separate component.
emdash:TEAM-01
Classic is a local desktop/SSH application with no multi-user shared prompting service in its scoped source. Hosted team early access is a separate component.
- Source review and pinned implementation inspection only; no installed-product, account or multi-user scenario was executed. Unanswered atomic questions remain open.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
emdash:TEAM-02: Classic has no application organization roles or enterprise SSO. SSH authentication applies to the remote machine, not product team membership.
emdash:TEAM-02
Classic has no application organization roles or enterprise SSO. SSH authentication applies to the remote machine, not product team membership.
- Source review and pinned implementation inspection only; no installed-product, account or multi-user scenario was executed. Unanswered atomic questions remain open.
-
Emdash: apps/emdash-desktop/src/core/services/app-db/node/schema.ts
Finding: The scoped open-source desktop app persists projects, workspaces, conversations, linked external issues and automations. It supplies local/SSH workspaces with worktrees, not a separate native issue store. The desktop entry and runtime manifests contain no released web/native-phone client, standalone end-user CLI, managed vendor worker, container/VM provisioner, product agent coordinator role or multi-human account/role/SSO prompting service. Agent registry is statically registered. Emdash 2.0 hosted/team early access is a separate component.
emdash:TEAM-03: Classic lists provider-specific auto-approve, which skips file-operation permission prompts, and confirms before discarding changes. Product-enforced permission policy was not established.
emdash:TEAM-03
Classic lists provider-specific auto-approve, which skips file-operation permission prompts, and confirms before discarding changes. Product-enforced permission policy was not established.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Emdash Where to find it; Actions; Inline editing
Finding: Classic updates changed/staged files from workspace Git events and offers unified/split diffs, inline editing of unstaged files, stage/unstage/discard, commit, push and create PR. Discard asks confirmation. PR views show files, commits, checks, comments and merge state; GitHub account/remote required for PR operations.
-
Emdash Supported providers; Feature support; Remote agents
Finding: Classic names Pi and Grok among its 35 CLI providers. Auto-approve skips file-operation permission prompts for the providers that support it; resume/hooks vary by provider. Credentials and installation must exist on the execution machine; per-agent/machine model and effort preferences are remembered.
emdash:TEAM-05: Classic offers diff inspection and PR check/comment context in the task workspace. Usability was not measured. cross-checked
emdash:TEAM-05
Classic offers diff inspection and PR check/comment context in the task workspace. Usability was not measured.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Emdash Where to find it; Actions; Inline editing
Finding: Classic updates changed/staged files from workspace Git events and offers unified/split diffs, inline editing of unstaged files, stage/unstage/discard, commit, push and create PR. Discard asks confirmation. PR views show files, commits, checks, comments and merge state; GitHub account/remote required for PR operations.
emdash:SHIP-01: Task diffs and browser previews are documented. cross-checked
emdash:SHIP-01
Task diffs and browser previews are documented.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Documents file staging, diffs and Git workflow actions.
-
Finding: Task browser previews can forward remote ports and restore saved tabs/profiles. It does not reuse system-browser profiles or extensions.
emdash:SHIP-02: Classic displays GitHub Actions checks. cross-checked
emdash:SHIP-02
Classic displays GitHub Actions checks.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Shows GitHub check status; this does not establish enforced delivery gates.
emdash:SHIP-03: Classic supports staging, commits, pushing and pull request creation inside its diff interface. cross-checked
emdash:SHIP-03
Classic supports staging, commits, pushing and pull request creation inside its diff interface.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Emdash Where to find it; Actions; Inline editing
Finding: Classic updates changed/staged files from workspace Git events and offers unified/split diffs, inline editing of unstaged files, stage/unstage/discard, commit, push and create PR. Discard asks confirmation. PR views show files, commits, checks, comments and merge state; GitHub account/remote required for PR operations.
emdash:SHIP-04: Classic advertises merging reviewed changes in the app. cross-checked
emdash:SHIP-04
Classic advertises merging reviewed changes in the app.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
emdash:SHIP-05: Classic links current-head PR checks to GitHub and can discard unstaged changes with confirmation. General rollback remains unknown.
emdash:SHIP-05
Classic links current-head PR checks to GitHub and can discard unstaged changes with confirmation. General rollback remains unknown.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Emdash Where to find it; Actions; Inline editing
Finding: Classic updates changed/staged files from workspace Git events and offers unified/split diffs, inline editing of unstaged files, stage/unstage/discard, commit, push and create PR. Discard asks confirmation. PR views show files, commits, checks, comments and merge state; GitHub account/remote required for PR operations.
-
Emdash Viewing checks; Refreshing check runs; Requirements
Finding: Checks display pass/fail/pending/skipped, source, timing and links for the PR current head commit; opening Checks or a new head refreshes GitHub data. PR comments appear below checks. Requires a selected GitHub account, PR and configured checks.
emdash:OWN-01: Classic repository is Apache-2.0. cross-checked
emdash:OWN-01
Classic repository is Apache-2.0.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: The cited root license governs this repository distribution, subject to component notices.
emdash:OWN-02: Classic operates on local or user-operated machines. cross-checked
emdash:OWN-02
Classic operates on local or user-operated machines.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: The remote Workspace Server handles repos, agents, terminals and scheduling over SSH; local credentials are not automatically copied.
emdash:OWN-03: Classic documents allowlisted default-on PostHog telemetry and opt-out; agent provider policy remains separate. cross-checked
emdash:OWN-03
Classic documents allowlisted default-on PostHog telemetry and opt-out; agent provider policy remains separate.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: Production telemetry defaults on, uses allowlisted PostHog events, can attach account identity after sign-in, and has settings/environment opt-out.
emdash:OWN-04: Classic is free Apache-2.0 desktop software using user-installed agent accounts, subscriptions and provider keys; Claude Code can authenticate with ANTHROPIC_API_KEY. Hosted Emdash 2.0 remains early access with no public complete pricing table.
emdash:OWN-04
Classic is free Apache-2.0 desktop software using user-installed agent accounts, subscriptions and provider keys; Claude Code can authenticate with ANTHROPIC_API_KEY. Hosted Emdash 2.0 remains early access with no public complete pricing table.
- Classic provider-key authentication does not establish current hosted Emdash 2.0 commercial plans.
-
Finding: Emdash 2.0 is an early-access team product that runs agents on the user's infrastructure or Emdash cloud with the user's own subscriptions and models; no prices are shown.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
-
Emdash Claude provider-key authentication
Finding: Classic detects authenticated Claude Code from the user ANTHROPIC_API_KEY environment variable before querying native CLI authentication. Model API billing remains with the user provider account; the ADE does not resell the key usage.
emdash:OWN-06: These docs cover shipped Classic; Emdash 2.0 is described as early-access/waitlist separately. cross-checked
emdash:OWN-06
These docs cover shipped Classic; Emdash 2.0 is described as early-access/waitlist separately.
- Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
-
Finding: Roadmap points to discussions and issue requests, rather than a dated delivery commitment.
emdash:OWN-08: Classic is advertised as free; agent and machine costs remain separate. cross-checked
emdash:OWN-08
Classic is advertised as free; agent and machine costs remain separate.
- The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
-
Finding: Classic runs installed coding CLIs in parallel Git worktrees on local or SSH machines. README lists desktop installers for macOS/Windows/Linux and Apache-2.0, with PR/check/merge workflow and separate provider data handling.
-
Finding: The Emdash Classic page answers that Emdash is open source and free to use. This covers the application, not agent subscriptions or remote machine costs.