Stable Pipx install
Install the isolated distribution, then verify local readiness.
$ pipx install algo-cli-runtime
$ algo-cli doctor
Algo CLI v0.20.1 is available from PyPI for Python 3.10 or newer. The algo-cli-runtime distribution installs the algo-cli command.
Version 0.20.1 is published from the immutable v0.20.1 tag through the protected release workflow. Wheel and sdist digests are listed in the release manifest.
Install the isolated distribution, then verify local readiness.
$ pipx install algo-cli-runtime
$ algo-cli doctor
Use uv for a fast isolated tool installation.
$ uv tool install algo-cli-runtime
$ algo-cli
Update in place from 0.20.0 or 0.19.2. Configuration, credentials, memory, and workspace settings are preserved. A 0.19.1 install in a pip-free uv pip environment cannot self-update; run uv pip install --upgrade algo-cli-runtime there once.
$ algo-cli update
$ algo-cli --version
Check out the immutable v0.20.1 tag when you want to inspect the exact source. Its release page carries the source archive, SBOM, provenance, and Sigstore bundles.
$ git clone https://github.com/Seabass-up/Algo-cli.git && cd Algo-cli && git checkout v0.20.1
$ pipx install . && algo-cli doctor
$ ollama pull qwen3
$ algo-cli
$ algo-cli config setup chatgpt
Then select a Codex model with algo-cli --model gpt-5.6-sol.
$ algo-cli --oneshot --json "summarize this folder"
The first event is session_start; the last is done.
$ algo-cli
$ /intelligence init
New in 0.20.0: the package ships no personal pattern catalog or kernels. /intelligence init creates an empty ~/.algo_cli/ALGO.md and kernels.json for you to fill; /kernel help shows the format.
$ /memory doctor
Memory routes only through the separately installed continuum-memory command, selected by setting continuum_enabled to true in ~/.algo_cli/config.json; /memory doctor then verifies both scopes. Upgrading from a configuration that still names a retired backend? Run algo-cli config memory repair.
$ algo-cli config jev enable --cli /absolute/path/to/jev-workflows
Bounded question contracts through the separately installed companion. Lint is local; inference needs this explicit setup and session approval, and answers never authorize actions.