/update

/update checks for a newer version of the AI Business OS engine and applies it after you agree. It previews every change first, backs up the files it replaces and keeps the edits you have made to engine files wherever it can. If your workspace has PRIMA Project Management, the same run updates it too.

PRIMA Project Management leaves /update as it is. The Updating Your Installation page covers the routine in a getting-started context.

What an Update Touches

AI Business OS separates two kinds of file.

Kind	Examples	On update
Engine files	Rules, skills, commands, agents, documentation and scripts	Updated from the new version
Your files	.claude/CLAUDE.md, the files in .claude/company/, state.json, integrations.json and the CLAUDE.md in each domain	Never touched

The file .claude/engine-manifest.json lists every engine file. An update changes only files on that list, so your projects, client folders, custom skills and anything else you have added stay as they are. An update never deletes a file, even one that a newer version no longer includes.

When to Use It

Run /update when you hear that a new version is out, or from time to time to check. If someone manages your workspace for you, they apply updates on your behalf and the changes reach you the next time you pull, so you do not need to run /update yourself.

How to Run It

1. Type /update in the message box at the bottom of the Claude Code panel and press Enter.
2. Read the preview of changes that Claude shows you, which lists every file the update would change.
3. Choose Apply now or Skip for now when Claude asks whether to apply the update.
4. Check the summary, which gives the old and new version, the number of files and where the backup is.

If the preview shows that you are already up to date, Claude stops there.

What It Does

1. Checks the update script and your version. Claude confirms that Infrastructure/Scripts/update-engine.sh exists and reads engineVersion from the engine manifest. If the script is missing, your workspace predates the update system and needs a manual update.
2. Previews the update. Claude runs the script with --dry-run and shows you the result, without changing anything at this stage.
3. Asks you to decide. Claude explains that the update brings fixes and improvements and that skipping keeps your current version.
4. Applies the update. Claude runs the script with --force, which applies the changes without a second prompt.
5. Commits. Claude commits the update with a message such as Update engine to v3.0.2, naming the PRIMA Project Management version as well when that was updated.

How Your Edits Are Kept

The preview sorts the changed files into groups, and the script treats each group differently.

Group	What happens
Updated	Files you have not edited are replaced with the new version
Locally modified	Files you have edited are merged. Your changes and the new version’s changes are combined
Critical	Files that control safety and updating are always replaced. Your .claude/settings.json is merged instead, so the permissions you approved and any hooks you added are kept
No merge base	Files the script cannot compare against the version you started from are replaced, and your copies are kept in the backup
New	Files that the new version adds
PRIMA-skipped	With PRIMA Project Management installed, the commands and files it manages are left to its own update

To merge an edited file, the script compares three copies. These are the upstream copy at the version you run, your copy and the new version. If you and the new version changed different parts of a file, both sets of changes survive. If you both changed the same lines, the file gets conflict markers.

Caution

A merge conflict leaves markers such as <<<<<<< in the file. Open each file the summary lists, search for the markers and choose which text to keep before you commit, or ask Claude to work through the conflicts with you.

Before applying anything, the script commits any uncommitted work as a snapshot, so you can return to that point with git revert. It also copies every engine file into .claude/engine-backups/v[old version]/.

Undoing an Update

Type /update rollback, or ask Claude in your own words to undo the last update. Claude does not check for updates in this case. It restores the engine files saved before the last update, reports the version and number of files restored, and commits the result unless you ask to review it first.

The rollback restores engine files only. Your company files, projects and settings you added are not affected. If the last update also updated PRIMA Project Management, the PRIMA Project Management files are not rolled back by this step. If there is no earlier version saved, Claude tells you so. The rollback leaves in place any files that the update added, because it copies files back and deletes nothing.

Running the Update From a Terminal

You can run the same script yourself from the workspace root.

bash Infrastructure/Scripts/update-engine.sh

Option	What it does
--dry-run	Shows what would change and changes nothing
--force	Applies the update without the confirmation prompt
--rollback	Restores the engine files from the most recent backup
--health	Reports any critical engine files that differ from the upstream copy. It changes no files, though it adds the upstream remote if your workspace does not have one

The script stages its changes and tells you the commit command to run, so you can review them first with git diff --cached.

Where Updates Come From

The script fetches the new version from a git remote called upstream. If your workspace has no remote with that name, the script adds one using the address in the engine manifest. With PRIMA Project Management installed, it also fetches from a second remote called prima-upstream. If that fetch fails, the script skips the PRIMA Project Management update with a warning and still applies the engine update.

When Something Goes Wrong

Problem	What to do
No access to the upstream repository	Check that git can reach the repository, for example with gh auth status if you use the GitHub command-line tool
jq is not installed	Install it, with brew install jq on macOS or sudo apt install jq on Linux and WSL
The engine manifest is missing	The workspace needs a manual update. Contact support
A version 1 company profile is found	The script tells you to run bash Infrastructure/Scripts/migrate-company.sh and then /migrate-company

Example

/update

Engine updated: v3.0.1 → v3.0.2
[count] files updated, backup saved to .claude/engine-backups/v3.0.1/

To undo this update: type /update rollback

Related Pages

• Updating Your Installation
• Hooks Overview
• Configuration
• Troubleshooting