How do I know an update is available?
While a board is open, the local app checks the latest published release. When a newer version exists, the board shows a small update notice. Open it to see what has changed, with a link to the release notes. You can also ask your agent: Check whether Planban has updates.
Each release is listed in the changelog.
What do "Update now" and "Update with Codex" do?
These buttons are in the board's update panel and are built for Codex installs. Before it offers them, Planban inspects the install.
- Update now appears when Planban can prove the install is safe to update directly: a Git-backed marketplace install or a local clone, with no unexpected local changes and the needed commands available. Planban shows its progress, refreshes the local install, restarts the local app and reopens the board you were viewing.
- Update with Codex appears when direct update is not safe: the install shape is unclear, dependencies are missing, a migration is needed, or local files would be overwritten. It opens a draft prompt in Codex that asks your agent to inspect the install, update it safely, verify the plugin and MCP tools, and open the right page afterwards. Copy update prompt puts the same prompt on your clipboard.
- Setup needed appears when a command Planban needs is missing:
node,npm,gitorcodex. Copy setup prompt and Open setup prompt in Codex ask your agent to install it.
In Claude Code, update with the plugin commands below.
How do I update Planban in Codex?
Choose Update now or Update with Codex on the board, or update from a terminal. These are the commands the board's update prompt gives. For a Git-backed marketplace install, upgrade the marketplace, then run the rest in the marketplace folder:
codex plugin marketplace upgrade planban
cd "$PLANBAN_ROOT"
npm install
node scripts/configure-local-plugin.mjs "$PWD"
codex plugin add planban@planbanFor a local clone install, update the clone with git pull instead of upgrading the marketplace, then run the same steps in the clone:
cd "$PLANBAN_ROOT"
git pull
npm install
node scripts/configure-local-plugin.mjs "$PWD"
codex plugin add planban@planbanPLANBAN_ROOT is your marketplace folder or clone; see How do I run the CLI? to set it.
Then start a new Codex session. If an older cached plugin still contains __PLANBAN_REPO_ROOT__, refresh the marketplace and reinstall the plugin, then start a new session.
How do I update Planban in Claude Code?
Update the marketplace, then the plugin:
claude plugin marketplace update planban
claude plugin update planban@planbanWhen a release changes dependencies, also run npm install in the marketplace folder ($HOME/.claude/plugins/marketplaces/planban). Then start a new Claude Code session.
Why does Claude Code need a reinstall to pick up plugin changes?
Claude Code copies the plugin's skills, hooks and scripts into its plugin cache when you install. The Planban runtime itself runs from the marketplace folder. claude plugin update refreshes the cache only when the plugin's version number changes, which every release does.
If you run Planban from a local clone and change anything under plugins/planban/ without a new version number, reinstall the plugin, then start a new session:
claude plugin uninstall planban@planban
claude plugin install planban@planbanWhy do I need to start a new session after updating?
A running session keeps the Planban MCP server it started with, along with its configuration. An idle session keeps that server process alive and does not see the update until it restarts. Opening a board does not refresh it either. Start a new session in Codex or Claude Code after every update.
Some releases also change the guidance that set-up writes into your projects. The release notes say so, and you can refresh a project's guidance by running set-up again.
What does the update check send to GitHub?
The check downloads one public file, release/latest.json, from the Planban repository on GitHub. The request carries a timestamp to avoid stale caches and identifies itself as planban-update-check. It sends no board contents, repository paths, logs or project details.
The file lists the latest version, a summary, the release notes link and release-specific update instructions, which the Update with Codex prompt includes. If the check fails, the board says it could not check for updates and nothing else changes.