codeden 0.1.0 → 0.1.1

package/README.md

@@ -29,6 +29,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)
@@ -196,6 +197,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 +218,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 +236,19 @@ 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`).
+
 ## FAQ
 
 **Do I need API keys?**