CodeDen
A local-first harness for coding agents. Run Claude Code, Codex, OpenCode, Cursor and Gemini CLI side by side in a calm, focused workspace, and when you're ready, let a small software factory work through your backlog while every step stays visible in GitHub.
npx codeden
That's the whole install. CodeDen starts a local server, opens your browser on an already signed-in URL, and reuses the Claude Code, Codex, OpenCode, Cursor, Gemini CLI, GitHub and git setup you already have. No accounts, no license keys, no hosted backend, no telemetry.
Prefer an app? Download the desktop app for Windows, macOS or Linux: the same CodeDen in its own window, with a tray icon, notifications and automatic updates, and no Node.js needed. See The desktop app.
Contents
Quick start
Requirements
| |
|---|
| Node.js 24+ | node --version |
| git | with user.name and user.email set |
| An agent CLI, signed in | Claude Code (claude), Codex CLI (codex), OpenCode 2.2+ (opencode), the Cursor CLI (agent) and/or Gemini CLI 0.68+ (gemini). At least one is required |
| GitHub CLI (optional) | gh auth login unlocks issues, pull requests, evidence and the factory. Local-only folders work without it |
| Edge or Chrome (optional) | for the browser panel and the agents' browser tools |
Run it
npx codeden # or: npm i -g codeden && codeden
Or install the desktop app from the latest release (CodeDen-Setup-<version>.exe on Windows, a .dmg on macOS, an AppImage or .deb on Linux). It needs no Node.js, uses the same data as npx codeden (~/.codeden), lives in the tray and updates itself. Builds without a publisher signature show a warning the first time you open them: on Windows choose More info › Run anyway; on macOS open CodeDen once, then choose Open Anyway under System Settings › Privacy & Security. If macOS says the app is "damaged", see Unsigned builds.
- The setup checklist detects Claude Code, Codex, OpenCode, Cursor, Gemini CLI, GitHub, your git identity and a browser, and only asks about what's missing. Each failed check has one fix: an install command, or a Sign in button that runs the tool's own login in an embedded terminal.
- Add a project: pick a local folder (a server-side folder picker) or paste a GitHub URL to clone.
- Start a session. The agent works in its own git worktree and branch, so your checkout is never touched.
Already installed something and want to check it? npx codeden doctor runs the same checks in the terminal. See Getting started for a full walkthrough.
What you get
Orchestrator, project managers and agent sessions
Three kinds of agents, each in its own lane:
- Orchestrator. One agent you talk to across every project. It creates and configures projects, hands work to project managers and summarises what's going on.
- Project managers (PMs). One long-lived agent per project. It triages issues, starts and steers agent sessions, follows their progress and escalates to you when it's unsure. PMs and the orchestrator are read-only: they never edit your code, they act through CodeDen's tools.
- Agent sessions. The coding agents. Each runs in its own worktree and branch, can ask you questions, request approvals, share screenshots, and finish by opening a pull request with evidence.
Every unit of work carries a work key (issue:142, automation:security-audit, ...), so starting something that's already running gives you a conflict card (wait, skip, join or force) instead of a silent duplicate. The orchestrator and PMs get a fresh status digest every time they wake, and session events reach them as typed notices. More on orchestration.
One inbox
Questions, approvals, PRs ready for review, failed runs, triage decisions, duplicate-work conflicts and budget alerts all land in one Inbox, each linked to its session, issue and PR and answerable in place. Toasts and (opt-in) browser notifications tell you when something new arrives, and when an agent is blocked on you a chime, a sticky toast and an amber dot on the tab icon make sure you notice.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
