Requires Paseo 0.10.3 to 0.12 (betas included), with plugins enabled (Settings → Plugins), and Claude Code\ninstalled with its native installer on the daemon host.
\nFrom the official Paseo plugin directory, once it is listed there (Paseo 0.11 or later):
\npaseo plugin add tomcrawf90/claude-update\nFrom npm, on any supported Paseo:
\npaseo plugin install npm:paseo-plugin-claude-update\nOr from a checkout of this repository:
\npaseo plugin install /absolute/path/to/paseo-plugin-claude-update\nThen paseo plugin ls should show claude-update as running. The first check happens about 30\nseconds after the plugin starts. A fresh install only tells you when an update is available and\nchanges nothing; turn on Auto-update Claude Code, on the status page or in the\nsettings, to have it update on the schedule.
Where to find it. The sidebar row \"Claude Code updates\" opens the status page. Its first card,\n\"Checks\", says when the plugin last checked, how that ended and when it checks next, and has the\n\"Check now\" button (it only looks) and \"Update now\" (it installs). The same lines and \"Check now\"\nare on the settings screen, under Settings → Plugins → Claude Code updates. The Command Center\n(⌘K) has \"Claude Code updates: open status\", \"Claude Code updates: check now\" and \"Claude Code\nupdates: settings\". The row's title changes only when:
\n| The row reads | \nWhen | \nIt goes back to \"Claude Code updates\" when | \n
|---|---|---|
| Claude up… | \n\n | \n |
claude update follows Claude Code's own channel; this plugin cannot choose a different one for it.autoUpdatesChannel from ~/.claude/settings.json only. Claude Code can also take it from managed settings (on macOS /Library/Application Support/ClaudeCode/managed-settings.json) or a project's .claude/settings.json, which the plugin does not read, so with one of those set claude update may follow a channel other than the one the plugin compared against.Not verified at the time of writing (0.2.1): how the status page, settings screen and sidebar row\nlook in the Paseo desktop window or on a phone (they were seen in the app's own web bundle in a br…
","readmeText":"# claude-update\n\n[](https://github.com/tomcrawf90/paseo-plugin-claude-update/actions/workflows/ci.yml)\n[](https://www.npmjs.com/package/paseo-plugin-claude-update)\n[](https://github.com/tomcrawf90/paseo-plugin-claude-update/blob/main/LICENSE)\n\nA [Paseo](https://paseo.sh) plugin that keeps the Claude Code CLI up to date on the machine your\nPaseo daemon runs on. Its status page shows which running agents are still on an old version.\n\n## Why\n\nClaude Code updates itself only from its interactive terminal interface. Paseo runs `claude` without\none, so on a machine that uses Claude mostly through Paseo the updater never runs and the CLI falls\nbehind. New models often need a newer CLI, so a stale CLI means missing them.\n\nThis plugin checks for a new version on a schedule and tells you. Once you turn on **Auto-update\nClaude Code** it also runs the CLI's own updater, `claude update`, and tells you what happened.\n\n## What it does\n\n| | |\n| --- | --- |\n| Checks | Every 4 hours by default, it compares `claude --version` with the version the release channel points at. |\n| Updates | Off until you choose it. With \"Auto-update Claude Code\" on, the scheduled check runs `claude update` when the CLI is behind, then reads the version again to confirm. Until then it only tells you; \"Update now\" installs on request. |\n| Reports | An update that went in: on its status page and in the history there, with a macOS notification. Something you have to act on (an update waiting with auto-update off, a failure): named on its sidebar row as well. Everything goes to a log file. |\n| Lists old processes | On the status page: running Claude Code processes (Paseo agents and Claude's own background daemon) that are still on an older version. It never restarts or interrupts them. |\n| Shows release notes | On the status page: the notes for the update that is waiting, or else for the last update, with a link to the full notes for every release. |\n| Shows that it is working | Its status page says when it last checked (how long ago and the clock time), how that ended, when the version last changed, and when it checks next, and has a \"Check now\" button. The settings screen has the same lines. |\n| Stays out of the way | While Claude Code is up to date, and after an update that worked, the sidebar row reads only \"Claude Code updates\" and no toast is raised, whatever is still running an older version. A check that finds nothing new changes only the \"Last checked\" time and the \"Last result\" line. |\n\nNew agents use the new version as soon as it is installed. Agents that are already running keep the\nversion they started with until they are restarted; that is how Claude Code works, and the plugin\nonly lists them.\n\n## Screenshots\n\nTaken from Paseo 0.12's own web app against a throwaway daemon with made-up data (`npm run screenshots`).\n\nAn update is waiting and auto-update is off, so the sidebar row says so:\n\n\n\nAfter \"Update now\": the release notes, the command to go back, and the processes still on the old version:\n\n\n\nThe settings screen:\n\n\n\n## Install\n\nRequires Paseo 0.10.3 to 0.12 (betas included), with plugins enabled (**Settings → Plugins**), and Claude Code\ninstalled with its native installer on the daemon host.\n\nFrom the official Paseo plugin directory, once it is listed there (Paseo 0.11 or later):\n\n```bash\npaseo plugin add tomcrawf90/claude-update\n```\n\nFrom npm, on any supported Paseo:\n\n```bash\npaseo plugin install npm:paseo-plugin-claude-update\n```\n\nOr from a checkout of this repository:\n\n```bash\npaseo plugin install /absolute/path/to/paseo-plugin-claude-update\n```\n\nThen `paseo plugin ls` should show `claude-update` as `running`. The first check happens about 30\nseconds after the plugin starts. A fresh install only tells you when an update is available and\nchanges nothing; turn on **Auto-update Claude Code**, on the status page or in the\nsettings, to have it update on the schedule.\n\n**Where to find it.** The sidebar row \"Claude Code updates\" opens the status page. Its first card,\n\"Checks\", says when the plugin last checked, how that ended and when it checks next, and has the\n\"Check now\" button (it only looks) and \"Update now\" (it installs). The same lines and \"Check now\"\nare on the settings screen, under **Settings → Plugins → Claude Code updates**. The Command Center\n(⌘K) has \"Claude Code updates: open status\", \"Claude Code updates: check now\" and \"Claude Code\nupdates: settings\". The row's title changes only when:\n\n| The row reads | When | It goes back to \"Claude Code updates\" when |\n| --- | --- | --- |\n| Claude update ready | A newer version is out and will not install itself: auto-update is off, or scheduled checks are | You dismiss the notice, or the update is installed |\n| Claude update failed | An update was tried and did not go in, or three checks in a row have failed | You dismiss the notice, or the update goes in. After failed checks alone, also when a check works again |\n| Claude pin mismatch | The installed version is not the pinned one and will not be moved to it by itself: auto-update is off, or scheduled checks are | You dismiss the notice, or it matches again |\n| Claude channel issue | Claude Code's own channel is not the plugin's, so nothing was installed | You dismiss the notice, or they match again |\n\nWhatever it reads, the row opens the status page, which has the detail. An update that went in\nnever changes the row: it is on the status page and in its history, with a macOS notification if those are on. Processes still on\nan older version are listed on the status page and nowhere else.\n\n**Release notes.** The \"Release notes\" card on the status page shows what changed: for an update\nthat is waiting, the versions it would bring; otherwise the versions the plugin's last update brought (or the\ninstalled version alone, before any update or after Claude Code updated itself). The newest three versions are shown, each with its\nfirst 12 changes, and the rest are counted. \"Full release notes\" opens\n[the Claude Code changelog](https://code.claude.com/docs/en/changelog), which has every release; its\naddress is on the card as well, to copy. The notes come from the changelog Anthropic publishes in\n[the claude-code repository](https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md). They are\nread right after a check, never as part of it, so they cannot hold up or change an update, and read\nagain only when the versions to show change. If they cannot be read, the card says why, keeps the link, and tries\nagain an hour later.\n\n**Auto-update Claude Code.** On: the next scheduled check installs a new version by itself, with\n`claude update` (or moves to the pinned version, with `claude install