Skip to main content
Keep your PraisonAI CLI current — 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

1

Upgrade in place

Update to the newest release using the tool manager that installed the CLI:
2

Check without changing anything

Report whether a newer version exists — no install, no mutation:
Example output:

How It Works

The command detects how the CLI was installed and runs the matching upgrade command:

Flags


Behaviour by Install Type

When installed via pipx, the command runs pipx upgrade praisonai against that isolated venv.
A plain pip install praisonai upgrades via pip install --upgrade praisonai. This is best-effort and shares your active environment.
If the install type can’t be self-managed, the command prints a clear manual fallback (for example pip install --upgrade praisonai) and exits non-zero rather than guessing.

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:
Running praisonai upgrade --check also warms this cache, so the next start reflects the newest info without its own network round-trip.

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