Emdash vs Karpathy Skills

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.

Karpathy Skills is a CLAUDE.md plugin distilled from Andrej Karpathy's public observations on LLM coding pitfalls. Drop the single file into your project root (or install it as a Claude Code skill) and every Claude Code session starts pre-loaded with the four principles Karpathy identified as most commonly violated: think before writing, prefer simplicity, make only targeted changes, and close loops with explicit verification. The project has accumulated 1,450+ GitHub stars in under two weeks. The implementation is intentionally minimal — it's a structured system prompt, not a framework. Each principle is spelled out with concrete anti-patterns to avoid: no premature generation, no over-engineering simple tasks, no cascading refactors when a surgical fix suffices, no ending a session without verifying the goal was actually met. It's Karpathy's "Software 2.0" thinking applied to the agent workflow meta-layer. What makes this compelling isn't the technology — it's the curation. Karpathy has spent more time thinking about LLM behavior patterns than almost anyone outside the major labs. Packaging that into something installable in 30 seconds lowers the floor for teams who want more reliable agent outputs without extensive prompt engineering work.