45 of 51 criteria have a sourced finding; 39 were also cross-checked by a second agent. Every comparison that includes Emdash links here for scope, limitations, atomic answers and sources.
Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.
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.
Scope
Surfaces: desktop, remote · Version: a2bdb78f7a619ac87c1c4f86c18570f5fcffae10 · Plan: Not specified · OS: macOS, Windows, Linux · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
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.
Mobile apps [unsupported] No iOS or Android client in the scoped desktop source. Sources: emdash:gap37-classic-boundary.
Browser [unsupported] No released ADE browser client in the desktop application. Sources: emdash:gap37-classic-boundary.
Mobile browser [unsupported] No phone-browser ADE work client in the scoped release. Sources: emdash:gap37-classic-boundary.
Cli [unknown] Cli: The November first-party documentation and repository pass did not establish client access at the rubric's required scope. No installed-product fixture was run.
Editor extensions [unknown] Editor extensions: The November first-party documentation and repository pass did not establish client access at the rubric's required scope. No installed-product fixture was run.
Task actions [supported] Create a task from a branch, issue or PR, choose a provider, and chat with the agent in Chat UI or terminal. Sources: emdash:nov07-tasks.
Notifications [supported] Lifecycle-hook notifications vary by agent. Sources: emdash:nov07-providers.
Cross device continuity [unknown] Cross device continuity: The November first-party documentation and repository pass did not establish client access at the rubric's required scope. No installed-product fixture was run.
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.
Scope
Surfaces: desktop, remote · Version: a2bdb78f7a619ac87c1c4f86c18570f5fcffae10 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
CLI model, effort, hooks and resume behavior vary by provider; no live coding session was run.
5 atomic answers
Harnesses [supported] The complete supported-provider list includes the existing mapped harnesses and omits Gemini CLI and Aider. Sources: emdash:gap37-complete-providers.
Model providers [partial] Model and effort controls are shown where the selected CLI supports them. Sources: emdash:nov07-providers.
Custom adapters [unknown] Custom adapters: The November first-party documentation and repository pass did not establish agent and model choice at the rubric's required scope. No installed-product fixture was run.
Session integration [supported] CLI launches with provider-specific hooks and resume support. Sources: emdash:nov07-providers.
Mixed harness operation [unknown] Mixed harness operation: The November first-party documentation and repository pass did not establish agent and model choice at the rubric's required scope. No installed-product fixture was run.
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.
Scope
Surfaces: desktop, remote · Version: Emdash Classic v1.2.11 (commit 9346e91); Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-10 (12 days old)
Agent cross-check
2026-11-22
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.
7 atomic answers
Agent subscriptions [partial] 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. Sources: emdash:src1-claude-auth, emdash:src1-providers.
Api accounts [supported] For Claude Code an ANTHROPIC_API_KEY in the environment counts as authenticated. Source inspection at v1.2.11. Sources: emdash:src1-claude-auth.
Vendor credits [unsupported] Classic sells no model usage or credits: setup uses the user's own agent CLIs and the pinned source has no billing or credit code. Sources: emdash:b06-installation, emdash:b06-no-billing.
Local models [unknown] Local models: The November first-party documentation and repository pass did not establish subscriptions, api keys and vendor credits at the rubric's required scope. No installed-product fixture was run.
Account switching [partial] Several GitHub accounts can be connected and each project picks one; agent CLI accounts are managed by each CLI on each machine, with no Emdash account switcher. Sources: emdash:b06-github-accounts, emdash:b06-providers.
Vendor account requirement [partial] Provider CLIs may need their own account authentication before Emdash can run them; Emdash itself holds no model credentials. Sources: emdash:src1-providers, emdash:src1-claude-auth.
Provider restrictions [partial] The providers page states that some provider CLIs need their own account authentication or product access before Emdash can run them; Emdash does not list which. Sources: emdash:b06-providers.
Install an agent CLI locally or on the selected remote machine before starting work.
Scope
Surfaces: desktop, remote · Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
7 atomic answers
First task setup [partial] Choose a project, branch/worktree and provider. Setup duration was not measured. Sources: emdash:nov07-providers, emdash:nov07-tasks.
No git [unknown] No git: The November first-party documentation and repository pass did not establish onboarding and project prerequisites at the rubric's required scope. No installed-product fixture was run.
Local git without remote [unknown] Local git without remote: The November first-party documentation and repository pass did not establish onboarding and project prerequisites at the rubric's required scope. No installed-product fixture was run.
Managed cloud setup [unsupported] Classic has no hosted runtime: work runs on the user's computer or on SSH machines the user adds. Emdash 2.0 early access is a separate product. Sources: emdash:b06-remote, emdash:b06-installation.
Byo vps onboarding [supported] Add a machine over SSH in Settings, Machines, install or start the Workspace Runtime from its System tab, then add a remote project. Sources: emdash:b06-ssh, emdash:b06-machines.
The scoped Classic application has no standalone product-owned user CLI. Provider CLIs and the SSH Workspace Server are dependencies of its desktop workflow.
Scope
Surfaces: desktop, remote · Version: a2bdb78f7a619ac87c1c4f86c18570f5fcffae10 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
Not separately cross-checked
Source review and pinned implementation inspection only; no installed-product, account or multi-user scenario was executed. Unanswered atomic questions remain open.
8 atomic answers
Cli [unsupported] No installed command interface for users to control the ADE; provider CLIs and internal workspace processes are separate. Sources: emdash:gap37-classic-boundary.
Api [unknown] Api: The November first-party documentation and repository pass did not establish programmable access at the rubric's required scope. No installed-product fixture was run.
Sdk [unknown] Sdk: The November first-party documentation and repository pass did not establish programmable access at the rubric's required scope. No installed-product fixture was run.
Mcp server [unknown] Mcp server: The November first-party documentation and repository pass did not establish programmable access at the rubric's required scope. No installed-product fixture was run.
Webhooks [unknown] Webhooks: The November first-party documentation and repository pass did not establish programmable access at the rubric's required scope. No installed-product fixture was run.
Operations [unknown] Operations: The November first-party documentation and repository pass did not establish programmable access at the rubric's required scope. No installed-product fixture was run.
Authentication [unknown] Authentication: The November first-party documentation and repository pass did not establish programmable access at the rubric's required scope. No installed-product fixture was run.
Stability [unknown] Stability: The November first-party documentation and repository pass did not establish programmable access at the rubric's required scope. No installed-product fixture was run.
The Library manages reusable prompts, skills and per-machine MCP configuration.
Scope
Surfaces: desktop, remote · Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
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.
7 atomic answers
Mcp client [partial] MCP configuration for agents; a tool call was not tested. Sources: emdash:nov07-library.
Plugins [unknown] Plugins: The November first-party documentation and repository pass did not establish external tools and extensions at the rubric's required scope. No installed-product fixture was run.
Custom tools [supported] MCP Servers configures external tools/data sources and syncs to supported agents; execution belongs to the agent. Sources: emdash:gap-library.
Authentication [partial] MCP server credentials are entered in the add-server modal; trackers use personal API keys or tokens; GitHub connects through an Emdash account (OAuth), GitHub CLI import or device flow. Sources: emdash:b06-mcp, emdash:b06-issues, emdash:b06-github-accounts.
Permission scope [supported] Remote skills/MCP configuration applies to the selected remote machine rather than being copied automatically from the laptop. Sources: emdash:gap-library.
Mobile implementation [unknown] Mobile implementation: The November first-party documentation and repository pass did not establish client implementation at the rubric's required scope. No installed-product fixture was run.
Hybrids [partial] The Electron desktop UI drives a separate Workspace Server daemon on SSH machines that runs files, Git, terminals, agents and automations. Sources: emdash:b06-remote, emdash:b06-ws-license.
Chat git triggers [unknown] Chat git triggers: The November first-party documentation and repository pass did not establish intake and external tracker relationship at the rubric's required scope. No installed-product fixture was run.
Authoritative tracker [supported] The external tracker stays authoritative; Emdash links the issue to the task and inserts it as context. Sources: emdash:b06-issues.
Stable ids [supported] Inserted issue context includes the provider, identifier and URL. Sources: emdash:b06-issues.
Sync [partial] One-way read: providers only list, search and fetch issues; no write-back to trackers exists in the pinned source. Sources: emdash:b06-issue-api, emdash:b06-issues.
Supported edits [unknown] Supported edits: The November first-party documentation and repository pass did not establish intake and external tracker relationship at the rubric's required scope. No installed-product fixture was run.
Classic uses the linked issue context and initial prompt as the task brief, linked to branch, worktree and pull request; it has no separate plan editor.
Scope
Surfaces: desktop, remote · Version: Emdash Classic v1.2.13 (17f32be, 2026-11-19); docs retrieved 2026-11-21 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-22
Documentation and pinned-source inspection only; no installed-product scenario was run.
7 atomic answers
Plans [partial] Issue context and the initial prompt serve as the brief; no plan document or editor exists. Sources: emdash:b06-issues, emdash:b06-tasks.
Acceptance criteria [unknown] Acceptance criteria: The November first-party documentation and repository pass did not establish durable task plans at the rubric's required scope. No installed-product fixture was run.
Editors [partial] Generated issue context can be reviewed and edited in the initial prompt before sending. Sources: emdash:b06-issues.
Revisions [unknown] Revisions: The November first-party documentation and repository pass did not establish durable task plans at the rubric's required scope. No installed-product fixture was run.
Amendment [unknown] Amendment: The November first-party documentation and repository pass did not establish durable task plans at the rubric's required scope. No installed-product fixture was run.
Restart persistence [partial] Saved conversations persist; running processes need tmux or provider resume. Sources: emdash:b06-tasks, emdash:b06-tmux.
Project docs [partial] Saved prompts hold reusable instructions; maintained specifications were not established. Sources: emdash:nov07-library.
Memory [unknown] Memory: The November first-party documentation and repository pass did not establish shared context and memory at the rubric's required scope. No installed-product fixture was run.
Scope [supported] Local Library and remote machine settings are separate; remote configuration is machine-scoped. Sources: emdash:gap-library.
Provenance [unknown] Provenance: The November first-party documentation and repository pass did not establish shared context and memory at the rubric's required scope. No installed-product fixture was run.
Correction [unknown] Correction: The November first-party documentation and repository pass did not establish shared context and memory at the rubric's required scope. No installed-product fixture was run.
Freshness [unknown] Freshness: The November first-party documentation and repository pass did not establish shared context and memory at the rubric's required scope. No installed-product fixture was run.
Takeover continuity [unknown] Takeover continuity: The November first-party documentation and repository pass did not establish shared context and memory at the rubric's required scope. No installed-product fixture was run.
Classic offers editor find/replace, language intelligence and app search, MCP-based external knowledge and file or image inputs; no agent-facing code index was established.
Scope
Surfaces: desktop, remote · Version: Emdash Classic v1.2.13 (17f32be, 2026-11-19); docs retrieved 2026-11-21 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-22
Documentation and pinned-source inspection only; no installed-product scenario was run.
10 atomic answers
Code search [partial] The file editor has find/replace and language intelligence; app search covers projects, tasks and conversations. No agent-facing code index. Sources: emdash:b06-file-editor, emdash:b06-search.
Indexing [unknown] Indexing: The November first-party documentation and repository pass did not establish architecture and api awareness at the rubric's required scope. No installed-product fixture was run.
External knowledge [partial] Through MCP servers synced to agents, including Context7 and Exa in the catalog. Sources: emdash:b06-mcp.
Multimodal inputs [partial] Local files and pasted images can be dropped into terminals (uploaded for remote tasks) and attached in chat. Sources: emdash:b06-remote-projects.
Freshness [unknown] Freshness: The November first-party documentation and repository pass did not establish architecture and api awareness at the rubric's required scope. No installed-product fixture was run.
Access scope [unknown] Access scope: The November first-party documentation and repository pass did not establish architecture and api awareness at the rubric's required scope. No installed-product fixture was run.
Api retrieval [unknown] Api retrieval: The November first-party documentation and repository pass did not establish architecture and api awareness at the rubric's required scope. No installed-product fixture was run.
Citations [unknown] Citations: The November first-party documentation and repository pass did not establish architecture and api awareness at the rubric's required scope. No installed-product fixture was run.
Conflict detection [unknown] Conflict detection: The November first-party documentation and repository pass did not establish architecture and api awareness at the rubric's required scope. No installed-product fixture was run.
Review enforcement [unknown] Review enforcement: The November first-party documentation and repository pass did not establish architecture and api awareness at the rubric's required scope. No installed-product fixture was run.
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.
Scope
Surfaces: desktop, remote · Version: a2bdb78f7a619ac87c1c4f86c18570f5fcffae10; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
17 atomic answers
Create [partial] Creation starts a workspace and agent rather than saving an independent issue. Sources: emdash:gap37-classic-boundary.
Edit [unknown] Edit: The November first-party documentation and repository pass did not establish native issue management and idea backlog at the rubric's required scope. No installed-product fixture was run.
Discuss [unknown] Discuss: The November first-party documentation and repository pass did not establish native issue management and idea backlog at the rubric's required scope. No installed-product fixture was run.
Prioritize [unknown] Prioritize: The November first-party documentation and repository pass did not establish native issue management and idea backlog at the rubric's required scope. No installed-product fixture was run.
Label [unknown] Label: The November first-party documentation and repository pass did not establish native issue management and idea backlog at the rubric's required scope. No installed-product fixture was run.
Assign [unknown] Assign: The November first-party documentation and repository pass did not establish native issue management and idea backlog at the rubric's required scope. No installed-product fixture was run.
Search [partial] App search indexes projects, tasks and conversations by name; archived tasks drop out. Sources: emdash:b06-search.
Filter [unknown] Filter: The November first-party documentation and repository pass did not establish native issue management and idea backlog at the rubric's required scope. No installed-product fixture was run.
Archive [supported] Tasks can be archived and restored; archiving stops the tmux session and agent process but keeps the worktree and session for resume. Sources: emdash:b06-archive.
Reopen [unknown] Reopen: The November first-party documentation and repository pass did not establish native issue management and idea backlog at the rubric's required scope. No installed-product fixture was run.
Project epic views [unknown] Project epic views: The November first-party documentation and repository pass did not establish native issue management and idea backlog at the rubric's required scope. No installed-product fixture was run.
Idea parking [unknown] Idea parking: The November first-party documentation and repository pass did not establish native issue management and idea backlog at the rubric's required scope. No installed-product fixture was run.
Explicit dispatch [supported] Creating the task launches the agent. Sources: emdash:nov07-tasks.
Task session separation [unsupported] Workspace/conversation entities and linked external issues do not form a native issue store. Sources: emdash:gap37-classic-boundary.
Metadata [unknown] Metadata: The November first-party documentation and repository pass did not establish native issue management and idea backlog at the rubric's required scope. No installed-product fixture was run.
Durable states [unsupported] No product-owned native issue state machine in the app database/runtime API. Sources: emdash:gap37-classic-boundary.
Classic documents parallel coding agents in separate worktrees.
Scope
Surfaces: desktop, remote · Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
5 atomic answers
Concurrent sessions [supported] Multiple coding agents can run at once. Sources: emdash:nov07-readme.
Concurrent tasks [supported] Separate task worktrees. Sources: emdash:nov07-readme.
Quotas [unknown] Quotas: The November first-party documentation and repository pass did not establish parallel work at the rubric's required scope. No installed-product fixture was run.
Observed concurrency [unknown] Observed concurrency: The November first-party documentation and repository pass did not establish parallel work at the rubric's required scope. No installed-product fixture was run.
Status visibility [partial] Hook-capable providers report working, awaiting input or done (status idle, working, awaiting-input, error, completed); providers without hooks lack these indicators. Automation runs show status and errors. Sources: emdash:b06-providers, emdash:b06-agent-events, emdash:b06-automations.
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.
Scope
Surfaces: desktop, remote · Version: a2bdb78f7a619ac87c1c4f86c18570f5fcffae10 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
Not separately cross-checked
Source review and pinned implementation inspection only; no installed-product, account or multi-user scenario was executed. Unanswered atomic questions remain open.
12 atomic answers
Roles [unknown] Roles: The November first-party documentation and repository pass did not establish inspectable delegation and communication at the rubric's required scope. No installed-product fixture was run.
Model harness effort [unknown] Model harness effort: The November first-party documentation and repository pass did not establish inspectable delegation and communication at the rubric's required scope. No installed-product fixture was run.
Messages [unknown] Messages: The November first-party documentation and repository pass did not establish inspectable delegation and communication at the rubric's required scope. No installed-product fixture was run.
Results return [unknown] Results return: The November first-party documentation and repository pass did not establish inspectable delegation and communication at the rubric's required scope. No installed-product fixture was run.
Cross harness [unknown] Cross harness: The November first-party documentation and repository pass did not establish inspectable delegation and communication at the rubric's required scope. No installed-product fixture was run.
Orchestration owner [unsupported] No product coordinator-agent role in the scoped manifests and APIs; underlying provider subagents remain separate. Sources: emdash:gap37-classic-boundary.
Activation [unknown] Activation: The November first-party documentation and repository pass did not establish inspectable delegation and communication at the rubric's required scope. No installed-product fixture was run.
Authentication [unknown] Authentication: The November first-party documentation and repository pass did not establish inspectable delegation and communication at the rubric's required scope. No installed-product fixture was run.
Live progress [unknown] Live progress: The November first-party documentation and repository pass did not establish inspectable delegation and communication at the rubric's required scope. No installed-product fixture was run.
Retained results [unknown] Retained results: The November first-party documentation and repository pass did not establish inspectable delegation and communication at the rubric's required scope. No installed-product fixture was run.
Followup [unknown] Followup: The November first-party documentation and repository pass did not establish inspectable delegation and communication at the rubric's required scope. No installed-product fixture was run.
Invocation [unknown] Invocation: The November first-party documentation and repository pass did not establish inspectable delegation and communication at the rubric's required scope. No installed-product fixture was run.
Events [unknown] Events: The November first-party documentation and repository pass did not establish unattended triggers at the rubric's required scope. No installed-product fixture was run.
Completion conditions [unknown] Completion conditions: The November first-party documentation and repository pass did not establish unattended triggers at the rubric's required scope. No installed-product fixture was run.
Scheduler location [supported] Project machine; Workspace Server for remote projects. Sources: emdash:nov07-automations.
Overlaps [unknown] Overlaps: The November first-party documentation and repository pass did not establish unattended triggers at the rubric's required scope. No installed-product fixture was run.
Retries [unknown] Retries: The November first-party documentation and repository pass did not establish unattended triggers at the rubric's required scope. No installed-product fixture was run.
Client independence [partial] Remote schedules do not need desktop connectivity unless desktop-backed services are required. Sources: emdash:nov07-automations.
Provider hooks expose attention needs and resumable sessions.
Scope
Surfaces: desktop, remote · Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
10 atomic answers
Pause [unknown] Pause: The November first-party documentation and repository pass did not establish intervention and attention at the rubric's required scope. No installed-product fixture was run.
Stop [unknown] Stop: The November first-party documentation and repository pass did not establish intervention and attention at the rubric's required scope. No installed-product fixture was run.
Steer [supported] Users chat with the agent or type in its TUI; prompts sent while a Chat UI agent is busy are queued and can be edited or deleted. Sources: emdash:b06-tasks, emdash:b06-acp-chat.
Pending decisions [partial] Chat UI surfaces provider permission requests in a queue for the user to answer; auto-approve on supported providers skips them. Sources: emdash:b06-acp-chat, emdash:b06-providers.
Escalation [unknown] Escalation: The November first-party documentation and repository pass did not establish intervention and attention at the rubric's required scope. No installed-product fixture was run.
Chat terminal parity [partial] Each agent runs in Chat UI or TUI. Chat keeps the provider's own options and permission requests; TUI keeps a separate auto-approve flag; hook support differs by provider. Sources: emdash:b06-providers, emdash:b06-provider-settings.
Retained history [partial] Conversations are saved per task; running processes persist only with tmux or provider resume. Sources: emdash:b06-tasks, emdash:b06-tmux.
Classic shows per-conversation attention and status signals, automation run history and a per-machine conversation list; no parent-child or dependency fleet view was established.
Scope
Surfaces: desktop, remote · Version: Emdash Classic v1.2.13 (17f32be, 2026-11-19); docs retrieved 2026-11-21 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-22
Documentation and pinned-source inspection only; no installed-product scenario was run.
8 atomic answers
Fleet fixture [unknown] Fleet fixture: The November first-party documentation and repository pass did not establish fleet and epic management ui at the rubric's required scope. No installed-product fixture was run.
Parent child [unknown] Parent child: The November first-party documentation and repository pass did not establish fleet and epic management ui at the rubric's required scope. No installed-product fixture was run.
Dependencies [unknown] Dependencies: The November first-party documentation and repository pass did not establish fleet and epic management ui at the rubric's required scope. No installed-product fixture was run.
Attention [partial] Permission, idle and elicitation hook events mark a conversation as needing attention, with notifications and sounds, for hook-capable providers. Sources: emdash:b06-agent-events, emdash:b06-providers.
History [partial] Automation run history with timing, status and errors, saved conversations per task and a Conversations list per machine. Sources: emdash:b06-automations, emdash:b06-machines.
Workload [unknown] Workload: The November first-party documentation and repository pass did not establish fleet and epic management ui at the rubric's required scope. No installed-product fixture was run.
Navigation errors [unknown] Navigation errors: The November first-party documentation and repository pass did not establish fleet and epic management ui at the rubric's required scope. No installed-product fixture was run.
Fixture mode [unknown] Fixture mode: The November first-party documentation and repository pass did not establish fleet and epic management ui at the rubric's required scope. No installed-product fixture was run.
Classic automations let users choose the agent, provider options, prompt and workspace for scheduled runs.
Scope
Surfaces: desktop, remote · Version: First-party documentation/source checked 2026-11-07; exact pinned source revision is recorded in each citation. No installed-product fixture.; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
10 atomic answers
Quick task [supported] Create a task with name (or generated name), source branch, issue or PR and a provider; no workflow preset is needed. Sources: emdash:b06-tasks.
Growing epic [unknown] Growing epic: The November first-party documentation and repository pass did not establish workflow flexibility and orchestration visibility at the rubric's required scope. No installed-product fixture was run.
Natural language [unknown] Natural language: The November first-party documentation and repository pass did not establish workflow flexibility and orchestration visibility at the rubric's required scope. No installed-product fixture was run.
Agent configuration [supported] Automation configuration selects the agent and available provider options. Sources: emdash:gap-automation.
In run changes [unknown] In run changes: The November first-party documentation and repository pass did not establish workflow flexibility and orchestration visibility at the rubric's required scope. No installed-product fixture was run.
Live roles [unknown] Live roles: The November first-party documentation and repository pass did not establish workflow flexibility and orchestration visibility at the rubric's required scope. No installed-product fixture was run.
Retained relationships [unknown] Retained relationships: The November first-party documentation and repository pass did not establish workflow flexibility and orchestration visibility at the rubric's required scope. No installed-product fixture was run.
Discoverability [unknown] Discoverability: The November first-party documentation and repository pass did not establish workflow flexibility and orchestration visibility at the rubric's required scope. No installed-product fixture was run.
Auth friction [partial] Each agent CLI must be installed and authenticated on every machine it runs on; local credentials are not copied to remote machines. Sources: emdash:b06-providers, emdash:b06-remote.
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.
Scope
Surfaces: desktop, remote · Version: a2bdb78f7a619ac87c1c4f86c18570f5fcffae10; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: local, user-owned-remote · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
Byo remote [supported] Workspace Server on a machine reached by SSH. Sources: emdash:nov07-remote.
Self hosted [unknown] Self hosted: The November first-party documentation and repository pass did not establish laptop-independent execution at the rubric's required scope. No installed-product fixture was run.
Managed cloud [unsupported] No managed vendor execution service in Classic source; only local and SSH machine workspaces. Sources: emdash:gap37-classic-boundary.
Hybrid [unknown] Hybrid: The November first-party documentation and repository pass did not establish laptop-independent execution at the rubric's required scope. No installed-product fixture was run.
Provisioning [partial] The user supplies the machine; Emdash installs, starts and updates the Workspace Server runtime over SSH. Sources: emdash:b06-machines, emdash:b06-ssh.
Payer [supported] User supplies the remote machine. Sources: emdash:nov07-remote.
Resources [unknown] Resources: The November first-party documentation and repository pass did not establish laptop-independent execution at the rubric's required scope. No installed-product fixture was run.
Region [unknown] Region: The November first-party documentation and repository pass did not establish laptop-independent execution at the rubric's required scope. No installed-product fixture was run.
Expiry [unknown] Expiry: The November first-party documentation and repository pass did not establish laptop-independent execution at the rubric's required scope. No installed-product fixture was run.
Client disconnect [partial] Remote automations run without the desktop connected and tmux keeps terminal and TUI processes; other processes stop with the session. Sources: emdash:b06-automations, emdash:b06-tmux.
Other device continuation [unknown] Other device continuation: The November first-party documentation and repository pass did not establish laptop-independent execution at the rubric's required scope. No installed-product fixture was run.
Classic creates task worktrees or uses an existing checkout. It does not implement container or VM workspace provisioning.
Scope
Surfaces: desktop, remote · Version: a2bdb78f7a619ac87c1c4f86c18570f5fcffae10; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
12 atomic answers
Checkout [partial] Existing workspace or root checkout can be selected; isolation can be disabled with a warning. Sources: emdash:nov07-tasks.
Branch [supported] Separate branch by default. Sources: emdash:nov07-tasks.
Worktree [supported] Separate Git worktree by default. Sources: emdash:nov07-tasks.
Container [unsupported] No container isolation backend in the scoped workspace provisioning runtimes. Sources: emdash:gap37-classic-boundary.
Vm [unsupported] No VM isolation backend in the scoped workspace provisioning runtimes. Sources: emdash:gap37-classic-boundary.
Os sandbox [unknown] Os sandbox: The November first-party documentation and repository pass did not establish workspace and process isolation at the rubric's required scope. No installed-product fixture was run.
Filesystem [partial] Separate worktree directories; tasks using the same directory share files, and worktrees can be disabled. Sources: emdash:b06-remote-projects, emdash:b06-tasks.
Process [unknown] Process: The November first-party documentation and repository pass did not establish workspace and process isolation at the rubric's required scope. No installed-product fixture was run.
Network [unknown] Network: The November first-party documentation and repository pass did not establish workspace and process isolation at the rubric's required scope. No installed-product fixture was run.
Secrets [partial] Project env vars and preserved .env files are copied into tasks; since v1.2.10 tokens and env values stay out of process arguments. No dedicated secret store is documented. Sources: emdash:b06-project-config, emdash:b06-changelog.
Code separation [supported] Per-task worktrees keep changes apart from the main checkout and other tasks. Sources: emdash:b06-tasks.
Security boundary [unknown] Security boundary: The November first-party documentation and repository pass did not establish workspace and process isolation at the rubric's required scope. No installed-product fixture was run.
Optional tmux preserves terminal processes/history across view closure or SSH loss, with host reboot excluded.
Scope
Surfaces: desktop, remote · Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
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.
12 atomic answers
Client disconnect [supported] 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. Sources: emdash:nov07-tmux.
Worker crash [unknown] Worker crash: The November first-party documentation and repository pass did not establish recovery, expiry and continuity at the rubric's required scope. No installed-product fixture was run.
Service restart [unsupported] Host reboot does not preserve tmux processes. Sources: emdash:nov07-tmux.
Expiry [unknown] Expiry: The November first-party documentation and repository pass did not establish recovery, expiry and continuity at the rubric's required scope. No installed-product fixture was run.
Transcript reload [supported] tmux keeps terminal history on the execution host; Chat UI history has a separate lifetime. Sources: emdash:nov07-tmux.
Process reconnect [supported] Reattach to the running tmux session. Sources: emdash:nov07-tmux.
Task resume [partial] Provider resume for the listed providers; archived tasks keep their session id for resume. Sources: emdash:b06-providers, emdash:b06-archive.
State reconstruction [unknown] State reconstruction: The November first-party documentation and repository pass did not establish recovery, expiry and continuity at the rubric's required scope. No installed-product fixture was run.
Context loss [partial] Tmux does not survive a host reboot or explicit termination. Sources: emdash:b06-tmux.
Duplicate actions [unknown] Duplicate actions: The November first-party documentation and repository pass did not establish recovery, expiry and continuity at the rubric's required scope. No installed-product fixture was run.
Manual repair [supported] tmux ls/attach can inspect and reconnect on the host; tmux must be installed and already enabled for that session. Sources: emdash:nov07-tmux.
Multi day continuity [unknown] Multi day continuity: The November first-party documentation and repository pass did not establish recovery, expiry and continuity at the rubric's required scope. No installed-product fixture was run.
Remote previews have explicit port forwarding and manual collision guidance.
Scope
Surfaces: desktop, remote · Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
10 atomic answers
Dependencies [supported] Prepare, setup, run and teardown scripts, shareable through .emdash.json. Sources: emdash:b06-project-config.
Caches [unknown] Caches: The November first-party documentation and repository pass did not establish development environment reliability at the rubric's required scope. No installed-product fixture was run.
Snapshots [unknown] Snapshots: The November first-party documentation and repository pass did not establish development environment reliability at the rubric's required scope. No installed-product fixture was run.
Services [partial] Run scripts start dev servers with an EMDASH_PORT range; a Docker Compose example is documented. Sources: emdash:b06-project-config.
Ports [supported] Manual or detected remote-port forwarding. Sources: emdash:nov07-browser.
Secrets [partial] Personal project env vars and preserve patterns copy .env files into tasks; no secret store. Sources: emdash:b06-project-config.
Duplicate installs [unknown] Duplicate installs: The November first-party documentation and repository pass did not establish development environment reliability at the rubric's required scope. No installed-product fixture was run.
Collisions [partial] Occupied local port may require selecting another port; automatic repair unverified. Sources: emdash:nov07-browser.
Automatic repair [unknown] Automatic repair: The November first-party documentation and repository pass did not establish development environment reliability at the rubric's required scope. No installed-product fixture was run.
v1.2.10 removed a 30-second failure on long workspace operations. The checked docs and release notes name no agent run, turn, token or spend limits; those parts remain unknown.
Scope
Surfaces: desktop, remote · Version: Emdash Classic v1.2.13 (17f32be, 2026-11-19); docs retrieved 2026-11-21 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-22
Documentation and pinned-source inspection only; no installed-product scenario was run.
8 atomic answers
Time limits [unknown] Time limits: The November first-party documentation and repository pass did not establish limits and failure handling at the rubric's required scope. No installed-product fixture was run.
Turn limits [unknown] Turn limits: The November first-party documentation and repository pass did not establish limits and failure handling at the rubric's required scope. No installed-product fixture was run.
Token limits [unknown] Token limits: The November first-party documentation and repository pass did not establish limits and failure handling at the rubric's required scope. No installed-product fixture was run.
Spend limits [unknown] Spend limits: The November first-party documentation and repository pass did not establish limits and failure handling at the rubric's required scope. No installed-product fixture was run.
Timeouts [partial] Long workspace operations no longer fail after 30 seconds (v1.2.10); agent run timeouts are not documented. Sources: emdash:b06-changelog.
Retries [unknown] Retries: The November first-party documentation and repository pass did not establish limits and failure handling at the rubric's required scope. No installed-product fixture was run.
Provider failures [unknown] Provider failures: The November first-party documentation and repository pass did not establish limits and failure handling at the rubric's required scope. No installed-product fixture was run.
Enforcement [unknown] Enforcement: The November first-party documentation and repository pass did not establish limits and failure handling at the rubric's required scope. No installed-product fixture was run.
Traces [unknown] Traces: The November first-party documentation and repository pass did not establish truthful status and operational statistics at the rubric's required scope. No installed-product fixture was run.
Usage export [unknown] Usage export: The November first-party documentation and repository pass did not establish truthful status and operational statistics at the rubric's required scope. No installed-product fixture was run.
Task stats [unknown] Task stats: The November first-party documentation and repository pass did not establish truthful status and operational statistics at the rubric's required scope. No installed-product fixture was run.
Agent stats [unknown] Agent stats: The November first-party documentation and repository pass did not establish truthful status and operational statistics at the rubric's required scope. No installed-product fixture was run.
Project stats [unknown] Project stats: The November first-party documentation and repository pass did not establish truthful status and operational statistics at the rubric's required scope. No installed-product fixture was run.
Time stats [partial] Per-check durations appear when GitHub supplies start/completion times; aggregated statistics by time were not established. Sources: emdash:gap-checks.
Failure status [supported] PR checks show pass, fail, pending, skipped or cancelled and failed checks sort first. Sources: emdash:gap-checks.
Reconnect consistency [unknown] Reconnect consistency: The November first-party documentation and repository pass did not establish truthful status and operational statistics at the rubric's required scope. No installed-product fixture was run.
Performance method [unknown] Performance method: The November first-party documentation and repository pass did not establish truthful status and operational statistics at the rubric's required scope. No installed-product fixture was run.
Responsiveness [unknown] Responsiveness: The November first-party documentation and repository pass did not establish truthful status and operational statistics at the rubric's required scope. No installed-product fixture was run.
Classic shows Claude Code and Codex subscription usage windows; it does not compute task or session cost.
Scope
Surfaces: desktop, remote · Version: Emdash Classic v1.2.13 (17f32be, 2026-11-19); docs retrieved 2026-11-21 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-22
Documentation and pinned-source inspection only; no installed-product scenario was run.
14 atomic answers
Task cost [unknown] Task cost: The November first-party documentation and repository pass did not establish per-task api and compute cost at the rubric's required scope. No installed-product fixture was run.
Session cost [unknown] Session cost: The November first-party documentation and repository pass did not establish per-task api and compute cost at the rubric's required scope. No installed-product fixture was run.
Child cost [unknown] Child cost: The November first-party documentation and repository pass did not establish per-task api and compute cost at the rubric's required scope. No installed-product fixture was run.
Epic cost [unknown] Epic cost: The November first-party documentation and repository pass did not establish per-task api and compute cost at the rubric's required scope. No installed-product fixture was run.
Harness aggregation [unknown] Harness aggregation: The November first-party documentation and repository pass did not establish per-task api and compute cost at the rubric's required scope. No installed-product fixture was run.
Billed vs estimated [unknown] Billed vs estimated: The November first-party documentation and repository pass did not establish per-task api and compute cost at the rubric's required scope. No installed-product fixture was run.
Tokens [unknown] Tokens: The November first-party documentation and repository pass did not establish per-task api and compute cost at the rubric's required scope. No installed-product fixture was run.
Subscription allowance [partial] Settings, Usage shows used percent and reset time per window for Claude Code and Codex accounts only. Sources: emdash:b06-usage, emdash:b06-machines.
Provider reconciliation [unknown] Provider reconciliation: The November first-party documentation and repository pass did not establish per-task api and compute cost at the rubric's required scope. No installed-product fixture was run.
Compute cost [unknown] Compute cost: The November first-party documentation and repository pass did not establish per-task api and compute cost at the rubric's required scope. No installed-product fixture was run.
Refresh delay [unknown] Refresh delay: The November first-party documentation and repository pass did not establish per-task api and compute cost at the rubric's required scope. No installed-product fixture was run.
Alerts [unknown] Alerts: The November first-party documentation and repository pass did not establish per-task api and compute cost at the rubric's required scope. No installed-product fixture was run.
Export [unknown] Export: The November first-party documentation and repository pass did not establish per-task api and compute cost at the rubric's required scope. No installed-product fixture was run.
Drilldown [unknown] Drilldown: The November first-party documentation and repository pass did not establish per-task api and compute cost at the rubric's required scope. No installed-product fixture was run.
Automation runs queue behind a concurrency cap; machines show resource usage without limiting work.
Scope
Surfaces: desktop, remote · Version: Emdash Classic v1.2.13 (17f32be, 2026-11-19); docs retrieved 2026-11-21 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-22
Documentation and pinned-source inspection only; no installed-product scenario was run.
12 atomic answers
Concurrency [unknown] Concurrency: The November first-party documentation and repository pass did not establish compute-aware scheduling and verification at the rubric's required scope. No installed-product fixture was run.
Queues [supported] Due automation runs wait in a queue until a run slot frees (default four concurrent runs). Sources: emdash:b06-scheduler.
Cpu ram [unknown] Cpu ram: The November first-party documentation and repository pass did not establish compute-aware scheduling and verification at the rubric's required scope. No installed-product fixture was run.
Backpressure [unknown] Backpressure: The November first-party documentation and repository pass did not establish compute-aware scheduling and verification at the rubric's required scope. No installed-product fixture was run.
Host awareness [partial] The machine System tab shows resource usage; it does not gate work. Sources: emdash:b06-machines.
Check reuse [unknown] Check reuse: The November first-party documentation and repository pass did not establish compute-aware scheduling and verification at the rubric's required scope. No installed-product fixture was run.
Check deduplication [unknown] Check deduplication: The November first-party documentation and repository pass did not establish compute-aware scheduling and verification at the rubric's required scope. No installed-product fixture was run.
Bounded tests [unknown] Bounded tests: The November first-party documentation and repository pass did not establish compute-aware scheduling and verification at the rubric's required scope. No installed-product fixture was run.
Cancellation [unknown] Cancellation: The November first-party documentation and repository pass did not establish compute-aware scheduling and verification at the rubric's required scope. No installed-product fixture was run.
Fairness [unknown] Fairness: The November first-party documentation and repository pass did not establish compute-aware scheduling and verification at the rubric's required scope. No installed-product fixture was run.
Recovery [unknown] Recovery: The November first-party documentation and repository pass did not establish compute-aware scheduling and verification at the rubric's required scope. No installed-product fixture was run.
Shared limits [unknown] Shared limits: The November first-party documentation and repository pass did not establish compute-aware scheduling and verification at the rubric's required scope. No installed-product fixture was run.
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.
Scope
Surfaces: desktop, remote · Version: a2bdb78f7a619ac87c1c4f86c18570f5fcffae10 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
Not separately cross-checked
Source review and pinned implementation inspection only; no installed-product, account or multi-user scenario was executed. Unanswered atomic questions remain open.
11 atomic answers
Visibility [unknown] Visibility: The November first-party documentation and repository pass did not establish live human collaboration at the rubric's required scope. No installed-product fixture was run.
Discussion [unknown] Discussion: The November first-party documentation and repository pass did not establish live human collaboration at the rubric's required scope. No installed-product fixture was run.
Comments [unknown] Comments: The November first-party documentation and repository pass did not establish live human collaboration at the rubric's required scope. No installed-product fixture was run.
Presence [unknown] Presence: The November first-party documentation and repository pass did not establish live human collaboration at the rubric's required scope. No installed-product fixture was run.
Coprompting [unsupported] No distinct human membership/input-channel model for one shared agent in Classic. Sources: emdash:gap37-classic-boundary.
Ordering [unknown] Ordering: The November first-party documentation and repository pass did not establish live human collaboration at the rubric's required scope. No installed-product fixture was run.
Conflicts [unknown] Conflicts: The November first-party documentation and repository pass did not establish live human collaboration at the rubric's required scope. No installed-product fixture was run.
Attribution [unknown] Attribution: The November first-party documentation and repository pass did not establish live human collaboration at the rubric's required scope. No installed-product fixture was run.
Permissions [unknown] Permissions: The November first-party documentation and repository pass did not establish live human collaboration at the rubric's required scope. No installed-product fixture was run.
Plan restrictions [unknown] Plan restrictions: The November first-party documentation and repository pass did not establish live human collaboration at the rubric's required scope. No installed-product fixture was run.
Owner online [unknown] Owner online: The November first-party documentation and repository pass did not establish live human collaboration at the rubric's required scope. No installed-product fixture was run.
Classic has no application organization roles or enterprise SSO. SSH authentication applies to the remote machine, not product team membership.
Scope
Surfaces: desktop, remote · Version: a2bdb78f7a619ac87c1c4f86c18570f5fcffae10 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
Not separately cross-checked
Source review and pinned implementation inspection only; no installed-product, account or multi-user scenario was executed. Unanswered atomic questions remain open.
9 atomic answers
Organization roles [unsupported] No human organization-role model in Classic. Sources: emdash:gap37-classic-boundary.
Project roles [unknown] Project roles: The November first-party documentation and repository pass did not establish roles and access boundaries at the rubric's required scope. No installed-product fixture was run.
Task roles [unknown] Task roles: The November first-party documentation and repository pass did not establish roles and access boundaries at the rubric's required scope. No installed-product fixture was run.
Membership [unknown] Membership: The November first-party documentation and repository pass did not establish roles and access boundaries at the rubric's required scope. No installed-product fixture was run.
Provisioning [unknown] Provisioning: The November first-party documentation and repository pass did not establish roles and access boundaries at the rubric's required scope. No installed-product fixture was run.
Unauthorized access [unknown] Unauthorized access: The November first-party documentation and repository pass did not establish roles and access boundaries at the rubric's required scope. No installed-product fixture was run.
Revocation [unknown] Revocation: The November first-party documentation and repository pass did not establish roles and access boundaries at the rubric's required scope. No installed-product fixture was run.
Plan scope [unknown] Plan scope: The November first-party documentation and repository pass did not establish roles and access boundaries at the rubric's required scope. No installed-product fixture was run.
Classic lists provider-specific auto-approve, which skips file-operation permission prompts, and confirms before discarding changes. Product-enforced permission policy was not established.
Scope
Surfaces: desktop, remote · Version: First-party documentation/source checked 2026-11-07; exact pinned source revision is recorded in each citation. No installed-product fixture.; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
14 atomic answers
Command [partial] Chat UI relays provider permission requests; auto-approve skips them on supported providers. Emdash has no own command policy. Sources: emdash:b06-acp-chat, emdash:b06-providers.
Tool [unknown] Tool: The November first-party documentation and repository pass did not establish approvals and temporary access at the rubric's required scope. No installed-product fixture was run.
Network [unknown] Network: The November first-party documentation and repository pass did not establish approvals and temporary access at the rubric's required scope. No installed-product fixture was run.
Secret [unknown] Secret: The November first-party documentation and repository pass did not establish approvals and temporary access at the rubric's required scope. No installed-product fixture was run.
Delivery [unknown] Delivery: The November first-party documentation pass did not establish delivery approvals; per-provider auto-approve covers file-operation prompts, not delivery. No installed-product fixture was run.
Approver identity [unknown] Approver identity: The November first-party documentation and repository pass did not establish approvals and temporary access at the rubric's required scope. No installed-product fixture was run.
Lifetime [unknown] Lifetime: The November first-party documentation and repository pass did not establish approvals and temporary access at the rubric's required scope. No installed-product fixture was run.
Allow [unknown] Allow: The November first-party documentation and repository pass did not establish approvals and temporary access at the rubric's required scope. No installed-product fixture was run.
Deny [unknown] Deny: The November first-party documentation and repository pass did not establish approvals and temporary access at the rubric's required scope. No installed-product fixture was run.
Revoke [unknown] Revoke: The November first-party documentation and repository pass did not establish approvals and temporary access at the rubric's required scope. No installed-product fixture was run.
Tunnels [partial] Port forwards to remote dev servers are created per preview or manually; no lifetime or access controls are documented. Sources: emdash:b06-browser.
Defaults [partial] Chat UI uses each provider's own options and modes; TUI auto-approve is a per-host, per-provider setting that defaults off. Sources: emdash:b06-provider-settings.
Safer modes [unknown] Safer modes: The providers page lists which providers support auto-approve but does not say whether it is optional or off by default, so available safer modes were not established. No installed-product fixture was run.
Enforcement [unknown] Enforcement: The November first-party documentation and repository pass did not establish approvals and temporary access at the rubric's required scope. No installed-product fixture was run.
Approvals [unknown] Approvals: The November first-party documentation and repository pass did not establish decision and activity history at the rubric's required scope. No installed-product fixture was run.
Edits [unknown] Edits: The November first-party documentation and repository pass did not establish decision and activity history at the rubric's required scope. No installed-product fixture was run.
Discussion [unknown] Discussion: The November first-party documentation and repository pass did not establish decision and activity history at the rubric's required scope. No installed-product fixture was run.
Decisions [unknown] Decisions: The November first-party documentation and repository pass did not establish decision and activity history at the rubric's required scope. No installed-product fixture was run.
Cross user persistence [unknown] Cross user persistence: The November first-party documentation and repository pass did not establish decision and activity history at the rubric's required scope. No installed-product fixture was run.
Cross session persistence [unknown] Cross session persistence: The November first-party documentation and repository pass did not establish decision and activity history at the rubric's required scope. No installed-product fixture was run.
Export [unknown] Export: The November first-party documentation and repository pass did not establish decision and activity history at the rubric's required scope. No installed-product fixture was run.
Mutability [unknown] Mutability: The November first-party documentation and repository pass did not establish decision and activity history at the rubric's required scope. No installed-product fixture was run.
Retention [unknown] Retention: The November first-party documentation and repository pass did not establish decision and activity history at the rubric's required scope. No installed-product fixture was run.
Integrity [unknown] Integrity: The November first-party documentation and repository pass did not establish decision and activity history at the rubric's required scope. No installed-product fixture was run.
Classic offers diff inspection and PR check/comment context in the task workspace. Usability was not measured.
Scope
Surfaces: desktop · Version: First-party documentation/source checked 2026-11-07; exact pinned source revision is recorded in each citation. No installed-product fixture.; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
13 atomic answers
Pending reviews [unknown] Pending reviews: The November first-party documentation and repository pass did not establish review experience and guidance at the rubric's required scope. No installed-product fixture was run.
Comments [partial] Line comments on working-tree, PR or commit diffs can be attached to chat for the agent. Sources: emdash:b06-line-comments.
Request changes [partial] Feedback goes back through diff comments or chat; there is no formal request-changes state. Sources: emdash:b06-line-comments.
Shipping guidance [partial] Commit, Commit & Push and Commit & Create PR, with push and publish actions in the footer. Sources: emdash:b06-diff-view.
Effort [unknown] Effort: The November first-party documentation and repository pass did not establish review experience and guidance at the rubric's required scope. No installed-product fixture was run.
Missed evidence [unknown] Missed evidence: The November first-party documentation and repository pass did not establish review experience and guidance at the rubric's required scope. No installed-product fixture was run.
Keyboard [partial] Documented, mostly rebindable shortcuts such as Cmd+N, Cmd+J and Cmd+Shift+B. Sources: emdash:b06-shortcuts.
Narrow screen [unknown] Narrow screen: The November first-party documentation and repository pass did not establish review experience and guidance at the rubric's required scope. No installed-product fixture was run.
Context switching [supported] PR files, commits, checks, comments and merge state appear in the task sidebar without leaving Emdash. Sources: emdash:gap-diff.
Roles [unknown] Roles: The November first-party documentation and repository pass did not establish review experience and guidance at the rubric's required scope. No installed-product fixture was run.
Retained context [unknown] Retained context: The November first-party documentation and repository pass did not establish review experience and guidance at the rubric's required scope. No installed-product fixture was run.
No colleague takeover was established in Classic; within a task, new conversations can use a different agent without automatic context transfer.
Scope
Surfaces: desktop, remote · Version: Emdash Classic v1.2.13 (17f32be, 2026-11-19); docs retrieved 2026-11-21 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-22
Documentation and pinned-source inspection only; no installed-product scenario was run.
12 atomic answers
Ongoing takeover [unknown] Ongoing takeover: The November first-party documentation and repository pass did not establish colleague takeover and continuity at the rubric's required scope. No installed-product fixture was run.
Same task [unknown] Same task: The November first-party documentation and repository pass did not establish colleague takeover and continuity at the rubric's required scope. No installed-product fixture was run.
Session history [unknown] Session history: The November first-party documentation and repository pass did not establish colleague takeover and continuity at the rubric's required scope. No installed-product fixture was run.
Decisions [unknown] Decisions: The November first-party documentation and repository pass did not establish colleague takeover and continuity at the rubric's required scope. No installed-product fixture was run.
Artifacts [unknown] Artifacts: The November first-party documentation and repository pass did not establish colleague takeover and continuity at the rubric's required scope. No installed-product fixture was run.
Permissions [unknown] Permissions: The November first-party documentation and repository pass did not establish colleague takeover and continuity at the rubric's required scope. No installed-product fixture was run.
Runtime context [unknown] Runtime context: The November first-party documentation and repository pass did not establish colleague takeover and continuity at the rubric's required scope. No installed-product fixture was run.
Owner disconnect [unknown] Owner disconnect: The November first-party documentation and repository pass did not establish colleague takeover and continuity at the rubric's required scope. No installed-product fixture was run.
Ownership [unknown] Ownership: The November first-party documentation and repository pass did not establish colleague takeover and continuity at the rubric's required scope. No installed-product fixture was run.
Attribution [unknown] Attribution: The November first-party documentation and repository pass did not establish colleague takeover and continuity at the rubric's required scope. No installed-product fixture was run.
Context loss [unknown] Context loss: The November first-party documentation and repository pass did not establish colleague takeover and continuity at the rubric's required scope. No installed-product fixture was run.
Harness transfer [partial] Each conversation in a task has its own provider, so a new conversation can use another agent; context is not carried over automatically. Sources: emdash:b06-conversations.
Documents [unknown] Documents: The November first-party documentation and repository pass did not establish retained artifacts and outputs at the rubric's required scope. No installed-product fixture was run.
Screenshots [unknown] Screenshots: The November first-party documentation and repository pass did not establish retained artifacts and outputs at the rubric's required scope. No installed-product fixture was run.
Recordings [unknown] Recordings: The November first-party documentation and repository pass did not establish retained artifacts and outputs at the rubric's required scope. No installed-product fixture was run.
Reviewer outputs [unknown] Reviewer outputs: The November first-party documentation and repository pass did not establish retained artifacts and outputs at the rubric's required scope. No installed-product fixture was run.
Gallery [unknown] Gallery: The November first-party documentation and repository pass did not establish retained artifacts and outputs at the rubric's required scope. No installed-product fixture was run.
Revision links [unknown] Revision links: The November first-party documentation and repository pass did not establish retained artifacts and outputs at the rubric's required scope. No installed-product fixture was run.
Persistence [partial] Browser tabs and last URL restore; general artifact retention remains unverified. Sources: emdash:nov07-browser.
Child findings [unknown] Child findings: The November first-party documentation and repository pass did not establish retained artifacts and outputs at the rubric's required scope. No installed-product fixture was run.
Prompt leakage [unknown] Prompt leakage: The November first-party documentation and repository pass did not establish retained artifacts and outputs at the rubric's required scope. No installed-product fixture was run.
Surfaces: desktop, remote · Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
11 atomic answers
Tests [unknown] Tests: The November first-party documentation and repository pass did not establish verification and spec gates at the rubric's required scope. No installed-product fixture was run.
Lint [unknown] Lint: The November first-party documentation and repository pass did not establish verification and spec gates at the rubric's required scope. No installed-product fixture was run.
Types [unknown] Types: The November first-party documentation and repository pass did not establish verification and spec gates at the rubric's required scope. No installed-product fixture was run.
Ci [supported] GitHub Actions check-run inspection. Sources: emdash:nov07-checks.
Independent review [unknown] Independent review: The November first-party documentation and repository pass did not establish verification and spec gates at the rubric's required scope. No installed-product fixture was run.
Spec checks [unknown] Spec checks: The November first-party documentation and repository pass did not establish verification and spec gates at the rubric's required scope. No installed-product fixture was run.
Required checks [partial] Branch requirements are enforced by GitHub; Emdash can merge a blocked GitHub PR only after the user ticks a bypass-rules checkbox, and GitHub decides whether that bypass is allowed. Sources: emdash:b06-merge.
Failure blocking [unknown] Failure blocking: The November first-party documentation and repository pass did not establish verification and spec gates at the rubric's required scope. No installed-product fixture was run.
Requirement conflicts [unknown] Requirement conflicts: The November first-party documentation and repository pass did not establish verification and spec gates at the rubric's required scope. No installed-product fixture was run.
Configured policy [unknown] Configured policy: The November first-party documentation and repository pass did not establish verification and spec gates at the rubric's required scope. No installed-product fixture was run.
Enforced policy [unknown] Enforced policy: The November first-party documentation and repository pass did not establish verification and spec gates at the rubric's required scope. No installed-product fixture was run.
Comments [partial] Pull Requests section can show PR comments; comment authoring is not established. Sources: emdash:gap-diff.
Ci response [partial] Inspect check status; automated response was not established. Sources: emdash:nov07-readme.
Rebase [unknown] Rebase: The November first-party documentation and repository pass did not establish git and pull request workflow at the rubric's required scope. No installed-product fixture was run.
Conflicts [partial] Changes list marks conflicted file status; automated conflict resolution remains unknown. Sources: emdash:gap-diff.
Product state [supported] PR files, commits, checks, comments and merge state are tracked per task branch. Sources: emdash:b06-diff-view.
Classic advertises merging reviewed changes in the app.
Scope
Surfaces: desktop, remote · Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
6 atomic answers
Approve [unknown] Approve: The November first-party documentation and repository pass did not establish merge and deployment authority at the rubric's required scope. No installed-product fixture was run.
Release [unknown] Release: The November first-party documentation and repository pass did not establish merge and deployment authority at the rubric's required scope. No installed-product fixture was run.
Deploy [unknown] Deploy: The November first-party documentation and repository pass did not establish merge and deployment authority at the rubric's required scope. No installed-product fixture was run.
Exact revision [unknown] Exact revision: The November first-party documentation and repository pass did not establish merge and deployment authority at the rubric's required scope. No installed-product fixture was run.
Authority enforcement [partial] Merges use the project's selected GitHub account, so the Git host's permissions apply; Emdash adds no approval rules. Sources: emdash:b06-github-accounts, emdash:b06-merge.
Classic links current-head PR checks to GitHub and can discard unstaged changes with confirmation. General rollback remains unknown.
Scope
Surfaces: desktop · Version: First-party documentation/source checked 2026-11-07; exact pinned source revision is recorded in each citation. No installed-product fixture.; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
Pr links [supported] The task's pull request is shown in its Pull Requests section. Sources: emdash:b06-diff-view.
Build links [supported] Each CI check includes an external link to the full GitHub check run. Sources: emdash:gap-checks.
Deployment links [unknown] Deployment links: The November first-party documentation and repository pass did not establish completion evidence and rollback at the rubric's required scope. No installed-product fixture was run.
Delivery status [partial] PR merge state is shown; deployment status is not tracked in the pinned source-control code. Sources: emdash:b06-diff-view, emdash:b06-merge.
Retained evidence [partial] Check runs are synced from GitHub for the PR's current head commit when the Checks tab opens or the head changes; durable retention and stale-approval invalidation were not established. Sources: emdash:gap-checks.
Rollback [unknown] Rollback: The November first-party documentation and repository pass did not establish completion evidence and rollback at the rubric's required scope. No installed-product fixture was run.
Revert [unknown] Revert: The November first-party documentation and repository pass did not establish completion evidence and rollback at the rubric's required scope. No installed-product fixture was run.
Stale approval invalidation [unknown] Stale approval invalidation: The November first-party documentation and repository pass did not establish completion evidence and rollback at the rubric's required scope. No installed-product fixture was run.
Classic repository is Apache-2.0. The Workspace Server is in the same Apache-2.0 repository.
Scope
Surfaces: desktop, remote · Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision.; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
The remaining atomic questions and the rubric scenario are unverified. Documentation is not a successful product test.
6 atomic answers
Client license [supported] Apache-2.0, subject to component notices. Sources: emdash:nov07-license.
Server license [supported] Apache-2.0: the Workspace Server (apps/workspace-server) declares Apache-2.0 in the same repository, with no separate license. Sources: emdash:b06-ws-license.
Hosted extensions [unknown] Hosted extensions: The November first-party documentation and repository pass did not establish source and license at the rubric's required scope. No installed-product fixture was run.
Hosted parity [unknown] Hosted parity: The November first-party documentation and repository pass did not establish source and license at the rubric's required scope. No installed-product fixture was run.
Vendor dependencies [partial] Agent providers are separate dependencies. Full account-independent use was not tested. Sources: emdash:nov07-remote, emdash:nov07-readme.
Export [unknown] Export: The November first-party documentation and repository pass did not establish hosting and exit at the rubric's required scope. No installed-product fixture was run.
Import [partial] Imports projects, tasks, conversations and SSH connections from an Emdash v0 database; no import from other tools was found. Sources: emdash:b06-legacy-import, emdash:b06-rel-1212.
Formats [unknown] Formats: The November first-party documentation and repository pass did not establish hosting and exit at the rubric's required scope. No installed-product fixture was run.
Cancellation [unknown] Cancellation: The November first-party documentation and repository pass did not establish hosting and exit at the rubric's required scope. No installed-product fixture was run.
Account independence [supported] Local use needs no sign-in or GitHub connection. Sources: emdash:b06-installation.
History portability [unknown] History portability: The November first-party documentation and repository pass did not establish hosting and exit at the rubric's required scope. No installed-product fixture was run.
Surfaces: desktop, remote · Version: First-party sources checked 2026-11-07; pinned implementations retain their cited revision. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-10
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.
15 atomic answers
Code data [partial] Normal events exclude code, prompts and file contents; diagnostic errors may include exception text. Sources: emdash:nov07-telemetry.
Prompts [supported] Normal usage telemetry excludes prompts, messages and command text; diagnostics may include exception text. Sources: emdash:nov07-telemetry.
Credentials [unknown] Credentials: The November first-party documentation and repository pass did not establish data handling and telemetry at the rubric's required scope. No installed-product fixture was run.
Logs [supported] Error events may include exception messages and stack traces for diagnostics. Sources: emdash:nov07-telemetry.
Artifacts [unknown] Artifacts: The November first-party documentation and repository pass did not establish data handling and telemetry at the rubric's required scope. No installed-product fixture was run.
Retention [unknown] Retention: The November first-party documentation and repository pass did not establish data handling and telemetry at the rubric's required scope. No installed-product fixture was run.
Deletion [unknown] Deletion: The November first-party documentation and repository pass did not establish data handling and telemetry at the rubric's required scope. No installed-product fixture was run.
Training [unknown] Training: The November first-party documentation and repository pass did not establish data handling and telemetry at the rubric's required scope. No installed-product fixture was run.
Residency [unknown] Residency: The November first-party documentation and repository pass did not establish data handling and telemetry at the rubric's required scope. No installed-product fixture was run.
Subprocessors [partial] PostHog is named for analytics; a complete subprocessor list is not established. Sources: emdash:nov07-telemetry.
Telemetry disclosure [supported] PostHog and allowlisted usage/error events. Sources: emdash:nov07-telemetry.
Telemetry defaults [supported] Enabled in production by default. Sources: emdash:nov07-telemetry.
Telemetry controls [supported] Settings toggle or TELEMETRY_ENABLED=false. Sources: emdash:nov07-telemetry.
Consent prompt [unknown] Consent prompt: The November first-party documentation and repository pass did not establish data handling and telemetry at the rubric's required scope. No installed-product fixture was run.
Provider separation [supported] Agent provider data handling is separate. Sources: emdash:nov07-readme.
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.
Scope
Surfaces: desktop, remote · Version: a2bdb78f7a619ac87c1c4f86c18570f5fcffae10; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-10 (12 days old)
Agent cross-check
2026-11-22
Classic provider-key authentication does not establish current hosted Emdash 2.0 commercial plans.
12 atomic answers
Currency [unknown] Not stated in the sources checked (homepage, docs, /pricing (404), README, LICENSE.md).
Interval [unknown] Not stated in the sources checked (homepage, docs, /pricing (404), README, LICENSE.md).
Seat minimum [unknown] Not stated in the sources checked (homepage, docs, /pricing (404), README, LICENSE.md).
Workspace fees [unknown] Not stated in the sources checked (homepage, docs, /pricing (404), README, LICENSE.md).
Included usage [unknown] Not stated in the sources checked (homepage, docs, /pricing (404), README, LICENSE.md).
Credits [unknown] Not stated in the sources checked (homepage, docs, /pricing (404), README, LICENSE.md).
Trial [unknown] Not stated in the sources checked (homepage, docs, /pricing (404), README, LICENSE.md).
Overages [unknown] Not stated in the sources checked (homepage, docs, /pricing (404), README, LICENSE.md).
Taxes [unknown] Not stated in the sources checked (homepage, docs, /pricing (404), README, LICENSE.md).
Model cost [supported] User-provided agent credentials include native subscriptions and an ANTHROPIC_API_KEY route; API usage is billed by the provider. Sources: emdash:gap37-claude-api-auth, emdash:homepage-nov10.
Classic itself costs nothing; agent subscriptions or API usage and machine costs are external and not modeled by Emdash.
Scope
Surfaces: desktop, remote · Version: Emdash Classic v1.2.13 (17f32be, 2026-11-19); docs retrieved 2026-11-21 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-22
Documentation and pinned-source inspection only; no installed-product scenario was run.
11 atomic answers
One person [unknown] One person: The November first-party documentation and repository pass did not establish scenario cost and controls at the rubric's required scope. No installed-product fixture was run.
Two people [unknown] Two people: The November first-party documentation and repository pass did not establish scenario cost and controls at the rubric's required scope. No installed-product fixture was run.
Five people [unknown] Five people: The November first-party documentation and repository pass did not establish scenario cost and controls at the rubric's required scope. No installed-product fixture was run.
Task assumptions [unknown] Task assumptions: The November first-party documentation and repository pass did not establish scenario cost and controls at the rubric's required scope. No installed-product fixture was run.
Concurrency [unknown] Concurrency: The November first-party documentation and repository pass did not establish scenario cost and controls at the rubric's required scope. No installed-product fixture was run.
Tokens [unknown] Tokens: The November first-party documentation and repository pass did not establish scenario cost and controls at the rubric's required scope. No installed-product fixture was run.
Compute hours [unknown] Compute hours: The November first-party documentation and repository pass did not establish scenario cost and controls at the rubric's required scope. No installed-product fixture was run.
Variable cost [unknown] Variable cost: The November first-party documentation and repository pass did not establish scenario cost and controls at the rubric's required scope. No installed-product fixture was run.
Included cost [unknown] Included cost: The November first-party documentation and repository pass did not establish scenario cost and controls at the rubric's required scope. No installed-product fixture was run.
Unknown cost [partial] Agent subscription or API costs and SSH machine costs are paid to third parties and not estimated by Emdash. Sources: emdash:b06-providers, emdash:b06-remote.
These docs cover shipped Classic; Emdash 2.0 is described as early-access/waitlist separately. The desktop was renamed Emdash Classic on 2026-11-05 and keeps getting fixes; releases continued through v1.2.13.
Scope
Surfaces: desktop · Version: First-party documentation/source checked 2026-11-07; exact pinned source revision is recorded in each citation. No installed-product fixture.; Emdash Classic v1.2.13 (17f32be, 2026-11-19) for backfilled atoms · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Only the named atomic facts are established by documentation. Remaining rubric scenarios and unknown answers were not demonstrated.
8 atomic answers
Release stage [supported] Documentation labels the scope Emdash Classic, with Emdash 2.0 docs coming at launch. Sources: emdash:nov07-roadmap.
Access restrictions [supported] Classic is downloadable; 2.0 early access is a separate waitlist and not counted as released cloud capability. Sources: emdash:nov07-roadmap.
Support [supported] Roadmap directs users to GitHub discussions, enhancement issues and Discord. Sources: emdash:nov07-roadmap.
Response commitments [unknown] Response commitments: The November first-party documentation and repository pass did not establish availability and support at the rubric's required scope. No installed-product fixture was run.
Status history [unknown] Status history: The November first-party documentation and repository pass did not establish availability and support at the rubric's required scope. No installed-product fixture was run.
Deprecation [partial] Renamed Emdash Classic on 2026-11-05 while Emdash 2.0 is built; it stays open source and keeps getting fixes. No end date is announced. Sources: emdash:b06-blog-next.
Export options [unknown] Export options: The November first-party documentation and repository pass did not establish availability and support at the rubric's required scope. No installed-product fixture was run.
Trial [unknown] Trial: The November first-party documentation and repository pass did not establish useful free tier and evaluation access at the rubric's required scope. No installed-product fixture was run.
Credits trial [unknown] Credits trial: The November first-party documentation and repository pass did not establish useful free tier and evaluation access at the rubric's required scope. No installed-product fixture was run.
Self host cost [partial] User supplies agents and remote machines. Their costs are not zeroed. Sources: emdash:nov07-readme.
Paid only [unknown] Paid only: The November first-party documentation and repository pass did not establish useful free tier and evaluation access at the rubric's required scope. No installed-product fixture was run.
Early access [supported] Emdash 2.0 is early access with a work-email waitlist; v1.2.11 added in-app waitlist signup. Sources: emdash:b06-blog-next, emdash:b06-rel-1211.
Free scenarios [partial] Local and SSH remote work with the user's own agent subscriptions is free in Classic; Emdash 2.0, the team product, is early access without published pricing. Sources: emdash:b06-installation, emdash:b06-remote, emdash:b06-blog-next.
Card required [supported] No account, sign-in or card is needed for local use. Sources: emdash:b06-installation.
Usage caps [unknown] Usage caps: The November first-party documentation and repository pass did not establish useful free tier and evaluation access at the rubric's required scope. No installed-product fixture was run.
Paid evaluation [unknown] Paid evaluation: The November first-party documentation and repository pass did not establish useful free tier and evaluation access at the rubric's required scope. No installed-product fixture was run.
Classic is free with no resale of compute or model usage; Emdash 2.0 pricing is not published.
Scope
Surfaces: desktop, remote · Version: Emdash Classic v1.2.13 (17f32be, 2026-11-19); docs retrieved 2026-11-21 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-22
Documentation and pinned-source inspection only; no installed-product scenario was run.
9 atomic answers
Units [unknown] Units: The November first-party documentation and repository pass did not establish pricing transparency at the rubric's required scope. No installed-product fixture was run.
Included limits [unknown] Included limits: The November first-party documentation and repository pass did not establish pricing transparency at the rubric's required scope. No installed-product fixture was run.
Overages [unknown] Overages: The November first-party documentation and repository pass did not establish pricing transparency at the rubric's required scope. No installed-product fixture was run.
Model markup [supported] None: agents bill through their own provider accounts and Emdash sells no model usage. Sources: emdash:b06-providers, emdash:b06-no-billing.
Minimum commitment [unknown] Minimum commitment: The November first-party documentation and repository pass did not establish pricing transparency at the rubric's required scope. No installed-product fixture was run.
Cancellation [unknown] Cancellation: The November first-party documentation and repository pass did not establish pricing transparency at the rubric's required scope. No installed-product fixture was run.
Sales only unknowns [unknown] Sales only unknowns: The November first-party documentation and repository pass did not establish pricing transparency at the rubric's required scope. No installed-product fixture was run.
Transparency classification [partial] Classic is transparent (free, no billing). Emdash 2.0 has no published pricing. Sources: emdash:b06-installation, emdash:b06-blog-next.
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.
Kind
documented
Locator
Overview, setup, features and component boundaries
Names 35 detected CLI integrations, with provider-specific hooks, resume and model/effort options; remote CLIs must be installed and authenticated remotely.
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.
Kind
source-inspected
Locator
App database; packages/core/src runtime manifests and API schemas; apps/emdash-desktop/src/main; packages/plugins/src/agents/registry.ts
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.
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 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.
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.
Kind
documented
Locator
Supported Providers, Remote agents and Adding a Provider sections (last updated 2026-10-17)
35 detected agent CLIs. Resume, hooks (working, awaiting input, done) and auto-approve are each supported by a listed subset of providers. Some provider CLIs require account authentication or product access before Emdash can run them. Remote agents must be installed and authenticated on the remote host; preferences are remembered per agent and machine; Chat UI or TUI is chosen in the agent selector.
Emdash runs agents through their official CLIs. Users add a local project, clone a GitHub repository or connect a remote machine. Emdash works locally without signing in or connecting GitHub; GitHub and tracker integrations are optional.
Multiple GitHub accounts can be connected (Emdash account/OAuth, GitHub CLI import or device flow) and each project selects one for issues, pull requests (create, list, merge), checks and repository creation. Agent git credentials can use that account, system credentials or none.
No purchase, billing or credit-sale code exists in the Classic desktop or Workspace Server; credit matches are wire flow control and an MCP catalog description.
Kind
source-inspected
Locator
search of apps/ and packages/ for stripe, checkout, purchase, billing and credits
The Emdash UI stays on the laptop; repositories, worktrees, agents, terminals, lifecycle scripts, search and scheduled automations run on the SSH machine through the Workspace Server. Agent CLIs and credentials must be installed and authenticated on that machine. A banner advertises Emdash 2.0 early access.
The System tab shows connection, resource usage and dependencies and installs, starts, restarts, shuts down or updates the Workspace Server. A Conversations tab lists agent sessions on the machine. Subscription readings are in Settings, Usage. Closing the desktop does not stop remote automations.
Kind
documented
Locator
System; Workspaces and conversations; Agents, MCP and skills; Automations
Remote projects can pick, clone or create a GitHub repository. Tasks use a new worktree, existing workspace or repository root; tasks in the same directory share files. Local files and pasted images are uploaded into remote terminals; chat attachments are stored on the target machine. Tmux keeps processes across disconnects but not a reboot.
Kind
documented
Locator
Open a project; Create a task; Agents, files and tools; Previews and reconnects
Add a machine in Settings, Machines with an SSH alias or host details (password, key or agent auth), test it, then install or start the Workspace Runtime from the System tab and add a remote project. Hosts need SSH, Git and the development tools.
v1.2.10: long workspace operations no longer fail after 30 seconds; credential tokens and environment values stay out of process arguments. v1.2.9 adds GitLab repository creation and merge request workflows. Retrieved 2026-11-21, the page's newest entry is v1.2.10.
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.
Tasks can be created from Linear, Asana, Monday.com, Trello, GitHub, Jira, GitLab, Plane, Forgejo, Featurebase, Plain or Notion issues. The linked issue stays attached and inserted context includes provider, identifier, title, URL, description, status, assignees and project; the generated context can be reviewed or edited before sending. Trackers connect with personal API keys or tokens; GitHub uses the project's GitHub account.
Kind
documented
Locator
Create from an Issue; Supported Trackers; Connecting Your Tracker
MCP servers are added from a 54-server catalog (including Context7 and Exa) or as custom stdio/http servers, with required credentials entered in the modal, and synced into each selected agent's native config. Remove deletes a server from all agents.
Kind
documented
Locator
Adding a Server from the Catalog; Editing and Removing; Catalog Servers
The Workspace Server daemon lives in apps/workspace-server of the same repository, declares Apache-2.0 and has no separate license file; the root LICENSE.md is Apache-2.0 (General Action, Inc.).
Issue providers implement listIssues, searchIssues and optional getIssue only; a bounded search of the provider implementations found no create, update, comment, transition or POST/PATCH/PUT calls.
A task starts from a branch, issue or pull request with a name (or generated name) and a provider; no preset is required. By default each task gets its own git worktree and branch; worktrees can be disabled or an existing workspace used. Saved conversations and running processes have different lifetimes; tmux keeps terminal and TUI-agent sessions.
Tmux keeps terminal and TUI-agent processes and history on the host across closed views or lost SSH, but not through a host reboot or explicit termination. Chat UI history and provider resume are separate.
The Pull Requests section shows PR files, commits, checks, comments and merge state for the task branch. Commit offers Commit, Commit & Push or Commit & Create PR; the footer shows fetch, pull, push and publish actions.
The file editor offers syntax highlighting, find/replace, tabs and language intelligence (definitions, references, diagnostics) in local and SSH workspaces.
The app search index holds projects, tasks (with branch) and conversations, updated on create, rename, archive and delete; archived tasks leave the index.
Archiving sets archivedAt and reaps the task's tmux session and agent process while keeping the worktree and session id; restoreTask clears archivedAt so the task can resume.
Automations run an agent prompt on a cron schedule in a project's new worktree, existing workspace or repository root. For remote projects the Workspace Server owns scheduling and execution and the desktop need not stay connected; a stopped machine cannot run. Run history shows timing, status and errors.
Agent status is idle, working, awaiting-input, error or completed; permission, idle and elicitation hook notifications count as attention and drive needs-attention sounds and notifications.
Kind
source-inspected
Locator
AgentStatus line 3; ATTENTION_NOTIFICATION_TYPES lines 11-20
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.
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.
Settings are stored per host and provider: Chat UI (ACP) keeps the provider's own option values; TUI (PTY) keeps an autoApprove flag that defaults to false.
Per-project GitHub account, worktree directory, remotes, tmux, agent git credentials, environment variables, preserve patterns (copy .env-style files into new tasks), shell setup and prepare/setup/run/teardown scripts. Scripts, preserve patterns and shell setup can be shared through .emdash.json; for remote projects they run on the remote machine. Env vars are personal settings; credentials should not go in a committed .emdash.json. Run script logs show in the terminal drawer; EMDASH_PORT and a Docker Compose example support services.
Kind
documented
Locator
What you can configure; Share settings with your team; Project environment variables; Lifecycle scripts
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.
An in-app browser previews task dev servers. Remote previews forward the remote port to the laptop automatically or through Forward Port with an optional local port; no tunnel lifetime or access control is documented.
Default shortcuts such as Cmd+N create task, Cmd+J terminal drawer, Cmd+Shift+B browser and Cmd+Shift+1 changes panel; most can be rebound in Settings.
Each conversation in a task has its own providerId, pty or acp transport, session id, model, agentStatus and agentStatusSeen flag, so a task can hold conversations with different agents.
For GitHub PRs that are blocked, behind or waiting on checks, Emdash offers merging only after ticking 'Merge without waiting for requirements to be met (bypass rules)'; GitLab gets no bypass. Whether the bypass succeeds is decided by the Git host. A bounded search of source-control, github and agent/issue plugin code for deployment found no deployment status tracking.
Kind
source-inspected
Locator
canBypass line 27; BLOCKED and pending-check states; merge-footer.tsx bypass checkbox
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.
Kind
documented
Locator
Hero and 'All your coding agents in one place'; 'Get early access' form
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.
Kind
source-inspected
Locator
claudeAuthStatus: ANTHROPIC_API_KEY detection before native auth status
Emdash 2.0 (coding agents for whole teams) is in early access with a work-email waitlist. The current desktop app is renamed Emdash Classic; it stays open source and keeps getting fixes. No end date is given.
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.