- An External App or a platform key can ask 1 to 25 named people for a decision or input with Ask a person. It declares its own form and a due date from 15 minutes to 14 days. It reads the outcome with Read one of your asks and cancels an open ask with Withdraw one of your asks. People answer in the Forge Console, Slack or email. Software never answers a human task.
- The new permission
human_tasks:use(Run family, not elevated) lets software ask. No preset or default role includes it. An operator gives it through a role, and an app’s token must also name it in itsscope. A grant reaches only the people homed under the unit it covers. - A person may take one of the app’s actions only while holding the app’s non-elevated eligibility permission at the task’s home. Anyone asked may decline. Asks are capped at 200 open per requester, 10 open per person asked, and 200 created per 24 hours (10 per person asked); a breach of a 24-hour cap answers
429withRetry-After. - Every surface names who asked, for example
Requested by the External App “Vendor desk”, and says “Forge never asks for passwords or codes in a request.” Email for these tasks shows links in the app’s text inert (hxxps://example[.]com). - Through a Personal key, an app’s task is summary-only and decline-only: the reads show fixed copy and no form, and every declared action is refused with the task’s Console link.
- An External App hears its own asks through the
human_task.completedandhuman_task.canceledwebhooks, which carry ids only. Admin subscriptions see these ids for every app. A platform key, or an app whose grant covers only a sub-unit, polls instead. No webhook is sent when an ask closes because its requester can no longer ask.
Idempotency-Key. A completed turn or a failure after dispatch keeps the key spent.- An agent node placed detached (a declared timeout above 8 minutes, so it runs in a sandbox VM) no longer waits up to 2 minutes for an answer. Its
human_askreturnsstatus: "pending"at once, as an inline node’s does. When its turn ends, the VM stops and the node pauses: it holds no agent slot, no VM and no timer reaps it. - When every question the node asked has closed, it resumes on the same conversation in a new VM turn with a fresh timeout. Each answer arrives as a Forge notice. The resumed turn replays earlier messages’ final text, not earlier tool calls or their results, and the agent is told to call its tools again for anything it needs.
- For a detached node,
human_checkandhuman_withdrawreport a question’s status without its answer. - A node can pause at most 5 times per attempt. Each paused turn’s spend counts toward the run’s cost cap as it happens.
- A value a person supplied to a step, such as a human node’s answer passed downstream, is no longer pasted into an agent node’s opening prompt. The prompt refers to the input by name. The value arrives in a fenced Forge notice, after a Forge line that the Console shows as Forge, not as the person. This applies to inline and detached nodes and to debug attempts.
- An agent node already running in a VM when this change shipped keeps the 2-minute wait until it ends.
- When a Foreman plan’s or request’s approval is voided, every running or paused
sdlc-implement-taskrun launched for it is cancelled, however many runs the workflow has. A run started after the void is cancelled too, unless a person has approved the plan or request again. - The approval check on an
sdlc-implement-tasklaunch reads the inputs the run stores, including input defaults. A default that names a plan or request needs that plan or request to be approved. - A launch without the launch permission, or with inputs the workflow’s contract rejects, now reports that error before
FOREMAN_APPROVAL_REQUIRED.
- A human node’s answer that reaches an agent node or an LLM router through a procedure node, whether the procedure is connected to the human node or reads its answer or failure context as one of the procedure’s inputs, or through an input wired to a failed node’s failure context, is no longer pasted into the prompt. The prompt refers to the input by name, and the value arrives in a fenced Forge notice.
- An LLM router that has run 50 or more times again receives inputs that came from no person whole, in its prompt, with no notice.
- The value in a fenced Forge notice is one line: line breaks become spaces, and a value over 4,000 characters is cut and ends in
…. Other inputs reach the prompt whole. - Correction to the 2026-10-18 note on detached agent nodes: only inputs wired from a step a person completed, such as a human node’s answer, move to the notice. Values a person supplies when launching a run, such as workflow inputs and
{{workflow.x}}, are still placed in the prompt. - When a Foreman plan’s or request’s approval is voided, a run is cancelled even when it stored the plan or request id in a different accepted form.
forge_search_knowledge. Kind selection preserves existing scope and source access checks
and returns the existing empty result when a known kind has no searchable matches.GET /api/v2/providers/listAuditEvents (forge_list_provider_audit_events) lists a provider’s
recent changes with audit:read at the platform scope: event, category and time, never the actor or
the option diffs. GET /api/v2/capabilities/getBindingReadiness
(forge_get_capability_binding_readiness) reads a bindable capability’s provider binding for one
organization with credentials:read there, never a credential id, field or secret. Binding
readiness, in the API and the Console, now finds an organization’s own binding however many
organizations the capability binds./api/v2/knowledge/synchronized-sources/* and the corresponding
forge_*_synchronized_source* tools. SDK callers replace listKnowledgeSources with
listSynchronizedSources, getKnowledgeSource with getSynchronizedSource,
listKnowledgeSourceRuns with listSynchronizedSourceRuns, updateKnowledgeSource with
updateSynchronizedSource, listKnowledgeSourceProviders with
listSynchronizedSourceProviders, createKnowledgeSource with createSynchronizedSource,
removeKnowledgeSource with removeSynchronizedSource, relistKnowledgeSource with
relistSynchronizedSource, and requestKnowledgeSourceSync with
requestSynchronizedSourceSync. Retries through the canonical HTTP routes keep the persisted
idempotency identity created during the compatibility interval./knowledge/synchronized-sources; bookmarks to the
old Console route redirect there. Integrations can use the canonical
/api/v2/knowledge/synchronized-sources/* routes and forge_*_synchronized_source* MCP tools.
The previous HTTP and MCP names remain compatibility aliases until their containing release has
given callers one release to migrate. See synchronized knowledge sources.
