codeden 0.1.0 → 0.2.0

package/README.md

@@ -19,6 +19,8 @@ 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, GitHub and git setup you already have. No accounts, no license keys, no hosted backend, no telemetry.
 
+Prefer an app? **[Download the desktop app](https://github.com/leonvanzyl/codeden/releases/latest)** 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](https://github.com/leonvanzyl/codeden/blob/main/docs/desktop.md).
+
 ---
 
 ## Contents
@@ -29,6 +31,7 @@ That's the whole install. CodeDen starts a local server, opens your browser on a
 - [Security model](#security-model)
 - [Configuration](#configuration)
 - [CLI reference](#cli-reference)
+- [Updating](#updating)
 - [FAQ](#faq)
 - [Documentation](#documentation)
 - [Contributing](#contributing) · [License](#license)
@@ -51,6 +54,8 @@ That's the whole install. CodeDen starts a local server, opens your browser on a
 npx codeden            # or: npm i -g codeden && codeden
 ```
 
+Or install the **desktop app** from the [latest release](https://github.com/leonvanzyl/codeden/releases/latest) (`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. Unsigned builds show a SmartScreen or Gatekeeper warning the first time; see [The desktop app](https://github.com/leonvanzyl/codeden/blob/main/docs/desktop.md).
+
 1. The **setup checklist** detects Claude Code, Codex, 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.
 2. **Add a project:** pick a local folder (a server-side folder picker) or paste a GitHub URL to clone.
 3. **Start a session.** The agent works in its own git worktree and branch, so your checkout is never touched.
@@ -75,7 +80,7 @@ Every unit of work carries a **work key** (`issue:142`, `automation:security-aud
 
 ### 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.
+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.
 
 ![The inbox with a conflict, an approval and a PR ready for review](https://raw.githubusercontent.com/leonvanzyl/codeden/main/docs/images/inbox.png)
 
@@ -196,6 +201,9 @@ Inside the data directory:
   orchestrator/         the orchestrator's working directory
   backups/              copies of config files taken before CodeDen overwrote them
   logs/runner.log       runner output
+  deps/                 Claude Code support, installed on demand
+  app/<version>/        CodeDen versions installed by one-click updates
+  app/current.json      which installed version `codeden` starts
 ```
 
 Two copies can run side by side with different homes and ports, for example `codeden --home ~/.codeden-test --port 4400`.
@@ -214,6 +222,7 @@ A minimal `.codeden/project.json`:
 ```
 codeden [options]      Start CodeDen and open it in the browser
 codeden doctor         Check the installation (--install: add Claude Code support now)
+codeden update         Install the latest version and switch to it (--rollback: go back)
 codeden stop           Stop the server and the runner
 
 Options:
@@ -231,6 +240,20 @@ Options:
 
 Environment variables: `CODEDEN_HOME` (data directory), `CODEDEN_DEBUG=1` (server log lines in the terminal), `CODEDEN_SHELL` (terminal shell; PowerShell on Windows, `$SHELL` elsewhere), `CODEDEN_GITHUB_SYNC=0` (turn GitHub polling off).
 
+## Updating
+
+CodeDen checks npm for a new version when it starts and every 6 hours (only the package name is sent; turn it off under **Settings > General > Updates**). When one is out, a banner says so: **What's new** shows the release notes, **Update now** installs it and restarts CodeDen, and the page reconnects on its own. Running agents are drained and resumed, the same as after any runner restart.
+
+- **How it works.** New versions install side by side into `~/.codeden/app/<version>/`, and `~/.codeden/app/current.json` names the one to run. Whatever `codeden` you start (`npx codeden`, a global install) checks that file first and runs the newer installed version in its place, so there's nothing to reinstall by hand. The previous version is kept for rollback.
+- **Install automatically.** Set **Updates** to *Install automatically* to download new versions in the background; they start the next time you open CodeDen (or right away with **Restart now**).
+- **From the terminal.** `codeden update` does the same as the button (and restarts a running CodeDen); `codeden update --rollback` goes back to the previous version. `codeden doctor` lists the installed versions and which one starts.
+- **Roll back** from **Settings > About** as well.
+- **If it can't restart itself** (for example when started some other way), the banner says "Update installed, restart CodeDen to finish" with the command to run.
+- **Running from source** (a clone of this repository) never switches versions: pull and rebuild (`git pull && pnpm install && pnpm build`).
+- **The old way still works:** `npm i -g codeden@latest`, or `npx codeden@latest`. A globally installed version newer than the side-by-side one always wins.
+- **Upgrading from 0.1.0:** 0.1.0 predates one-click updates; update it once by hand (`npm i -g codeden@latest` or `npx codeden@latest`).
+- **The desktop app** updates itself from GitHub Releases with the same banner and the same setting; see [The desktop app](https://github.com/leonvanzyl/codeden/blob/main/docs/desktop.md#updates).
+
 ## FAQ
 
 **Do I need API keys?**
@@ -262,6 +285,7 @@ It's experimental. Read [Autonomy and the dark factory](https://github.com/leonv
 | Guide | |
 |---|---|
 | [Getting started](https://github.com/leonvanzyl/codeden/blob/main/docs/getting-started.md) | Install, first-run setup, first project and session |
+| [The desktop app](https://github.com/leonvanzyl/codeden/blob/main/docs/desktop.md) | Install, tray, notifications, updates, signing and where data lives |
 | [Orchestration](https://github.com/leonvanzyl/codeden/blob/main/docs/orchestration.md) | Orchestrator, PMs, agents, work keys, conflicts and notices |
 | [GitHub](https://github.com/leonvanzyl/codeden/blob/main/docs/github.md) | Issues, PRs, checks, reviews and the evidence branch |
 | [Automations](https://github.com/leonvanzyl/codeden/blob/main/docs/automations.md) | Triggers, guards, templates and writing your own |