> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pomerado.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Follow builds as tasks

> Clients that support the MCP Tasks extension get a build back as a task to follow.

A client that supports the MCP Tasks extension gets a build back as a task, which it follows with its own task calls instead of `get_job`.

## Negotiate tasks

The client sends MCP protocol version `2026-07-28` and declares the `io.modelcontextprotocol/tasks` extension in its client capabilities. Then a build call, such as `build_website_tool`, returns a task instead of the job. Runs return the job as usual.

The task's `taskId` is the job's `job_` ID, so `get_job` still works on it.

## Follow the task

| Task call | What it does |
| - | - |
| `tasks/get` | Reads the task: `working`, `input_required`, `completed` or `cancelled` |
| `tasks/update` | Answers the question the task asks |
| `tasks/cancel` | [Cancels the job](/guides/jobs/cancel) |

A task that needs input carries an elicitation request. A plain question comes as a form. A secret, a login or a saved login to correct comes as a link to a protected Pomerado page, so the value never passes through the client. See [answer questions](/guides/jobs/answer-questions).

## Read the result

A completed task's result is the [job object](/guides/jobs/job-object), marked as an error unless the job succeeded. Reading it counts as the result's one read, as described in [results are read once](/guides/jobs/wait-for-a-result#results-are-read-once).

<Note>
  A completed task doesn't mean the build succeeded. Check the job's `status`, `error` and `write_status` as you would for any job.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.