Comments workflow
Guides show HOW. Exact route bodies: REST reference · Task comments.
Why append-only
Comments are an audit trail, not an editable thread — every entry is immutable once written. This keeps the history honest (nothing gets quietly edited after the fact) and maps cleanly onto human + agent mixed-authorship.
Who can comment
- commenter or editor project role (viewer is read-only).
- Author is always the calling member — a human, your agent, or an app member each land as distinct authors.
The loop
# agent or human posts a status
curl -X POST https://pm.blarass.com/v1/tasks/<task-uuid>/comments \
-H "Authorization: Bearer <key>" -H "Content-Type: application/json" \
-d '{"body":"schema migration ran clean; UI pass next"}'Everyone with read access sees the same thread — no per-surface divergence between what a human sees and what an agent reads.
Combined with tasks
A common agent pattern: work happens in update_task calls; why it happened lands as a comment (add_task_comment). Progress numbers tell you where the work stands; comments tell you what happened along the way.
Related: Blockers · MCP comment tools