praisonai upgrade updates the managed install in place using whichever tool manager provisioned it.
This is CLI self-management only. The core
praisonaiagents SDK is never touched by this command.Quick Start
How It Works
The command detects how the CLI was installed and runs the matching upgrade command:| Install type | Upgrade command run |
|---|---|
uv-managed (one-line installer) | uv tool upgrade praisonai |
pipx-managed (one-line installer) | pipx upgrade praisonai |
plain pip (library / SDK install) | pip install --upgrade praisonai |
Flags
| Flag | Description |
|---|---|
--check | Report whether a newer version exists without upgrading. Exits 1 if PyPI can’t be reached. |
--json | Global flag — emit machine-readable output (current / latest / update_available). |
- Human output
- JSON output
Behaviour by Install Type
uv-managed (recommended)
uv-managed (recommended)
The one-line installer provisions an isolated
uv tool environment. praisonai upgrade runs uv tool upgrade praisonai — clean, in place, no other Python touched.pipx-managed
pipx-managed
When installed via
pipx, the command runs pipx upgrade praisonai against that isolated venv.pip-installed (library use)
pip-installed (library use)
A plain
pip install praisonai upgrades via pip install --upgrade praisonai. This is best-effort and shares your active environment.Update Hint on Start
Long-lived installs surface a non-blocking “update available” hint on start (text mode only), backed by a time-boxed cache at~/.praison/state/update_check.json (24h TTL). It never performs network I/O at start-up and never blocks or raises.
Opt out with an environment variable:
Related
praisonai uninstall
Cleanly remove the managed CLI install
Installer Internals
How the one-line installer picks a backend
Installation
Install paths for CLI and SDK users
Isolation Backends
uv, pipx, and venv explained