> ## 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-05 — Forge hosts and procedure approval guarantees

> Forge purpose hosts and API path aliases; approved procedure holds are spent once under the launcher's current authority, and run trust status reports their continuation.

**2026-10-05**

Held procedure nodes get the agent-node spend-once and launcher re-check.

## Summary

When an eligible person approves a Trust Fabric hold on a **procedure** node of a workflow run, the approval is now spent exactly once, by one dispatch attempt, and only while the External App that launched the run still holds its launch authority. This is the guarantee agent nodes already had; this release extends it to procedure nodes. No new scope, permission or refusal code.

## Changed

* Rerunning an approved procedure node needs a new approval. The approval authorizes one dispatch attempt; a second pass in the same attempt is refused `approval_spent`.
* A run launched with a `platform-key:` credential is refused after approval (`original_actor_unauthorized`), as are runs whose External App was deactivated, lost `workflows:use`, or no longer covers the workflow's home. The refusal happens before any effect: the invocation is never opened and no sandbox starts.
* `GET /api/v2/runs/getTrustStatus` and `forge_get_run_trust_status` now report `continuation` for a procedure-node hold (`awaiting_decision`, `released`, `dispatched` or `refused`) instead of `null`. `effect` is `not_recorded` unless the run records effect evidence. See [Get run hold status](https://docs.gloo.com/forge/reference/http-api/runs/getTrustStatus.md).

## Deploy note

An approval approved but not yet spent before this deploy can be used once more by the next dispatch of that node; from then on it is spent.

**2026-10-05**

Purpose hosts for the API, inbound hooks and MCP, and the version in the path.

## Summary

Forge gives each kind of caller its own address: `api.forge.gloo.com` for the HTTP API, `hooks.forge.gloo.com` for capability URLs and inbound webhooks, and `mcp.forge.gloo.com` for MCP hosts. The staging equivalents under `forge.staging.gloo.us` are pending DNS, certificate verification and activation; use the existing staging deployment addresses until they are verified. Every existing address keeps working: the deployment's `*.convex.site` origin, `/api/v2/...` paths and `forge.gloo.com/api/mcp`. See [Conventions → Base URL](https://docs.gloo.com/forge/reference/conventions.md#base-url).

## New

* Every `/api/v2/<path>` route is also served at `/v2/<path>`, with the same authentication, permission check and refusals. One `Idempotency-Key` covers both spellings: a retry that switches spelling replays the original response. `/v2/ingress/wht_<token>` reaches the same ingress trigger. The OpenAPI spec and Forge's clients keep `/api/v2`.
* The hosted MCP endpoint is served at `https://mcp.forge.gloo.com/mcp`, with its own RFC 9728 resource (`https://mcp.forge.gloo.com`) and metadata at `/.well-known/oauth-protected-resource`. The MCP host shows no Console page, and the endpoint never sets or reads a cookie. See [Hosted endpoint](https://docs.gloo.com/forge/reference/mcp-server.md#hosted-endpoint).
* `buildHostedHostConfig` (`@tangogroup/forge-mcp`) accepts `mcpOrigin` in place of `consoleUrl` and emits `<mcpOrigin>/mcp`.

## Changed

* Interactive MCP sign-in belongs to the MCP host. Where one exists, the metadata for `forge.gloo.com/api/mcp` names no authorization server; that path keeps accepting MCP keys, platform API keys and External App tokens.
* The Console shows new ingress capability URLs and SendGrid Inbound Parse and Event Webhook URLs on the hooks host once it is configured. URLs already issued keep working.
* The committed OpenAPI spec lists the verified production server, `https://api.forge.gloo.com`, instead of a templated `*.convex.site` host. Staging is omitted while its purpose hosts are pending.


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