Update your installation

For a project-local installation such as my-abot, update the npm dependency inside the existing project. There is no need to create a new directory, clone the source repository, or initialize your configuration again.

Before updating

Read the release notes for the version you intend to install. Finish or stop active work deliberately, and remember that scheduled Jobs require a running Runtime: occurrences missed while it is offline are not replayed automatically.

Record the current package version:

cd my-abot
npm ls @abot-ai/runtime

Use the actual path to your installation. Make a private backup of its configuration and state before a significant update. Include package.json, the lockfile, .env, the active Runtime configuration, referenced model and request-runner files, methodologies you customized, and the runtime state directories selected by your configuration.

Do not assume every installation uses the same config path. LLM_RUNTIME_CONFIG_FILE, environment profiles, and custom paths can select different files or state directories. Keep the backup outside any public repository; it can contain credentials and conversations.

Update and restart

Stop the foreground npx abot start process using Ctrl+C after active work has finished. From that same installation directory, install the latest published release:

npm install @abot-ai/runtime@latest
npm ls @abot-ai/runtime
npx abot start

The middle command reports the installed version. Open the address printed by ABot and reload the Web UI. If you prefer an exact release, replace latest with the intended published version; for example:

npm install @abot-ai/runtime@1.8.1

These commands update a project dependency. A separately installed CLI, managed computer Companion, container image, or another my-abot directory is a different installation and may require its own documented update path.

Keep your configuration

Package upgrades do not automatically run a configuration migration or rewrite your local starter files. Existing legacy request-runner configuration remains supported as documented in the configuration reference.

Do not run abot init --force as an update step. --force explicitly asks to replace local starter files. If new configuration is needed for a feature, review the documented change and apply it deliberately to the existing installation.

After startup, check that the expected model profiles, project folders, conversations, and plugin selections are present. Send a small test request and inspect its result before resuming important automation. A package version number confirms what npm installed, not that every external dependency or model connection is healthy.

Check a paired Mac separately

Runtime updates can leave a paired Mac using an older Companion or Marketplace installation-link handler. If Repair Mac connection is available, use it. Otherwise, the updated project CLI can refresh the saved connection:

npx --no-install abot host status
npx --no-install abot host connect --url '<url from host status>'

Use the exact saved URL, not a newly invented address. This keeps the existing pairing while briefly reconnecting Computer access. Do not run disconnect first. OS permissions and SPARK collection controls remain separate from connection status.

If the update causes a problem

Keep the error output and compare it with troubleshooting. Do not delete .runtime or regenerate configuration merely to see whether the error disappears.

Reinstalling an older package is not, by itself, a guaranteed data rollback. Preserve the backup and current state, check compatibility, and restore only the components required by a deliberate rollback plan. Report a reproducible issue with the version and sanitized evidence if the problem persists.