Runs & execution
A run is a single autonomous task. This page covers its lifecycle, states, and how to control it.
Lifecycle
| State | Meaning |
|---|---|
| queued | Accepted, waiting for an executor. |
| running | Actively planning, editing or executing. |
| healed | Recovered from one or more failures, completed successfully. |
| ok | Completed successfully without recovery. |
| failed | Halted after exhausting recovery budget. |
| cancelled | Stopped by a user or policy. |
Triggering a run
bash
# CLI
veyra run "Refactor billing module to use webhooks"
# REST
curl -X POST https://veyra.tubox.cloud/v1/runs \
-H "Authorization: Bearer $VEYRA_KEY" \
-d '{"goal":"Refactor billing module to use webhooks","repo":"acme/api"}'Inputs
- goal — natural language intent.
- repo — target repository (Git remote or local path).
- branch — base branch (default: main).
- policy — overrides for sandboxing, model routing, or budgets.
Cancelling
Cancel from the Run history page or with veyra cancel <run-id>. Cancellation is graceful — Veyra will commit any safe partial work before halting.