CLI Reference¶
The canonical developer workflow uses the cross-platform intellifl-dev CLI. Every command is invoked through uv run:
make compatibility
make <target> is still available as a thin wrapper, but intellifl-dev is the source of truth for all supported commands.
Environment¶
| Command | Description |
|---|---|
check-env |
Verify that uv, Python, and Docker are available and correctly configured |
Setup & Maintenance¶
| Command | Description |
|---|---|
setup |
Install all Python dependencies and download datasets |
upgrade |
Update all dependencies to their latest versions |
yolo |
Nuke and rebuild: runs clean → setup → upgrade in sequence |
Development Workflows¶
| Command | Description |
|---|---|
dev |
Start all services via Docker Compose (hot reload in dev mode) |
dev-down |
Stop all services |
docs |
Serve the documentation site locally (Zensical) |
sim |
Run a local simulation with optimized Ray environment |
baselines |
Record fast simulation baselines for CI regression checks |
This starts the full Docker Compose stack: API, frontend, Redis, Celery worker, and docs site. In development mode, docker-compose.override.yml is automatically applied for hot reload.
Runs the default example config at config/simulation_strategies/example_strategy_config.json. Pass extra arguments after --:
Quality Gates¶
| Command | Description |
|---|---|
lint |
Run code quality checks (ruff format, ruff check, ty) |
validate |
Quick feedback: lint + unit tests only |
test |
Full test suite: unit + integration + performance |
audit |
Audit Python dependencies for known security vulnerabilities (pip-audit) |
frontend-audit |
Fix frontend (npm) security vulnerabilities |
Security scanning
audit runs pip-audit against the locked dependency set. frontend-audit runs npm audit fix in the frontend/ directory.
Maintenance¶
| Command | Description |
|---|---|
deps |
Show the dependency tree |
clean |
Remove build artifacts and caches |
reset |
Clean artifacts and experiment results (out/) |
cache-dir |
Show uv's cache directory location |
cache-prune |
Prune unused entries from uv's cache |
Destructive commands
reset deletes the out/ directory containing all simulation results. Use clean if you only want to remove build artifacts.
Passthrough arguments¶
Any command accepts extra arguments after a -- separator. These are forwarded directly to the underlying script or tool: