updatelisted

# Updating charter One command converges the upgrade. Your job is the conversation around it. ```bash charter update ``` It moves the CLI, asks this harness how its own artifact moves, proves the install took by handing off to the new binary, and reports what the new version brought. **Read its output and relay it** — that text is the report, not a summary of one. It is idempotent: run it without first working out whether there is anything to do. ## Where it stops, and what you do there **The pin.** When this plane already sits on its pin and something newer is published, `update` proposes `charter update --bump` and stops. Moving the pin moves every teammate on their next session, so get an explicit yes before running it. **A host's command.** Claude Code's plugin and Codex's belong to the host, so charter names the command rather than running it. Hand that command to the person and let them run it. **A charter checkout.** The CLI there is the tree being edited, so `update` never installs over it — that refusal stays. What it does instead depends on what is left to do: on the **dev channel** it refreshes the Claude Code plugin, which lives outside the tree, and says that is all it did; on stable, and whenever `--to` names a version, it refuses outright. `charter version` is the read-only view either way. ## Adopt what the version brought ```bash charter news --pending ``` Each line is one entry: its slug, what it gives you, and how to take it up. An entry prefixed