Governance
List my open work
List my open work. Requires a Personal key and permission approvals:read.
GET
List my open work
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.
v2 compatibility notes
Lists the open human workflow steps and pending approvals that ask the Personal key’s owner — the Forge Console My Work list — breached SLAs first, then by SLA deadline, then oldest first. It also lists the review-queue items the owner may decide (kind: "human_task"): the synthesis queue, held
procedure drafts, judge panel admissions and curator recommendations. Each item’s humanTaskId opens it with
getHumanTask; a human_node item’s id is
the step’s node run, which listHumanTaskInputFiles
takes.
Who can call it
Call it with a Personal key. It reads as the key’s owner, the person who created the key, never as anyone the request names. A platform key or an External App has no work of its own: it gets403 with error.personRequired: true, and no grant changes that. The
owner’s grants, narrowed to the key’s scopes, must hold approvals:read. See
Person-relative reads.
Review-queue items
A review-queue item is a group human task. It asks everyone who holds the queue’s permission at the platform scope now —synthesis:approve for the synthesis queue, judge admissions and curator
recommendations, approvals:approve for held procedure drafts — and is an active person with an email.
The owner’s grants are narrowed to the key’s scopes, so a key whose scopes do not reach the queue’s
permission lists none of that queue. Every open item of a queue is listed, across pages, so no item
carries queueOverflow. A review-queue item’s
slaDeadlineAt is null. Take it over with
reassignHumanTask and kind: "human_task".
Paging
Every item is listed: page withlimit (1 to 100, default 100) and cursor, following
meta.nextCursor while meta.hasMore is true. The list is read from the owner’s own index: the
steps and approvals that ask them, oldest first, then each review queue whose permission they hold.
Other people’s work is not read, so the first page holds the owner’s oldest items up to limit.
Each page is sorted like the Console list. A page can hold fewer items than limit while
meta.hasMore is true.
Each item is listed once per walk. An item that starts asking the owner after you have paged past
its place appears the next time you list from the start.
While Forge is still indexing work that existed before the owner index (a deployment’s one-time
backfill, or a re-check that finds an item missing from the index), a listing reads every open step
and approval and keeps the owner’s. Then a page can hold fewer items than limit, or none, while
meta.hasMore is true, and a step that escalates while you page can appear on two pages. A
listing that starts in one mode finishes in it.
Example
Authorizations
A Personal key (fmcp_…), bound to the person who created it, or an interactive MCP sign-in that resolves to one. Pass as Authorization: Bearer <key>. It acts for that person, under their role grants narrowed by its scopes; an operation that acts for a person admits only this kind.
Query Parameters
Response
One page of the owner's open work

