praisonai uninstall

Cleanly remove the managed PraisonAI CLI environment and shim

Cleanly remove the PraisonAI CLI — praisonai uninstall deletes the managed environment and global shim that the one-line installer created.

praisonai uninstall

This is CLI self-management only. The core praisonaiagents SDK is not removed by this command.

Quick Start

1. Interactive uninstall

   Prompts for confirmation, then removes the managed install:

   praisonai uninstall
   

   Remove PraisonAI 1.3.0 (installed via uv)? [y/N]
   
2. Non-interactive (CI)

   Skip the prompt with --yes (or -y):

   praisonai uninstall --yes
   

---

What It Removes

Removed	Not touched
The managed environment (uv tool / pipx venv)	Your ~/.praison/ config and state
The global praisonai shim on your PATH	Any provider API keys you configured

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

Install type	Uninstall command run
uv-managed	uv tool uninstall praisonai
pipx-managed	pipx uninstall praisonai
plain pip	pip uninstall -y praisonai

If the install type can’t be self-managed, the command prints a clear manual fallback (for example pip uninstall praisonai) and exits non-zero rather than deleting anything unexpectedly.

---

Flags

Flag	Description
--yes, -y	Skip the confirmation prompt (non-interactive / CI).
--json	Global flag — emit machine-readable output ({"manager": ..., "removed": ...}).

Human output

praisonai uninstall --yes

PraisonAI 1.3.0 removed.

JSON output

praisonai --json uninstall --yes

{"manager": "uv", "removed": "1.3.0"}

---

Best Practices

Use --yes in scripts and CI

Non-interactive shells have no TTY for the confirmation prompt. Pass --yes (or --json) to run cleanly in automation.

Keep your config if you plan to reinstall

praisonai uninstall leaves ~/.praison/ in place, so a later reinstall keeps your settings and cache. Remove that directory manually only if you want a fully clean slate.

---

Related

praisonai upgrade

Update the managed CLI install in place

Installer Internals

How the one-line installer works

Installation

Install paths for CLI and SDK users

Isolation Backends

uv, pipx, and venv explained