Tasks

A task is what you ask Zaprex to do. Each task starts a run: one attempt in its own sandbox.

Where tasks come from

• The chat in the Zaprex app (one conversation per repository).
• A routine, on its schedule.
• A follow-up on an earlier run, for example "address the review comments".

Writing good tasks

• Name the file, test or behaviour: Fix the failing auth tests beats fix stuff.
• Say what done means: "tests pass", "no new lint warnings".
• Keep it to one repository per run.

Run lifecycle

queued → starting → running ⇄ awaiting_approval → finishing → succeeded | failed | cancelled | timed_out

• queued / starting: the server checked your plan and limits and a sandbox is being prepared.
• running: Zaprex is working; steps stream into the run log.
• awaiting_approval: a risky step is waiting for you. See Approvals and safety.
• finishing: tests ran, the branch is pushed and the draft PR is opened.

Cancel a run

Use the stop button next to a running item in the Runs list of the Zaprex app. Cancelled runs keep their log.

Follow-ups

Ask Zaprex to continue on the same repository after a run, for example to address review comments on its draft PR. A follow-up is a new run that knows about the previous one.

Choosing a model per task

Zaprex runs on Ingot by default. You can pick another allowed model for a task. See Models.