> ## 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-17 — Forge updates

> Trust Fabric's Permissions tab opens with the catalog's four key numbers and shades every permission by how many roles include it, marking elevated permissions and the ones an agent may never hold. The Access page's permission grid lights up for a chosen role, for your own access at a scope, or for what an agent can hold, and a panel explains any permission you choose. The Access page's Enforced tile filters the permission grid to the permissions no enforcement site checks yet, and a Roles tile links to the Roles tab. The Factories Codebase page lists indexed files 500 chunks at a time with Load more, so a large index no longer fails the page. A coding-agent VM reaches github.com only, and a held merge shows its repository, PR and commit and needs a person. Every request Forge sends with a credential to a configured URL refuses a redirect to another origin before anything is sent there. GET /api/v2/workflows/listDebugFiles omits a file whose companies the caller may not use workflows in, as the download does. An SDLC factory's Foreman agent can no longer approve its own work; factories:manage holders decide in My Work. linkPersonIdentity and forge_link_person_identity link a Freshservice technician to a person from a synchronized Freshservice Knowledge source. A voided request voids its plan's approval, restarts are gated, and demote feedback is fenced. Creating a synchronized knowledge source schedules its first sync at once instead of waiting for the five-minute dispatcher, and the Console says so. A procedure's network call that carries its own session token as written is refused before it is sent. The secrets_store capability is no longer reachable from a procedure or agent session, whatever the procedure's manifest declares. GET /api/v2/runs/getMarkdown cuts a transcript at the read reserve and says partial instead of answering 500. Slack, GitHub project sync and Vercel sandbox requests refuse a redirect to another host. Synthesis templates, the synthesis budget and the JIT synthesis default are readable and writable over the Platform API and the Forge MCP server. Requests Forge sends with a key to a fixed vendor API also refuse a redirect to another host, and the Google model catalog key moves out of the URL.

**2026-10-17**

The Access page shows who can do what at a glance.

The Permissions tab of **Trust Fabric → Access** (`/trust-fabric/access`) opens with four numbers:
the permissions in the catalog, how many are elevated, how many an agent may never hold, and the
share Forge checks somewhere. The grid below is compact, with the five verbs beside each resource
and each family as a colored band. Every cell prints how many roles include the permission and is
shaded to match. An amber ring marks an elevated permission, a robot with a slash marks one an
agent may never hold, and a verb a resource lacks is left blank. See
[Access](https://docs.gloo.com/forge/console/trust-fabric/access#permissions).

**2026-10-17**

Access lenses and the permission panel.

The Permissions tab of **Trust Fabric → Access** adds four lenses above the grid. **All roles**
shades each permission by how many roles include it. **A role** lights what one role includes, and
**Your access** lights what you can do at a scope you choose, including permissions that scopes
narrow or a ceiling caps. **What an agent can hold** marks the elevated permissions an agent may
never hold. Choosing a cell opens a panel beside the grid with what the permission means in the
lens, the roles that include it, where Forge checks it and who holds it. The lens and the open
permission are kept in the address, so a link shares the view. See
[Access](https://docs.gloo.com/forge/console/trust-fabric/access#permissions).

**2026-10-17**

Access: the not-checked filter and the Roles tile.

The numbers above the grid on **Trust Fabric → Access** are now Permissions, Elevated (which
agents may never hold), Roles and Enforced somewhere. **Only the … not checked** under Enforced
narrows the grid to the permissions no server function, Console page or table checks yet; the
filter is kept in the address so a link shares it. The Roles tile links to the Roles tab. See
[Access](https://docs.gloo.com/forge/console/trust-fabric/access#permissions).

**2026-10-17**

The Console codebase file list loads in pages.

The **Codebase** page under Factories lists indexed files 500 chunks at a time, with **Load more**
for the rest, instead of reading up to 5,000 at once, which a large index could push past the
database's per-request read limit and fail the page. A file whose chunks span two loads is shown
once with all of its chunks counted. `GET /api/v2/factories/listCodebaseFiles` is unchanged.

**2026-10-17**

Coding-agent egress and merge approvals.

A coding-agent run's VM now reaches `github.com` for git only, never GitHub's API. Forge opens the pull request and reads its checks itself, so nothing in a run changes, but the agent inside the VM can no longer merge a pull request with the platform token.

When an agent's merge waits for approval, the approval now shows the repository, the pull-request number and the exact commit it would merge. Only a person can approve it; an External App cannot.

Published workflows behave as before.

**2026-10-17**

Credentials never follow a redirect off their host.

When Forge sends a credential to a URL you configure, it now follows a redirect only while the
redirect stays on the same scheme, host and port, and refuses any other redirect before anything is
sent there. This covers tool calls, inference provider and gateway calls, connection tests and
credential verification, OAuth code exchange, revocation and identity lookup, environments, secrets
stores (1Password Connect, HashiCorp Vault), Splunk export, embeddings, and the project management,
source control and Rippling providers.

If a provider you configured redirects to another host (for example from a bare domain to a
regional API host), the request now fails; configure the final host as the base URL instead.

**2026-10-17**

A debug attempt's file list leaves out files you may not download.

`GET /api/v2/workflows/listDebugFiles` (and `forge_list_workflow_debug_files`) now leaves out a file
that carries a company the caller does not hold `workflows:use` at, the same rule
`getDebugFileUrl` already applied to its download, and a file whose record no longer exists. A key
could previously see such a file's name, type and size in the list without being able to download it.

**2026-10-17**

Foreman approvals come from a person.

An SDLC factory's Foreman agent can no longer approve its own plans or requests. When it moves one to awaiting approval, everyone who holds `factories:manage` at the platform is asked in [My Work](https://docs.gloo.com/forge/console/my-work.md#foreman-approvals), and only a person's Approve moves it on. A move into an approved state without that decision is refused with `FOREMAN_APPROVAL_REQUIRED`. An approval is voided when the plan or request is sent back or edited in GitHub or Linear.

A Personal key decides it through `completeHumanTask` like any human task, when its scopes reach both `approvals:approve` and `factories:manage`; human tasks of kind `foreman_approval` appear in `listMyWork` and `getHumanTask`.

**2026-10-17**

Freshservice identity links over the Platform API.

`POST /api/v2/workforce/linkPersonIdentity` and the `forge_link_person_identity` MCP tool now link
Freshservice identities, which were previously refused. Send `provider: "freshservice"` with the
synchronized Freshservice Knowledge source (`freshserviceSourceId`), the org unit it is homed at
(`orgUnitId`) and the technician (`technicianId`). As in the Console, you need `knowledge:read` at
that org unit, and the identity is derived from the source's account, so the API and the Console
link the same identity for the same technician. See
[Link person identity](https://docs.gloo.com/forge/reference/http-api/workforce/linkPersonIdentity.md).

**2026-10-17**

Foreman approvals follow the request they cover.

* An approved Foreman plan stays approved only while its request does. When a person rejects the request, or it moves to `pending` or `won't_do`, the plan goes back to `planning` and the Foreman must submit it again. A change to the request's title, description, risk tier or priority asks a person again.
* Running `sdlc-implement-task` runs launched for a plan or request whose approval was voided are cancelled.
* Restarting an `sdlc-implement-task` run needs the plan or request to be approved now. Otherwise [`POST /api/v2/runs/restart`](https://docs.gloo.com/forge/reference/http-api/runs) answers a 409 naming `approval_required`, and `forge_restart_run` returns the same reason.
* GitHub and Linear send a request's priority only when the issue's priority changes.
* When a person demotes a synthesized primitive, agents see only a fixed code and the reviewer's feedback in a fenced, attributed notice. They never see the raw text.

**2026-10-17**

A new knowledge source starts syncing as it is created.

Creating a synchronized knowledge source, in the Console or over `POST /api/v2/knowledge/sources/create`,
now schedules its first sync in the same step, audited as `knowledge_source_sync_requested` by
whoever created it. It no longer waits up to five minutes for the next dispatch. The dispatcher
still finds the source due, and the run it schedules starts nothing while the first run holds the
source, so a source never has two runs. Until the first run begins, the source drawer shows
**First sync queued**; the sources table shows **First sync started** until a run finishes. See
[External knowledge sources](https://docs.gloo.com/forge/knowledge/external-sources.md#sync-interval-and-runs).

**2026-10-17**

network.fetch refuses a call that carries a procedure's session token.

A procedure's `network` capability call is refused with `CAPABILITY_DENIED` when its URL, headers
or body contain the procedure's own session token as written, the bearer the procedure uses to call
back into Forge. Nothing is sent, the refusal is recorded on the run, and the record never stores the
token. This catches a token sent by mistake; it cannot stop procedure code that encodes the token
before sending it, and it does not cover a procedure's direct egress to its own allowlisted hosts.
Network calls carry only what the procedure itself sends; Forge adds no credential to them.

**2026-10-17**

Procedures and agents cannot read secrets by id.

A procedure or agent session can no longer call the `secrets_store` capability, even when the
procedure's manifest lists it in `capabilities`, and it can call only the operations Forge admits for
each capability: `network.fetch`, the file routes, the `knowledge` reads, typed judgments and the
project-management task and project operations. Operations that would return a platform credential,
such as an inference provider's route or a source-control token, are never reachable. Such a call is refused with `CAPABILITY_DENIED`
before anything is read, so knowing a secret's id never lets a procedure resolve, rotate, store or
revoke it. Procedures keep using vendor credentials as before, through their connections: the
sandbox applies a credential to a request for its own host without the procedure ever holding the
value. No published procedure in production or staging declared `secrets_store`.

**2026-10-17**

Run Markdown export stops a long transcript instead of failing.

`GET /api/v2/runs/getMarkdown` (and `forge_get_run_markdown`) bounds each read of a step's
transcript to the read room the request has left, and stops the transcript when that room runs out. A run
whose transcripts are larger than one request can read now returns the Markdown it could read with
`meta.partial: true` instead of a `500`.

**2026-10-17**

Slack, project sync and sandbox credentials stay on their hosts.

Slack messages, file transfers, OAuth installs and token refreshes, the GitHub project board sync, and
Vercel sandbox requests no longer follow a redirect to another host. A redirect within the same host
still works; a redirect elsewhere fails the request before the bot token, OAuth client secret, GitHub
token or Vercel token is sent there. No configuration changes.

**2026-10-17**

Synthesis settings over the Platform API.

Eight routes under `/api/v2/synthesis/*` manage what the Console's Synthesis Settings and
Synthesis Templates pages manage: list, create, update and delete the synthesis templates the Spec
Linter checks Builder drafts against, read and set the workspace's synthesis budget, and read and
set the JIT synthesis default for new Workflow Architect channels. Reads need `platform:read` and
writes need `synthesis:manage` and `platform:read`, all at the platform scope. A constraint the
Spec Linter would skip as malformed is refused. The Forge MCP server adds eight matching tools to
its `governance` group. See [Synthesis settings](https://docs.gloo.com/forge/reference/http-api/synthesis#synthesis-settings).

**2026-10-17**

Vendor credentials stay on the vendor's host.

Requests Forge sends with a key to a fixed vendor API now follow a redirect only while it stays on
that vendor's host, as requests to configured URLs already do. This covers model catalog syncs
(OpenAI, Google, Anthropic, Gloo), direct Anthropic inference, GitHub and Vercel environment syncs,
SendGrid email, WorkOS management calls, Vercel sandbox token checks, Pipedream and the demo
advisor. The Google model catalog sync now sends its key in the `x-goog-api-key` header instead of
the URL.


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