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

# 2026-10-14 — Human tasks: v2 forms only, canceled questions, and what each surface approves

> An open human task is answered only on its pinned v2 form, human_check reports an unanswered closed question as canceled, and each surface approves in place only what it can show.

**2026-10-14**

Trust Fabric: if you have the rights to approve, you can approve.

## Risk no longer requires someone else to approve

A financial-risk tool call, a procedure exposed through one, and a destructive, network-egress or privileged sandbox command are now released like any other hold: whoever holds `approvals:approve` and the permissions the held action needs may release it, including the person who asked for the work or owns the agent. The release is recorded as self-released. A hold raised before this change keeps its stored policy, so it still needs someone else; once released, its call is held again under the new rule. Approving any of these holds still needs a signed-in Forge Console session, and a Slack or email approval of an agent tool's hold checks the tool's risk as it is when you decide. See [Approval lifecycle](https://docs.gloo.com/forge/run/approvals-and-hitl.md#approval-lifecycle).

**2026-10-14**

Human tasks, Increment 2 cleanup: open tasks need their v2 form, and the expired alias is gone.

## Summary

Every open human task already carries the form it was asked on. The one-release fallback that kept an open task without that form answerable is now removed. A closed task's history still reads exactly what it recorded.

## Breaking (agent authors)

* `human_check`, `human_ask` and `human_withdraw` return `status: "canceled"` with its `cancelReason` (`due_date`, `declined`, `run_ended`, `superseded` or `withdrawn`) for a question that closed without an answer. The one-release `expired` alias is removed. An agent that tested for `"expired"` tests for `"canceled"`.

## Changed

* An open human task is answered only on its pinned v2 form. An open task without one is not presented, and an answer to it is refused with `action_not_declared`; a person can still say "Not me" in Forge Console. No open task in staging or production lacks its form.

**2026-10-14**

Human tasks, Increment 2 hardening 3: what each surface approves in place, answers as Forge notices, and inert Slack run threads.

## Approve in place only what the surface shows

* Every kind of human task follows the rule that hold approvals already followed: a surface that cannot show what is being decided links out with "Approve in Forge". Reject stays in place.
* A workflow human step links out on the Slack card, Slack Home, `/forge approvals` and email when it has inputs from prior steps or a decision briefing. Forge Console shows those inputs above the step's form.
* A synthesis confirmation, an Architect plan or an agent setup is confirmed only in Forge Console.
* A task whose title, summary or detail is too long for the surface links out. A long title shows in full beneath the card's header.
* An approve from Slack Home is checked against what Home shows, not against the card.

## An agent's question is answered as a Forge notice

* A chat agent's `human_ask` answer reaches the agent as a Forge notice in its conversation. The notice names the person and the `requestId` and quotes the answer as fenced text. The agent's next turn starts from a fixed Forge message that names only the `requestId`. Act on the notice as the person's answer.
* A rejected hold's reason reaches the agent the same way, marked as untrusted text.
* Forge Console shows each notice as a Forge row and never shows the turn-starting message.
* The public `listMessages` API returns the notice as an `assistant` message that starts with `[Forge notice]`, and the turn-starting message as a `user` message that starts with `[Forge]`.

## Slack

* Workflow run threads post step names, inputs, outputs, errors and skip reasons as plain text. A `<!channel>`, a mention or a link inside them no longer acts. A link is posted only for a plain `http(s)` URL.
* A click on a retired workflow-step card whose step is still waiting says the card is out of date and links to the task in Forge.
* An approval with an SLA window is marked breached when the window passes, even when nothing else happens to it.

**2026-10-14**

Workforce: Pod-to-Customer assignments through the API and MCP.

## Added

* Six Pod-to-Customer assignment writes under the existing scope `workforce:write:pods` (`workforce:manage` at the platform scope, plus the `workforce:read` scope): [Assign pod customer](https://docs.gloo.com/forge/reference/http-api/workforce/assignPodCustomer.md), [Change pod customer assignment effective](https://docs.gloo.com/forge/reference/http-api/workforce/changePodCustomerAssignmentEffective.md), [Update future pod customer assignment](https://docs.gloo.com/forge/reference/http-api/workforce/updateFuturePodCustomerAssignment.md), [Delete future pod customer assignment](https://docs.gloo.com/forge/reference/http-api/workforce/deleteFuturePodCustomerAssignment.md), [End pod customer assignment](https://docs.gloo.com/forge/reference/http-api/workforce/endPodCustomerAssignment.md) and [Confirm pod customer assignment accuracy](https://docs.gloo.com/forge/reference/http-api/workforce/confirmPodCustomerAssignmentAccuracy.md). Each runs the Console's own command, and a same-key retry is replayed under the pod write rule.
* [Preview pod customer assignment](https://docs.gloo.com/forge/reference/http-api/workforce/previewPodCustomerAssignment.md) under the same key, and three reads under `workforce:read` at the platform scope: [List pod customer assignments](https://docs.gloo.com/forge/reference/http-api/workforce/listPodCustomerAssignments.md), [List customer pod assignments](https://docs.gloo.com/forge/reference/http-api/workforce/listCustomerPodAssignments.md) and [List pod customer assignment history](https://docs.gloo.com/forge/reference/http-api/workforce/listPodCustomerAssignmentHistory.md). None needs `customers:read`.
* Matching MCP tools in the `workforce` group.

Pods managed by, or under, a customer organization stay invisible to every machine route, and a Customer's list omits their assignments. See [Workforce](https://docs.gloo.com/forge/reference/http-api/workforce#pod-customer-assignments).

**2026-10-14**

Workforce: pod lifecycle, ownership, internal profiles and worker detail through the API and MCP.

## Added

* Eight pod administration writes under the existing scope `workforce:write:pods` (`workforce:manage` at the platform scope, plus the `workforce:read` scope): [Create pod](https://docs.gloo.com/forge/reference/http-api/workforce/createPod.md), [Update pod](https://docs.gloo.com/forge/reference/http-api/workforce/updatePod.md), [Archive pod](https://docs.gloo.com/forge/reference/http-api/workforce/archivePod.md), [Assign pod owner](https://docs.gloo.com/forge/reference/http-api/workforce/assignPodOwner.md), [Change pod owner effective](https://docs.gloo.com/forge/reference/http-api/workforce/changePodOwnerEffective.md), [End pod owner](https://docs.gloo.com/forge/reference/http-api/workforce/endPodOwner.md), [Set pod internal profile](https://docs.gloo.com/forge/reference/http-api/workforce/setPodInternalProfile.md) and [End pod internal profile](https://docs.gloo.com/forge/reference/http-api/workforce/endPodInternalProfile.md). Each runs the Console's own command, and a same-key retry is replayed under the pod write rule.
* Three reads under `workforce:read` at the platform scope: [List pod owners](https://docs.gloo.com/forge/reference/http-api/workforce/listPodOwners.md), [List pod internal profiles](https://docs.gloo.com/forge/reference/http-api/workforce/listPodInternalProfiles.md) and [Get worker](https://docs.gloo.com/forge/reference/http-api/workforce/getWorker.md). Get worker never returns the owner's email, metadata, agent configuration, budget or spend.
* Eleven matching MCP tools in the `workforce` group.

Pods managed by, or under, a customer organization stay invisible to every machine route. See [Workforce](https://docs.gloo.com/forge/reference/http-api/workforce#pod-lifecycle-ownership-and-internal-profiles).


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