You can tell your agent: "Update EditorBrain and check its skills." Updating does not edit videos, change your preferences, start renders or spend credits.
If you only use MCP
The service is updated at EditorBrain. You do not have to install Node.js or update a CLI. If new tools do not appear, reload the connector or open another conversation and ask it to read get_task_guide and get_editing_guide again.
Guides arrive in parts with their version and hash. An open conversation can keep old instructions; connecting MCP does not install or overwrite files in the Claude or Codex folders. Also confirm the workspace with workspace_info.
If you use the CLI
To update the CLI and your skills without losing your changes, run this sequence between edits, from your usual folder. It keeps customized files and reports the conflicts the command flags:
editorbrain version
editorbrain update --dry-run
editorbrain update
editorbrain version
editorbrain skill list
editorbrain status
In current versions, the first update shows what it would do. The second updates the global package and the skills of the current project and of existing global installs. It does not install another agent where there was none, it does not walk your disk and it does not update other folders by surprise.
| Need | Command |
|---|---|
| CLI and existing global skills only | editorbrain update --global |
| One specific project | editorbrain update --dir ./my-videos |
| Include registered projects, the current one and globals | editorbrain update --all |
| See destinations before updating all of them | editorbrain update --all --dry-run |
| Install skills for Claude and Codex globally | editorbrain skill install --global --agent both |
| Keep the skills of one edit | editorbrain skill pin --dir ./my-videos |
| Allow them to update again | editorbrain skill unpin --dir ./my-videos |
Installing with npm install -g editorbrain@VERSION changes the executable, not the skill copies already installed. Use update to coordinate both. If you run a pinned version with npx --package=editorbrain@VERSION, that command keeps using that version until you change it. A skill pin also does not pin the executable, the API or the engine dependencies.
What is kept
Projects, brands, assets, memory, credentials, preferences, MCP configuration and customized files are kept. Official files recognized by hash are updated with a backup. Files you modified stay as a conflict to review, without deleting them or replacing your AGENTS.md or CLAUDE.md.
Skill backups land in .editorbrain-local/skill-backups/ for projects or ~/.config/editorbrain/skill-backups/ for global installs. They are backups of instructions, not of your videos.
If it returns attention_required or exit code 2, review the state of each destination: the CLI may have updated even if one folder keeps customizations. If npm fails or there is a timeout, check editorbrain version before you repeat the install. Do not use sudo or --force, and do not delete the folders to avoid the conflict.
After you update
Open a new chat or ask the agent to read the skills again. Check status and workspace_info, the project and the capabilities before you continue. A local update does not deploy the API and does not grant premium access or spending permission.
Version 0.39.1 had a bug in update --dry-run and update --all: do not use those options as a guarantee of a dry run on that version. Install a published and verified version from Install and connect and then update the instructions of the destinations you chose.
Versions and availability separates a published version from a pending candidate. A merged pull request is not yet an npm release.
Notices and the detected version
In "Connect AI," compatible CLI connections show the latest version they reported and when. That is the last data received from that connection: the browser cannot inspect your computer. If several terminals use the same connection, you see the most recent observation; an old connection can say that a version has not been detected yet. You do not need to authorize it again.
"Copy message to update" prepares the request for your agent. Paste it between edits; copying it does not run the update. After that, editorbrain status lets a compatible CLI report the version with your usual connection.
Notices inside the app summarize important versions and link to this guide. Dismissing them saves the read on your account, including other workspaces and browsers. Dismissing the notice does not update the CLI. If you only use MCP, reloading the service instructions as described above is enough.