pending
Count open tasks, active anti-patterns, notes, handoffs, and diagrams in a scope, or page through their headers. Filter by type, domain, offset, or pinned to see what still needs action.
Instructions
What is still open in a scope: counts per category, or one category's headers.
Without type: {"categories": [{"type", "count"}, ...]} for task,
anti_pattern, handoff, note and diagram, in that order, leaving out the
empty ones, plus "pinned" -- the same shape, counting the memories a
person pinned as mandatory reading -- when any pin is in scope. A pinned
memory still counts in its category. With type: {"type", "total",
"items", "next_offset"} -- one page of headers (uid, title, domain,
est_tokens; a task adds progress {done, total} and doing, the keys of
its items in progress), newest first, a task by its latest item update.
Open a header with get_memory(uid). next_offset is absent on the last
page.
pinned=true narrows the page to the pins of that type, and also accepts checkpoint and reasoning. Every pin listed is read with get_memory(uid) before acting, none skipped.
Pending means: a task that is open; an active anti_pattern, handoff or note that is not contradicted; an active diagram.
domain covers its subdomains and what is cross-listed there; empty is the whole project. A pin is in scope when it is global, or when the memory's domain or one of its also paths is the asked domain or above it; the whole project counts global pins only. limit is 1 to 50. Any other type is an error.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | ||
| limit | No | ||
| domain | No | ||
| offset | No | ||
| pinned | No |