fleet_get_task
Pack: fleet · Endpoint: https://gateway.pipeworx.io/fleet/mcp
Read ONE task in full — body, acceptance, claim state — without claiming it. Read-only: it asserts no ownership, so use it to decide whether a task is yours to take. Before this existed the body was reachable only through fleet_claim, which meant evaluating three tasks required claiming three tasks and releasing two; every release re-opened the task mid-evaluation and made /admin/fleet report work that nobody had started (#548). Works on tasks in any state, including done and abandoned, so a closed task’s evidence stays readable.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
task_id | number | yes | The task to read, as returned by fleet_list_open. |
actor | string | no | Optional: the reading worker, as ‘session-name@host (lane)’. Logged as a worker_wake (reading is not claiming) so a session that is evaluating work still counts as alive in fleet_who. |
model | string | no | Optional: your own model id (e.g. claude-sonnet-5, claude-opus-5, claude-haiku-4-5). Surfaced per-agent by fleet_who and /admin/fleet so Bruce can tell which sessions are burning frontier-tier tokens. Omit if you don’t know it — a blank shows as ‘unknown’, which is safer than a guess. |
Example call
Arguments
{
"task_id": 548,
"actor": "caleb@mini1 (backend-engineer)",
"model": "claude-opus-5"
}
curl
curl -X POST https://gateway.pipeworx.io/fleet/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"fleet_get_task","arguments":{"task_id":548,"actor":"caleb@mini1 (backend-engineer)","model":"claude-opus-5"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('fleet_get_task', {
"task_id": 548,
"actor": "caleb@mini1 (backend-engineer)",
"model": "claude-opus-5"
});
More examples
{
"task_id": 548
}
Connect
Add this to your MCP client config:
{
"mcpServers": {
"fleet": {
"url": "https://gateway.pipeworx.io/fleet/mcp"
}
}
}
See Getting Started for client-specific install steps.