CLI Installation
Document ID: CLI-001
File Path: docs/11-cli/installation.md
Version: 2.0.0
Status: Shipped — every install method below is a real, published artifact.
Owner: AI Platform Team
Last Updated: 2026-08-01
1. Purpose
Section titled “1. Purpose”How to install, update, and verify the wovyr CLI.
Scope note. Version 1.0.0 of this document described an install script at
get.wovyr.example.com, a Homebrew tap, winget/Scoop packages, aghcr.io/wovyr-ai/cliimage, release channels, and the commandswovyr upgrade,verify,completion,version,doctor, anduninstall— none of which exist. It was rewritten to describe what actually ships.
2. Supported Platforms
Section titled “2. Supported Platforms”Release binaries are built for:
| OS | Architecture | Artifact |
|---|---|---|
| Linux | x86_64 | wovyr-linux-x86_64.tar.gz |
| macOS | aarch64 (Apple Silicon) | wovyr-macos-aarch64.tar.gz |
| Windows | x86_64 | wovyr-windows-x86_64.zip |
Other targets (Linux aarch64, Intel macOS) are not pre-built — install from
source with cargo, which works anywhere the Rust toolchain does.
The CLI is a single Rust binary. Optional features (mistralrs, tiered-memory,
postgres, plugin-wasi, otlp, redis) are compile-time and therefore only
available via a cargo install or a source build.
3. Install Methods
Section titled “3. Install Methods”3.1 crates.io (recommended)
Section titled “3.1 crates.io (recommended)”cargo install wovyr-cli # installs a `wovyr` binaryRequires Rust 1.85+ (edition 2024). This is the path the README quickstart uses.
With optional features:
cargo install wovyr-cli --features tiered-memory,postgres3.2 Release binaries
Section titled “3.2 Release binaries”Each v* tag publishes the archives in §2 to the
GitHub Releases page, each
with a .sha256 companion file. Download, verify (§5), extract, and put wovyr
on your PATH.
3.3 Container image
Section titled “3.3 Container image”docker run --rm ghcr.io/punarduttrajput/wovyr:latest --versionTagged with both the release version and latest. This image runs the server
too — see docker.md.
3.4 From a clone
Section titled “3.4 From a clone”git clone https://github.com/punarduttrajput/wovyr && cd wovyrcargo build -p wovyr-cli # target/debug/wovyrEvery wovyr … invocation in the docs is equivalent to
cargo run -p wovyr-cli -- …, so a clone needs no install step at all.
4. Versioning
Section titled “4. Versioning”There are no release channels. The CLI version is the workspace version, kept in lockstep with the release tag (DX-101) — see CHANGELOG.md.
wovyr --versionNote that the roadmap milestone names (v1.0…v1.6) are planning labels and run
ahead of the package version by design; the
README explains the split. The CLI
does not currently check its version against a target server’s API version.
5. Verifying a Download
Section titled “5. Verifying a Download”Release archives ship a SHA-256 checksum. Compare it yourself:
sha256sum -c wovyr-linux-x86_64.tar.gz.sha256 # Linuxshasum -a 256 -c wovyr-macos-aarch64.tar.gz.sha256 # macOSGet-FileHash wovyr-windows-x86_64.zip -Algorithm SHA256 # WindowsThere is no wovyr verify command and release binaries are not signed today.
The Sigstore-shaped keyless signing described in
ADR-0009 applies to plugin packages
(wovyr plugin keyless-sign), not to the CLI binary itself.
6. Updating
Section titled “6. Updating”Re-run the install method you used:
cargo install wovyr-cli --force # crates.iodocker pull ghcr.io/punarduttrajput/wovyr:latestThere is no wovyr upgrade self-update command.
7. First Run
Section titled “7. First Run”wovyr --version # confirm the installwovyr agents run --local -f examples/agents/hello.yaml --input '{"message":"Hi"}'The local run needs no server, no API key, and no login — it falls back to a deterministic mock provider. To talk to a server, see configuration §4.
There is no wovyr doctor. If a local run misbehaves, set WOVYR_LOG=debug.
8. Shell Completion
Section titled “8. Shell Completion”Not implemented — there is no wovyr completion command.
9. Uninstall
Section titled “9. Uninstall”cargo uninstall wovyr-cli # or just delete the extracted binaryThis leaves ~/.wovyr in place. That directory holds real data — KMS root key,
secrets, memory, workflow checkpoints, installed plugins — so remove it only
deliberately, and take a backup first
if any of it matters. There is no wovyr uninstall command.
10. Related Documents
Section titled “10. Related Documents”11-cli/index.md11-cli/configuration.md11-cli/commands.md19-implementation-guide/release-process.md
11. Revision History
Section titled “11. Revision History”| Version | Date | Description |
|---|---|---|
| 2.0.0 | 2026-08-01 | Rewritten against real artifacts: cargo install wovyr-cli, the three published release archives, and ghcr.io/punarduttrajput/wovyr. Removed the fictional install script, Homebrew tap, winget/Scoop packages, release channels, and the upgrade/verify/completion/version/doctor/uninstall commands; corrected the signing claim to scope it to plugin packages |
| 1.0.0 | 2026-06-27 | Initial CLI Installation (target-state, largely unimplemented) |