GitHub - code-agents/emdash-x: Emdash X is an experimental fork of Emdash, an orchestration layer for running multiple coding agents in parallel in isolated Jujutsu Worktress

emdash is a cross-platform UI layer for running multiple coding agents in parallel — currently supporting OpenAI Codex CLI, Claude Code CLI, Droid (Factory CLI), Gemini CLI, Cursor CLI, Amp Code CLI, GitHub Copilot CLI, and Charm CLI. Each agent runs in its own Git worktree so you can fan out tasks, keep changes compartmentalized, and manage everything from a single UI.

Emdash supports the widest range of CLI providers

Install

Manual Installation

Either download the package for your platform from Releases (links above), or build and run the app locally — see Requirements and Getting Started below.

Homebrew

Install and manage emdash with Homebrew:

# Install
brew install --cask emdash

# Upgrade
brew upgrade --cask emdash

# Uninstall
brew uninstall --cask emdash

If Homebrew does not find the cask yet, run brew update.

Requirements

Node.js 22.12.0+ and Git
One or more providers (install as needed):
- OpenAI Codex CLI (install + authenticate)
- Optional: Claude Code CLI (install + authenticate)
Optional: GitHub CLI for PRs, badges, and repo info

Codex CLI

Install the Codex CLI and authenticate it:

npm install -g @openai/codex
# or
brew install codex

# authenticate
codex

Claude Code CLI (optional)

Install the Claude Code CLI and authenticate it:

npm install -g @anthropic-ai/claude-code

# start and login
claude
# then use /login inside the CLI

GitHub CLI

Install and authenticate GitHub CLI for GitHub features:

Install GitHub CLI:

macOS: brew install gh
Linux: sudo apt install gh (Ubuntu/Debian) or sudo dnf install gh (Fedora)
Windows: winget install GitHub.cli

Authenticate:

gh auth login

Getting Started

Prerequisites

Node.js 20.0.0+ (recommended: 22.20.0) and Git
Install and authenticate at least one provider (Codex or Claude Code)
(Optional) Install and authenticate GitHub CLI

Development Setup

Clone this repository

git clone https://github.com/generalaction/emdash.git
cd emdash

Use the correct Node.js version

This project uses Node.js 22.20.0. Choose one:

Option A: Using nvm (recommended)
```
nvm use
# or if you don't have v22.20.0 installed:
nvm install
```
Option B: Manual installation
- Download and install Node.js 22.20.0 from nodejs.org
Install and run
```
npm run d
```
This single command installs dependencies, rebuilds native modules, and starts the dev server.

Alternatively, you can run these steps separately:
```
npm install  # Install dependencies
npm run dev  # Start development server
```

Troubleshooting

SIGSEGV / Segmentation Fault on Startup

If you encounter a segmentation fault (SIGSEGV) when running the app, it's caused by native modules (sqlite3, node-pty, keytar) compiled for the wrong Node.js/Electron version. This happens when:

Switching between Node.js versions
Updating Electron
Using a different machine/architecture
Installing packages after changing versions

Quick fix:

npm run rebuild

If that doesn't work, nuclear option:

npm run reset

This removes node_modules and reinstalls everything from scratch.

Usage

In the chat input, use the provider selector to switch between Codex and Claude Code. Once a chat has started with Codex or Claude, the provider is locked for that chat.

Build from Source

macOS

npm run package:mac

Outputs: release/emdash-arm64.dmg and release/emdash-arm64.zip

Linux

Install build dependencies:

# Debian/Ubuntu
sudo apt-get install -y python3 python3-dev build-essential

# Fedora/RHEL
sudo dnf install -y python3 python3-devel gcc gcc-c++ make

# Arch
sudo pacman -S python base-devel

Build the app:

npm run package:linux

Outputs: release/emdash-x64.AppImage and release/emdash-x64.deb

AppImage Usage:

chmod +x emdash-x64.AppImage
./emdash-x64.AppImage

Debian Package:

sudo dpkg -i emdash-x64.deb
emdash  # Run from command line after install

Windows

Install build dependencies (via Chocolatey):

choco install python build-essentials

Or install manually:

Python 3
Visual Studio Build Tools (or Visual Studio with C++ workload)

Build the app:

npm run package:win

Outputs: release/emdash-x64.exe (portable) and release/emdash-x64-installer.exe (NSIS installer)

Cross-Platform Build

To build for all platforms:

npm run build        # Compiles TypeScript and Vite
npm run package      # Builds for current platform

To build for a specific platform on macOS:

npm run package:mac      # macOS
npm run package:linux    # Linux (requires cross-build tools)
npm run package:win      # Windows (requires cross-build tools)

Note: Native modules (sqlite3, node-pty, keytar) require platform-specific compilation. Building for a different platform than your current OS may require additional cross-compilation setup.

Demos

emdash in action

Creating a CONTRIBUTIONS.md file for an open source repository

Running multiple Codex agents in parallel

Monitor and review the work of several agents within emdash

Open a Pull Request from the dashboard

Review diffs, set title/description, choose target branch, and publish to GitHub — all from emdash

Data Persistence

emdash uses SQLite for local data persistence, ensuring your projects and workspaces are maintained across application sessions. All data is stored locally on your machine, providing privacy and offline functionality.

Database Architecture

The application maintains two primary data structures:

Projects Table

Stores information about opened Git repositories and their GitHub integration status:

CREATE TABLE projects (
  id TEXT PRIMARY KEY,
  name TEXT NOT NULL,
  path TEXT NOT NULL UNIQUE,
  git_remote TEXT,
  git_branch TEXT,
  github_repository TEXT,
  github_connected BOOLEAN DEFAULT 0,
  created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
  updated_at DATETIME DEFAULT CURRENT_TIMESTAMP
);

Key Features:

Unique Path Constraint: Prevents duplicate project entries
Git Integration: Tracks remote URLs and current branches
GitHub Status: Monitors connection state with GitHub CLI
Automatic Timestamps: Tracks creation and modification times

Workspaces Table

Manages isolated agent workspaces with their associated Git worktrees:

CREATE TABLE workspaces (
  id TEXT PRIMARY KEY,
  project_id TEXT NOT NULL,
  name TEXT NOT NULL,
  branch TEXT NOT NULL,
  path TEXT NOT NULL,
  status TEXT DEFAULT 'idle',
  agent_id TEXT,
  created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
  updated_at DATETIME DEFAULT CURRENT_TIMESTAMP,
  FOREIGN KEY (project_id) REFERENCES projects (id) ON DELETE CASCADE
);

Key Features:

Cascade Deletion: Removing a project automatically cleans up associated workspaces
Status Tracking: Monitors workspace state (idle, running, completed)
Agent Assignment: Links workspaces to specific agent instances
Branch Management: Tracks Git branch names for each workspace

Data Location

The SQLite database is automatically created in your system's application data directory:

macOS: ~/Library/Application Support/emdash/emdash.db
Windows: %APPDATA%/emdash/emdash.db
Linux: ~/.config/emdash/emdash.db

Database Operations

The application provides a comprehensive set of database operations through the DatabaseService:

Project Management: Save, retrieve, and delete project entries
Workspace Management: Create, update, and remove workspace records
Automatic Initialization: Database and tables are created on first launch
Error Handling: Robust error handling with detailed logging

Storage Usage

The application stores conversation history locally, which may consume disk space over time:

Clearing Local Storage (Reset Database)

If you want to reset or reclaim space, you can delete the app's local database. This removes saved conversations and resets projects/workspaces. The database is recreated automatically on next launch.

Important

Quit the app before deleting the DB to avoid file‑in‑use errors.
Paths with spaces need quotes (e.g. "Application Support").

Default locations (packaged app)

macOS: ~/Library/Application Support/emdash/emdash.db
Windows: %APPDATA%/emdash/emdash.db
Linux: ~/.config/emdash/emdash.db

Development builds (Electron default)

macOS: ~/Library/Application Support/Electron/emdash.db

Note: legacy filenames we migrate from (safe to remove if present): database.sqlite, orcbench.db.

Quick commands (macOS)

# Quit the app first

# Packaged path (if you ran a built app)
rm -f "$HOME/Library/Application Support/emdash/emdash.db" \
      "$HOME/Library/Application Support/emdash/emdash.db-wal" \
      "$HOME/Library/Application Support/emdash/emdash.db-shm"

# Dev path (vite/electron dev)
rm -f "$HOME/Library/Application Support/Electron/emdash.db" \
      "$HOME/Library/Application Support/Electron/emdash.db-wal" \
      "$HOME/Library/Application Support/Electron/emdash.db-shm"

# Optional: remove legacy DB filenames if they exist
rm -f "$HOME/Library/Application Support/emdash/database.sqlite" \
      "$HOME/Library/Application Support/emdash/orcbench.db"
rm -f "$HOME/Library/Application Support/Electron/database.sqlite" \
      "$HOME/Library/Application Support/Electron/orcbench.db"

# One-liner to locate any emdash.db under your home folder (preview only)
find "$HOME" -type f -name 'emdash.db*' -print

What's Next

Additional providers
Workspace lifecycle hooks to run custom scripts on create, run, and archive (e.g., install deps, copy env files, clean up resources)
Planning chat with controlled execution (draft actions in a separate chat, then run them one by one)
Linear integration to track and close out issues
Assign the same prompt to different providers at the same time and compare results

Security & Privacy

We take data security and privacy seriously. See docs/telemetry.md for exact details.
Your code, chats, and repository contents stay local. Emdash does not send your code or chats to us.
Using third-party CLIs (e.g., Codex, Claude, GitHub CLI) may transmit data to those providers per their policies.

Telemetry

By default, Emdash collects basic, anonymous usage statistics via PostHog to understand which features are used and improve stability. This helps us prioritize development and track aggregate adoption. We only send coarse aggregates (e.g., counts/buckets of projects and workspaces) and session duration — never code, paths, or content.
What we collect:
- Lifecycle events (e.g., app start/close), feature usage events (feature name only), and non-identifying context (app version, platform, architecture, Electron version, install source).
- We do not collect code, prompts, repository names, file paths, environment variables, or personally identifiable information.
How we protect your privacy:
- Telemetry is anonymous; a random instance ID is stored locally on your device.
- Autocapture and session replay are disabled; only explicit, allowlisted events are sent.
Opt-out:
- Toggle it off in Settings → General → Privacy & Telemetry, or set TELEMETRY_ENABLED=false before launching the app.
Full details, including the exact list of events and properties: see docs/telemetry.md.

Maintainers

Telemetry configuration (PostHog host and project key) is injected via CI for official builds. Local development does not send telemetry unless you explicitly provide credentials.
Recommended PostHog settings for the project: disable IP capture, autocapture, session replay, and geo‑IP enrichment by default.

Name		Name	Last commit message	Last commit date
Latest commit History 681 Commits
.github		.github
docs		docs
src		src
.eslintrc.json		.eslintrc.json
.gitignore		.gitignore
.node-version		.node-version
.nvmrc		.nvmrc
.prettierignore		.prettierignore
.prettierrc		.prettierrc
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE.md		LICENSE.md
README.md		README.md
components.json		components.json
instructions.md		instructions.md
package-lock.json		package-lock.json
package.json		package.json
postcss.config.js		postcss.config.js
tailwind.config.js		tailwind.config.js
tsconfig.json		tsconfig.json
tsconfig.main.json		tsconfig.main.json
vite.config.ts		vite.config.ts

License

code-agents/emdash-x

Folders and files

Latest commit

History

Repository files navigation

Install

macOS

Linux

Windows

Manual Installation

Homebrew

Requirements

Codex CLI

Claude Code CLI (optional)

GitHub CLI

Getting Started

Prerequisites

Development Setup

Troubleshooting

SIGSEGV / Segmentation Fault on Startup

Usage

Build from Source

macOS

Linux

Windows

Cross-Platform Build

Demos

Data Persistence

Database Architecture

Projects Table

Workspaces Table

Data Location

Database Operations

Storage Usage

Clearing Local Storage (Reset Database)

What's Next

Security & Privacy

Telemetry

About

Resources

License

Contributing

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages