Is Okto Nexus a replacement for Emdash, or something you would run alongside it?

Alongside. Emdash handles where agents run and how files stay separate, across more agents and platforms than most competitors. Nexus handles who owns the work, who verified it, and who approved it, none of which Emdash tracks.

Does Okto Nexus run on the same agents as Emdash?

Largely yes. Nexus's dashboard generates MCP connection snippets for Claude Code, Claude Desktop, Codex, Cursor, VS Code, Windsurf, and Cline. Since Nexus coordinates over MCP rather than shipping its own integrations, it works with any MCP-compatible agent without adding each one individually.

Is Okto Nexus open source like Emdash?

Not quite. Emdash is fully open source under Apache 2.0, with no restriction on reselling it as a hosted service. Nexus is source available under the Elastic License 2.0 with an addendum restricting hosted, multi tenant, or white label resale. Emdash's license is the more permissive of the two.

Does Nexus give me Emdash's diff viewer, in-app browser, or issue tracker integration?

No, and it's not trying to. Nexus tracks identity, ownership, verification, memory, and approvals. For running agents, reviewing diffs, or pulling in tickets, Emdash or your existing dev tools is still what you'd use.

Which one costs more to run?

Both are free at the core. Nexus has no paid tier at all, by design. Emdash's desktop app is free and open source; Cloud and Enterprise are contact-sales with no published pricing.

OVERVIEW · OKTO NEXUS VS EMDASH

Okto Nexus Source available · Elastic License 2.0 · Local-first · Free to run · Cross platform Emdash Open source · Apache 2.0 · Local-first · Free core · macOS, Windows, Linux

Okto Nexus vs. EmdashEmdash isolates more agents, on more platforms, for free. It still can't tell you which one owns what

Git worktrees stop agents from overwriting each other's files, across more agents and platforms than most. They still don't stop duplicate work or an unapproved risky action. Okto Nexus covers that: identity, ownership, verification, and approval gates.

Install Okto Nexus See how it works View on GitHub ↗

0: MCP tools (46 w/ memory)
0: Database tables
0: Opt-in feature flags
0: Cloud accounts required

Emdash

Open source (Apache 2.0) desktop app from General Action Inc. Runs coding agents in parallel, each in its own isolated git worktree, across 34 supported CLI agent providers.

Own branch, terminal, conversation, and review state per task
Local or remote via SSH; separate paid Cloud tier for ephemeral compute
Automations schedule recurring agent runs on a cron trigger
Native issue integration: Linear, Jira, GitHub, GitLab, Asana, and more
No agent identity, messaging, or cross-session memory
Native builds for macOS, Windows, and Linux

Okto Nexus

Local first coordination hub. Installs with pip, runs as a local hub every agent connects to over MCP.

Durable identity, presence, and inbox per agent
Atomic handoff_claim: one winner, no duplicate work
Separate verifier role, executor can't self-verify
Policies and human in the loop approval gates
Opt-in memory + immutable, replayable event log
43 MCP tools by default (46 with memory), 34 tables

> pip install "okto-nexus[serve]"

Emdash makes sure agents can't overwrite each other's files, across more agents and platforms than most tools in the category. Nexus makes sure they know who owns what, someone independent checked it, a human signed off on anything risky, and it's all on the record.

How each workflow actually moves

Emdash · task lifecycle

01New task

02Isolated worktree

03Runs & diff

04Review & CI

05Merge

Okto Nexus · real MCP tool calls

handoff_create()handoff_claim()memory_put()memory_search()handoff_complete()

Verifier gate

separate from the executor

VERIFYING

acceptance_criteria attached set · required

executor verifying its own result barred

verdict from a separate agent required to advance

status: a failed verdict returns the handoff with recorded feedback

Governance policy actions

versioned · plus byte limits

Deny

Blocked

The call never executes at all.

Quota

Capped

A ceiling enforced per agent or scope.

Max open handoffs

Limited

Caps how much work one agent can hold at once.

Require approval

Paused

Execution waits for a human decision.

agent claims → handoff (atomic, single winner)

handoff verified_by → validator (never the executor)

handoff depends_on → handoff (blocked until complete)

action requires_approval → human (paused until a decision)

Emdash · diff view & CI checks

# before merge

> diff view + CI/CD checks

diff review / CI checkssurfaced, not enforced

mergeunblocked, human choice only

Nothing stops the merge if the check is skipped.

Okto Nexus · require_approval policy

# sensitive action requested

> handoff_create(...) · policy-gated

require_approval policyintercepted

human decisionmust approve or reject first

The action does not execute until a person says yes.

Capability	Okto Nexus	Emdash
Coordination & governance
Agent to agent coordination	Native Durable identities + 7 routing strategies (direct, capability, role, tag, broadcast, mixed, fallback).	Not supported Agents in separate worktrees can't message each other; the human switches tabs.
Single owner task claims	Native `handoff_create` + atomic `handoff_claim`: exactly one winner.	Not supported A human creates each task manually; duplicate starts are possible.
Verification and separation of duties	Native Completed work enters `VERIFYING`; executor barred from self-verify.	Not supported Diff review and CI checks are real, but the reviewer isn't enforced as separate.
Task dependencies	Native (opt in) `depends_on` blocks claiming until the dependency completes.	Not supported No dependency concept; sequencing across tasks is manual.
Governance and human approval	Native Versioned policies (deny, quota, limits, `require_approval`) + guardrails + human-in-the-loop queue.	Not supported No policy layer sits between an agent and its next action.
Durable cross-session memory	Native (opt in) `memory_put` / `memory_get` / semantic `memory_search` across sessions.	Not supported History persists per task; no cross-task or cross-session recall.
Communication standardization	Native Versioned presets set tone, structure, and verbosity per role.	Not supported Each agent talks however its own model defaults to.
Audit trail and replay	Native Immutable, monotonic event log; CLI NDJSON replay export.	Partial Automation and git history record what ran, no coordination-level decisions tracked.
Presence and session tracking	Native Heartbeat-based presence within a configurable window.	Partial A task shows running or idle; no explicit agent presence model.
Observability dashboard	Native Agent graph, message threads, 6-column handoff Kanban, event timeline, health metrics.	Partial Per-task terminal, diff, and conversation view; no coordination-state dashboard.
Deployment, pricing & license
Platform support	Cross platform Anywhere Python 3.11+ runs.	Cross platform Native desktop builds for macOS, Windows, and Linux.
Core pricing	Free today No published paid tier.	Free core Cloud and Enterprise are contact-sales, no public pricing.
License	Source available Elastic License 2.0 + addendum; no hosted/multi tenant resale.	Open source Apache 2.0, no equivalent resale restriction.
Extensibility	Native 7 opt-in feature flags + 12 versioned MCP reference resources.	Native 34 supported CLI agent providers + a reusable prompt/skill Library.
Enterprise readiness	Partial Policies, guardrails, and audit log exist; built for single tenant use.	Partial An Enterprise offering exists, but it's contact-sales with no published SLA.

Emdash's supported-agent count varies by source; 34 per its own docs page is used here. Nexus's numbers are pinned to release 0.1.4. Reconfirm both before publishing.

Reach for Emdash when

The problem is spatial

Several agents touch the same codebase at once and you want the strongest free option: more providers, more platforms, native ticket integration. Its open license makes it an easy first install.

Reach for Okto Nexus once

File collisions stop being the problem

Duplicate fixes, unverified results, unapproved risk, or lost decisions start showing up. Emdash's breadth doesn't change that: it was never built to see across worktrees, only inside one.

Using both is reasonable

Not a compromise

Isolate execution with Emdash's worktrees; let Nexus own identity, verification, and approval on top. No official integration exists today.

Two agents fixing the same bug

Neither could see the other already claimed it. handoff_claim's atomic claim catches it first.

Marking its own work "done"

Diff review and CI checks are real, but nobody independent checked them. The VERIFYING state requires a separate verifier.

A risky action, unaware

A deploy or write executes with no human aware. Human-in-the-loop approval pauses it first.

A decision nobody can find

Made two tasks ago, now untraceable once that history scrolls out of view. Durable memory and the event log keep it retrievable.

Q1

Is Okto Nexus a replacement for Emdash, or something you would run alongside it?

Alongside. Emdash handles where agents run and how files stay separate, across more agents and platforms than most competitors. Nexus handles who owns the work, who verified it, and who approved it, none of which Emdash tracks.
Q2

Does Okto Nexus run on the same agents as Emdash?

Largely yes. Nexus's dashboard generates MCP connection snippets for Claude Code, Claude Desktop, Codex, Cursor, VS Code, Windsurf, and Cline. Since Nexus coordinates over MCP rather than shipping its own integrations, it works with any MCP-compatible agent without adding each one individually.
Q3

Is Okto Nexus open source like Emdash?

Not quite. Emdash is fully open source under Apache 2.0, with no restriction on reselling it as a hosted service. Nexus is source available under the Elastic License 2.0 with an addendum restricting hosted, multi tenant, or white label resale. Emdash's license is the more permissive of the two.
Q4

Does Nexus give me Emdash's diff viewer, in-app browser, or issue tracker integration?

No, and it's not trying to. Nexus tracks identity, ownership, verification, memory, and approvals. For running agents, reviewing diffs, or pulling in tickets, Emdash or your existing dev tools is still what you'd use.
Q5

Which one costs more to run?

Both are free at the core. Nexus has no paid tier at all, by design. Emdash's desktop app is free and open source; Cloud and Enterprise are contact-sales with no published pricing.

More agents in more worktrees still doesn't answer who owns what

Free to run locally, no account required, works with the coding agent you already have.

Install Okto Nexus Read the docs ↗

Emdash and General Action Inc. are trademarks of their owner, referenced here for comparison only. No affiliation with or endorsement by General Action Inc. is implied.