DocsGet started
Update
Update the blueprint the way you installed it. The table below gives the update command for each tool, and each tool’s support note on GitHub says how to check the install there:
Each tool updates Agent Blueprint through its own route. Cursor CLI and Amp follow Claude Code’s update when they read its plugin.
| Tool | How to update |
|---|---|
| Claude Code | claude plugin marketplace update agent-blueprint, then claude plugin update agent-blueprint@agent-blueprint, then /reload-plugins in a session |
| Codex | codex plugin marketplace upgrade agent-blueprint, then codex plugin add agent-blueprint@agent-blueprint again. Codex caches each version separately, so the second command is needed |
| Antigravity | Run agy plugin install https:// again |
| Grok Build | grok plugin update agent-blueprint |
| Pi | pi update --extensions |
| Cursor CLI | Claude Code’s update when Cursor CLI reads its plugin. For Cursor’s own install, cursor-agent plugin marketplace update agent-blueprint, then update agent-blueprint through /plugin in a session |
| Hermes | git pull in your clone of the repository, then bash install.sh --only hermes again |
| Amp | Claude Code’s update when Amp reads its plugin. For the Amp-only copy, git pull in your clone, then bash install.sh --only amp again |
In any tool, the ab-plugin-update skill finds the route you used, runs it and checks the installed version against main. Before the release, each tool was installed by its route from a local checkout, in a clean profile, and listed every skill once, and ab-plugin-update moved a Codex install from 4.0.2 to 4.1.0 (install record).