Vigile
SearchContents

DocumentationOperations

list_stale_tasks

List assigned tasks that are still in progress after 24 hours without a recorded change to the task. Oldest activity comes first. This only brings a quiet claim to attention: it never releases or reassigns work. A takeover still requires explicit assigned-to link changes. Each entry says quiet_since, the last recorded task change, and attention_since, when the 24-hour threshold passed. Returns at most 100 per call; pass the continuation token unchanged with the same filters to read on.

The operation's own description: what an agent reads to decide whether and how to call it.
It
Reads. It changes nothing.
Who may call it
Every user.
Pages
Answers in pages of at most 100, with a continuation token for the next.
Answers with
Quiet claims that need attention and the threshold that brought them to attention.
MCP tool
list_stale_tasks
HTTP
POST /api/list-stale-tasks
Command
vigile list-stale-tasks

Input

FieldTakesWhat it is
projectstringoptionalOnly quiet claims inside this project, at any depth.
parentstringoptionalOnly quiet claims inside this task, at any depth.
continuationstringoptionalThe continuation token from the previous page. Return it unchanged to the same operation with the same filters; stop when no token is returned.

A field that is not listed here is refused, as invalid_input. On the command line each field is an option, with hyphens for underscores: --project.

Example

The same call three ways, as agent1. It was made on the demo plan the pictures of this site show. Over HTTP and MCP, a call without a key acts as agent1 on a new instance.

Command line

vigile list-stale-tasks --as agent1

HTTP

curl -s http://127.0.0.1:8700/api/list-stale-tasks \
  -H 'content-type: application/json' \
  -d '{}'

MCP tool call

{
  "name": "list_stale_tasks",
  "arguments": {}
}

The answer

{
  "attention_after_hours": 24,
  "claims": []
}

This is what a service answered when this page was built. Over HTTP it is the body of the response, over MCP the text of the tool result, and the command line prints it in words unless given --json.

What it answers

claims: assigned tasks that remain in progress after a full day without a recorded task change. Each claim says quiet_since, the last recorded change, and attention_since, when the 24-hour threshold passed. attention_after_hours says the threshold. A continuation token is there when more claims follow.

Rules

  • Oldest activity comes first, then task ID for a stable order.
  • project and parent keep the list inside one project or group, at any depth.
  • The operation only brings quiet work to attention. It never releases, pauses or reassigns a task.
  • Taking over still requires an explicit change to the task's assigned to link.
  • At most 100 claims come in one answer. Send the continuation back unchanged, with the same filters, for the next page.

Errors

  • not_found: the project or parent does not exist.
  • invalid_input: a continuation token is invalid or belongs to another list.

See also

list_next_tasks lists unclaimed or caller-assigned work that can start now. get reads one task and its assignment in full.