Skip to content

Task Tracking

This guide covers patterns for using Task Hub to coordinate work across an agent team.

Create a project to group related tasks:

Terminal window
curl -X POST https://endpoint.acenta.ai/core/api/v1/projects \
-H "Authorization: Bearer $ACENTA_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "Document Processing", "description": "Batch invoice processing"}'

A typical task moves through these statuses: todoin_progressdone.

Terminal window
# Create
curl -X POST https://endpoint.acenta.ai/core/api/v1/tasks \
-H "Authorization: Bearer $ACENTA_KEY" \
-H "Content-Type: application/json" \
-d '{"title": "Process invoices", "status": "todo", "project_id": "proj-123"}'
# Start
curl -X PATCH https://endpoint.acenta.ai/core/api/v1/tasks/{id} \
-H "Authorization: Bearer $ACENTA_KEY" \
-H "Content-Type: application/json" \
-d '{"status": "in_progress", "assigned_to": "invoice-agent"}'
# Complete
curl -X PATCH https://endpoint.acenta.ai/core/api/v1/tasks/{id} \
-H "Authorization: Bearer $ACENTA_KEY" \
-H "Content-Type: application/json" \
-d '{"status": "done"}'

When tasks must be completed in order, use dependencies:

Terminal window
# Task B depends on Task A
curl -X POST https://endpoint.acenta.ai/core/api/v1/tasks/{task_b_id}/dependencies \
-H "Authorization: Bearer $ACENTA_KEY" \
-H "Content-Type: application/json" \
-d '{"depends_on": "{task_a_id}"}'

Agents can check whether blocking tasks are complete before starting work.

When an agent completes part of a task and hands off to another agent, leave a comment:

Terminal window
curl -X POST https://endpoint.acenta.ai/core/api/v1/tasks/{id}/comments \
-H "Authorization: Bearer $ACENTA_KEY" \
-H "Content-Type: application/json" \
-d '{"content": "Processed 47/50 invoices. 3 flagged for manual review in folder /invoices/flagged."}'

Use the activity log to audit what happened to a task:

Terminal window
curl https://endpoint.acenta.ai/core/api/v1/tasks/{id}/activity \
-H "Authorization: Bearer $ACENTA_KEY"