Emdash vs Honker

Emdash is a desktop application from Y Combinator's W26 batch that lets developers run multiple AI coding agents simultaneously, each isolated in its own Git worktree. Rather than switching between Claude Code for one task and Codex for another, you launch parallel agents from one interface, review their diffs in one place, and merge the results through a queue that handles the Git complexity automatically. It supports 23 CLI agent providers including Claude Code, Qwen Code, Hermes Agent, Amp, and OpenAI Codex. The remote development story is particularly strong: Emdash connects to remote machines via SSH/SFTP with keychain credential storage, meaning you can run GPU-heavy agents on a beefy remote devbox while managing everything from your laptop. Ticket integration with Linear, GitHub, and Jira means you can drag a ticket directly onto an agent and watch it work — no copy-pasting requirements into a chat window. Built with Electron and TypeScript with SQLite for local storage, Emdash is local-first by design — your code never touches Emdash's servers, only your chosen agent providers. The project is MIT-licensed, open source, and has accumulated 3,700+ commits since its YC batch. At the intersection of the multi-agent workflow boom and the need for developer tooling that actually scales to parallel workstreams, Emdash is one of the more credible attempts at solving a real daily pain.

Honker is a Rust-built SQLite extension that brings Postgres-style NOTIFY/LISTEN semantics to SQLite without any external broker. It adds cross-process notifications, durable pub/sub channels, task queues with retries and priority, and crontab-style scheduling — all living inside your existing SQLite file. Single-digit millisecond delivery via WAL-file watching instead of polling. The core trick: rather than polling the database on an interval, Honker watches SQLite's Write-Ahead Log (WAL) file with stat(2) calls. When a write lands, listeners wake up immediately. This gives push semantics without Redis, RabbitMQ, or any additional infrastructure. Business logic writes and task enqueues are atomic because they're in the same database. Honker ships as a loadable SQLite extension plus language packages for Python, Node.js, Rust, Go, Ruby, Bun, Elixir, and C++. It's experimental and the API may change, but it's addressing a real pain point: SQLite projects that outgrow simple reads/writes inevitably reach for external messaging, and Honker defers that moment significantly.