One task to completion. --team splits it across a Flood, --json emits newline-delimited events, --yes runs it unattended. Exits 0 completed, 1 failed, 2 cancelled, 3 out of capacity — or pass --wait-for-capacity to sit out a provider's limit and carry on when it lifts.
# the current release, checksummed
curl -fsSL https://github.com/Mehxeo/Velora/releases/latest/download/install-velora-cli.sh | shVerifies a SHA-256 checksum, installs to ~/.local/bin, and never asks for sudo. The installer picks Apple silicon or Intel for you.
Also on npm i -g runvelora, brew install mehxeo/tap/velora-cli and scoop install velora-cli. Those three are published separately and can sit a version or two behind the release above.
The standalone release includes its runtime. Mac app and CLI downloads are Developer ID signed and notarized. Direct Windows downloads remain unsigned.
The whole engine, in your terminal.
velora runs the same control plane the desktop app runs — the same agents, missions, memory, permissions and approvals, against the same account. It is not a remote control for the app: it is the engine, embedded in the process, with its own database at ~/.velora/velora.sqlite.
Use one-shot commands in scripts or open an interactive session with velora. List commands offer JSON output; run --json streams events. Exit codes distinguish completed, failed, cancelled, and capacity-limited work.
First five minutes
velora doctor # what can this machine run?
velora workspace add ~/code/api # open a project
velora run "migrate the users table" --budget 5
velora tasks # what is running, and what is waiting
No account and no sign-in is needed to run work on your own machine — bring a coding agent you already have and go. velora login is what connects this install to your Velora account, the plan that comes with it, and the devices on it.
The commands
Quick capture. Takes your saved defaults — agent, model, project — and starts, so a thought costs one line.
Search durable history with project, provider, status, and workspace filters. --page-json includes the continuation cursor. Inspect receipts before explicitly accepting prepared changes.
Autopilot: start, pause, resume, stop, approve a review, add a constraint to the mission ledger.
What is waiting on you, and the decision that answers it. --json here too, on both the queue and its history, so a script can read a decision and act on it.
What the work knows, what happened while you were away, and what still needs you.
Create project context, save a report, inspect document history, and revise it with version checks. Project covers and managed Google account setup remain in the desktop app.
Read the provider’s live model catalog, inspect runtime health, and reconnect a disconnected agent.
What this machine can actually run, and the exact command to install what it cannot.
An authenticated local stdio daemon. It remains available until shutdown or input closes, and accepts cancellation while work is running.
Approvals still ask
The terminal does not lower the bar. An action that reaches past the task pauses for the same decision the app would ask for — a to allow, d to deny — and a command that needs administrator rights is refused whichever way it is written. In a script, --yes answers the routine ones for you; nothing answers the ones the engine will not delegate.