Skip to main content
praisonai upgrade updates the managed CLI in place using whichever tool manager installed it, and --check reports whether a newer release exists without touching anything.

​
Quick Start

1

Check for a newer version

Queries PyPI (5s timeout) and prints Update available: X.Y.Z -> X.Y.Z+1 or You are on the latest version (X.Y.Z).
2

Upgrade in place

Detects the manager (uv → pipx → pip) and runs the matching upgrade command.

​
How It Works

praisonai upgrade mirrors the one-line installer’s detection order and only ever touches the CLI binary.
This is CLI self-management only — praisonaiagents (the SDK) is never touched by praisonai upgrade.

​
Options

praisonai upgrade takes a single flag.

​
JSON output

Add --output json for machine-readable output.
--check also warms the background update-check cache, so long-lived installs surface the update hint on next start without their own network round-trip.

​
Common Patterns

Check first, then upgrade in CI.
Non-interactive fleet upgrade — upgrade never prompts, so it is safe to run unattended.

​
Non-Managed Installs

When PraisonAI was installed with plain pip (library/embedded use), automatic upgrade is unsupported.
If --check cannot reach PyPI, it exits non-zero:

​
Best Practices

Run praisonai upgrade --check --output json and gate the upgrade on update_available so pipelines only reinstall when a new release exists.
The one-line installer provisions uv tool or pipx. Keep that managed environment so praisonai upgrade can update in place without manual pip commands.
Leave the background update hint on. --check warms its cache, so subsequent starts remind you to upgrade without any network call.

praisonai uninstall

Cleanly remove the managed install

Update Hint

Non-blocking “update available” notice

Installer Internals

How install.sh provisions the CLI

Quick Install

One-liner install