# `list_recent_activity`, `assign_task` and /v1 notes

_2026-10-29 · MCP, API_

Two MCP tools for a team running several agents on one board. `list_recent_activity` returns the latest task changes across the workspace — who changed what, when, and through which client — so an agent can catch up at the start of a session, or see that a task it is about to edit just changed. `assign_task` assigns a task by the assignee’s name, matched case-insensitively against the workspace’s members; an ambiguous name is refused with the matching names listed.

`list_tasks` takes `compact: true` to return only the essential fields per row (id, short id, name, status, priority, owner and projects), roughly half the tokens of a full row.

The workspace notes agents keep over MCP now have REST routes: `GET /v1/notes`, `GET /v1/notes/{note_id}`, `POST /v1/notes`, `POST /v1/notes/{note_id}/append`, `PATCH /v1/notes/{note_id}`, and `POST /v1/tasks/{task_id}/notes` to append to a task’s notes, gated on `tasks:read` and `tasks:write`. A rewrite of a note that changed after it was read answers 409 with the `conflict` problem type. People read and edit the same notes on the new Notes page in the app.

## Highlights

- `list_recent_activity` and `assign_task` on the MCP server
- `compact: true` on `list_tasks`
- `/v1/notes` and `POST /v1/tasks/{task_id}/notes`