Skip to content

Run a task

Bridge workflow dispatch and execution callbacks were removed in S5 (owner decisions a9f0e60e and 6cab5c63). Coordinators run tasks with scripts/heyaira-run.sh and record results with task_update. Historical workflow data remains readable; no migration or data deletion is part of this change.

  1. Read the task with task_get, confirm its scope and repository, and prepare a brief file containing the work and the commands that verify it.
  2. From the HeyAira repository, run:
scripts/heyaira-run.sh --repo /path/to/main-clone --id 1234abcd \
  --branch codex/task-1234abcd --brief /path/to/brief.txt \
  --check 'PYTHONPATH=src python -m pytest -q tests'

Choose the check for the target repository. The default base is origin/main; --base origin/<branch> selects another base. --no-pr and --no-review disable those publication steps. The script can commit and publish changes; use it only within the task's authorization. 3. Inspect the script's exit status and local logs. Exit 0 means finished; 2 is invalid usage, 3 no changes, 4 failed checks, 5 worker/Git/GitHub failure and 6 a missing or unclear review or open P1/P2 findings. A failed check can still result in a published PR: inspect the evidence before closing the task. 4. Read task_get again, then save the outcome with task_update, the current expected_version and write_context. Include actual checks, remaining blockers, branch/commit references and the required completion receipt.

The script does not perform HeyAira bookkeeping. The coordinator owns task updates, corrections and the decision to proceed. For PR monitoring use task_ci_follow and task_ci_failures; historical Bridge workflow state can still be inspected with workflow_get.