Keeping your BlueRock toolkit up to date
Which copy of the toolkit your session runs, how to tell whether it is behind, and how to update it.
- Explains which copy of the BlueRock toolkit your session runs, and how to update it.
- Something told you your toolkit is behind, or you want to confirm which version you are on.
The version that counts is on your own computer
When you connect from Claude Desktop, Desktop sends its own copy of the BlueRock toolkit into your workspace, and that is the copy your session uses. The version installed on your computer decides what you get.
Updates do not arrive on their own
Claude Code leaves automatic updates off for plugins that come from outside its own catalog, and the BlueRock toolkit is one of those. Unless you have turned automatic updates on, your copy stays at the version you installed.
How to tell whether you are behind
Run /bluerock:check. It reads the version you are running, compares it against the published one, and tells you. /bluerock:wrap-up and /bluerock:learn also mention it when they notice.
Do not read the Update button as an answer. It compares against a copy of the catalog your app has stored rather than against what has been published, so a stale copy greys it out whether you are current or a long way behind. The version number under the plugin name is the honest signal.
Updating
In Claude Desktop, go to Customize → Plugins, open BlueRock Builder Toolkit, and click Update. Then quit Claude Desktop fully and open it again.
If Update is greyed out and /bluerock:check says you are behind, the stored catalog is stale and the button cannot refresh it. Two commands in a terminal on your own computer do it, in this order:
claude plugin marketplace update bluerockclaude plugin update bluerock@bluerock
Then quit Claude Desktop fully and open it again. If your computer does not recognise the claude command, ask in the Builder Community.
The terminal inside Claude Desktop is your workspace
The >_ terminal in Claude Desktop opens a terminal in your BlueRock Cloud AI Workspace, not on your computer. Running the update commands there updates the workspace’s copy, which is not the copy your session uses. Use your computer’s own terminal.