Skip to main content
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.
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.
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.
Workforce: Pod-to-Customer assignments through the API and MCP.

Added

Pods managed by, or under, a customer organization stay invisible to every machine route, and a Customer’s list omits their assignments. See Workforce.
Workforce: pod lifecycle, ownership, internal profiles and worker detail through the API and MCP.

Added

Pods managed by, or under, a customer organization stay invisible to every machine route. See Workforce.