Updates

Update an Open Ticket AI install to a new release.

Updates

Use the CLI to safely upgrade Open Ticket AI. Updates automatically create a backup and roll back if post-update checks fail.

Online update

# From any directory once install put `otai` on PATH:
otai update              # latest version allowed by the license
# or:
otai update 0.2.0

Air-gap update

Copy the extracted release tree to the server, then run:

otai update --from-dir /path/to/otai-0.2.0

No download API call is made in this mode.

What otai update does

  1. Tags running images with the old version for rollback.
  2. Runs otai backup to store an archive under backups/.
  3. Downloads the release or reads it from --from-dir.
  4. Loads image tars, updates compose files, CLI helpers, .env, and PATH wrapper.
  5. Starts the stack (docker compose up -d).
  6. Runs otai verify health checks.
  7. On failure: restores the pre-update backup (compose, .env, SQLite DBs) and restarts the previous version.

Verify

otai verify
otai version

verify checks that Studio API and Runtime containers are running and responding on /health.

Tips

  • Prefer pinned versions in production (otai update 0.2.0).
  • Do not run docker image prune during or right after updates so rollback tags remain available.
  • otai update does not upgrade ticket-system add-ons. Apply OpenTicketAI (and optional OTAICustomerChat) via your ticket system package manager.
  • Save a backup off-host before major upgrades (see Backups).