# Notice when a human comments or changes a task the agent owns

> Notice when a human comments or changes a task the agent owns: 1 companies fully do it, 16 with a limit, 15 carry the tag. Every listing in Project & task management with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/project-management.watch-for-changes/
- Markdown: https://www.anchorterminal.com/niches/project-management.watch-for-changes/index.md (~1,600 tokens)
- Slim: https://www.anchorterminal.com/niches/project-management.watch-for-changes/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/project-management.watch-for-changes/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 16 | 15 | 6 | 3 |

## What counts as done

A change or comment made in the web app reaches the agent as an event, with the task id and the changed field, and missed events can be replayed or re-synced.

Measured, for our own tests: the event arrives within a minute.

How agents ask for it: tell me when the client replies on the ticket; pick up work when someone moves a card to Ready; keep my index in sync with the board

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Taiga (Taiga Cloud Services, S.L.)**: Webhooks fire on create, change and delete with a change diff, and /webhooklogs lists deliveries with a resend endpoint, so missed events can be replayed; the setup is per project.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Asana (Asana, Inc.)**: REST webhooks deliver task and comment changes, on average within a minute, but delivery is at-most-once with no replay, MCP has no event route, and task changed events stopped for a week in acc-43.
- **Basecamp (37signals LLC)**: Webhooks fire for to-do, comment and other recording events with up to 10 attempts and inspectable delivery records, and basecamp connect watches for an agent's work, but no replay or sync-token route is documented.
- **ClickUp (Mango Technologies, Inc. DBA ClickUp)**: REST webhooks cover task and comment events with five retries per event, after which the event is dropped and fail_count rises; no replay is documented and MCP has no event route.
- **monday.com (monday.com Ltd.)**: GraphQL webhooks fire on column changes, status changes, item moves and new updates, retrying once a minute for 30 minutes; no replay is documented and MCP has no event tool.
- **ONES (The Beautiful ONES Technology PTE. LTD.)**: Plugin apps can subscribe to issue created, updated, status-changed and deleted events by HTTP callback, but replay or missed-event recovery isn't stated in the index and MCP has no event route.
- **OpenProject (OpenProject GmbH)**: Admin-configured webhooks fire on work package, comment, project, time entry and attachment create and update, per project, but no retry, replay or missed-event guidance is documented.
- **Plane (Plane Software, Inc.)**: v2 webhooks carry event_id, previous_attributes diffs and PQL filters, with retries over five attempts, but there is no manual retry or replay and events aren't queued while disabled.
- **Redmine (Redmine project)**: Redmine 7 sends issue webhooks with the update's journal, but WebhookJob calls the hook once with no retry or replay found in the source, and the wiki API page doesn't document them.
- **Roma (Milo Mode Inc.)**: list_items changedSince is a changes feed including trashed items, and wait_for_item holds up to 25 seconds for news on one item, but this is polling, not a push event with the changed field.
- **Shortcut (Shortcut Software Company)**: Outgoing webhooks send story changes with the changed fields, and story history is readable through /stories/<id>/history for re-sync, but no retry or replay policy is documented and an incident delayed webhooks on 19 October 2026.
- **Taskade (Taskcade Inc.)**: Signed webhooks cover six events (task.due, task.assigned, comment.created and three project events), so completions and field edits need automation triggers; no retry or replay is documented.
- **Teamwork.com (Teamwork Crew Limited)**: Webhooks can be set at site or project level on paid plans, but the setup guide states no retry, replay or missed-event recovery, and the MCP has no event route.
- **Todoist (Todoist Inc.)**: Webhooks send item and note events with the changed entity and a delivery id, retried up to three times 15 minutes apart, and the Sync API's sync_token re-syncs missed changes, but delivery can be 45 minutes late, past the one-minute bar.
- **Trello (Trello, Inc.)**: Webhooks fire per model on card updates and comments with the action data, retrying three times with backoff, but there is no replay; acc-56 dropped Trello because replies needed manual refresh.
- **Wrike (Wrike, Inc.)**: Webhooks send events such as TaskStatusChanged with old and new values and CommentAdded, and can be suspended or resumed, but no retry or replay of missed events is described.
- **YouTrack (JetBrains s.r.o.)**: There are no native webhooks; an administrator writes an on-change workflow rule that makes outbound HTTP requests, with no replay, and MCP has no event route.

- not this job: Financial Cents MCP (Financial Cents LLC): No webhook, event or changed-since tool appears among the 40 MCP tools in the guide.

## What stops agents finishing

- task-level changed events stop silently while story events still arrive
- no event stream, so the agent polls and misses human edits

## Around it

Before: project-management.coding-agent-ticket-loop. After: project-management.update-tasks, notifications.push.

## Where this comes from

Weight 6 of 100 in Project & task management: 3 of 58 accounts (an Asana change-event outage, a ClickUp user indexing via webhooks, a builder who dropped in-ticket conversation because issues needed refreshing); weight lifted above its count because change events are a buyer check.

As data: https://www.anchorterminal.com/api/v1/use-cases/project-management.watch-for-changes.json, or the MCP tool get_use_case with id project-management.watch-for-changes. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
