WARG CLI

warg-cli provides the warg command for working with the WARG autonomy monorepo. It reads the root projects.toml, loads each project's warg.toml, resolves project dependencies, manages Git sparse-checkout paths, and runs project-defined commands.

Installation

Install from PyPI:

uv tool install warg-cli

Commands

Clone the WARG monorepo with sparse checkout enabled:

warg clone
warg clone autonomy-monorepo
warg clone git@github.com:warg/autonomy-monorepo.git

Only root files such as README.md and projects.toml are checked out initially. Project directories stay absent until they are materialized. When called without a repository, warg clone opens a searchable list of repositories in the UWARG GitHub organization, sorted by most recently updated first. You can also pass a UWARG repository name instead of a full clone URL.

Fork, clone, and configure the autonomy bootcamp repository:

warg bootcamp
warg bootcamp my-bootcamp

This forks UWARG/autonomy-bootcamp into your account with the gh CLI, clones the fork, and sets origin to your fork and upstream to the original repository. It needs gh installed and logged in. See the bootcamp repository for details.

Check the machine for common dev environment problems:

warg doctor
warg doctor --verbose

Doctor checks the tools the CLI depends on (Git, uv, Docker, gh), SSH access to GitHub, and the current clone's remote, Git identity, and checked-out projects. Each result is marked ok, warn, or fail, with a suggested fix for anything that isn't ok. The command exits non-zero only when a check fails. Run it from inside a clone to include the repository checks; elsewhere they are skipped. --verbose prints the output of every command doctor ran.

List registered projects:

warg list

Materialize a project and its dependencies:

warg up gesture_control

Unload a project from sparse checkout:

warg down gesture_control

Projects that depend on the unloaded project are unloaded too, with a warning. Pass --include-dependencies to also unload checked-out dependencies.

Inspect a project's manifest metadata:

warg info gesture_control

Run commands defined in a project's warg.toml:

warg run camera test
warg run camera test:unit
warg run mavlink_comm lint -- --fix

If warg up or warg run is called without a project or command where one can be selected interactively, the CLI prompts for a choice.

Project commands

The CLI does not hardcode command names such as test, lint, or run. Projects define their own command surface in warg.toml:

[commands]
setup = "uv sync"
test = "uv run pytest"
run = "uv run python -m gesture_control"
lint = "uv run ruff check ."

warg up <project> runs setup for the project and its dependencies every time, keeping already-materialized projects in sync with their current setup commands.

Development

From the monorepo root directory:

warg run warg_cli setup
warg run warg_cli test
warg run warg_cli run -- --help

The package exposes the CLI entry point from pyproject.toml:

[project.scripts]
warg = "cli:app"