Follow-ups

Continue a finished task on the same branch and pull request — from the dashboard, the API, or automatically from review feedback on GitHub.

A follow-up is a new task that continues a finished one. It works on that task's branch — fetching what others pushed to it since, when that fast-forwards — and adds to its pull request instead of opening a second one.

Create one

Dashboard: Follow up on a completed task.
API: send continuesTaskId when creating a task.
GitHub: a review that requests changes can create the follow-up by itself; see review feedback.

Terminal

curl -X POST "$AO_SERVER/api/v1/orgs/$AO_ORG/tasks" \
  -H "Authorization: Bearer $AO_TOKEN" -H "Content-Type: application/json" \
  --data '{
    "projectId": "prj_123",
    "continuesTaskId": "tsk_123",
    "title": "Address review",
    "prompt": "Rename the helper and add the missing test."
  }'

With CI checks as verification, a fix after failed checks joins the same branch and pull request in the same way, without a new task.

Based on docs/operations/README.md in the core repository (v0.2.10).

Create one

Dashboard: Follow up on a completed task.
API: send continuesTaskId when creating a task.
GitHub: a review that requests changes can create the follow-up by itself; see review feedback.

Terminal

curl -X POST "$AO_SERVER/api/v1/orgs/$AO_ORG/tasks" \
  -H "Authorization: Bearer $AO_TOKEN" -H "Content-Type: application/json" \
  --data '{
    "projectId": "prj_123",
    "continuesTaskId": "tsk_123",
    "title": "Address review",
    "prompt": "Rename the helper and add the missing test."
  }'

With CI checks as verification, a fix after failed checks joins the same branch and pull request in the same way, without a new task.