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

> Produce and procedure nodes lose the Secret Bindings section, and Workflow Settings loses Default Vault; Credentials is where secrets reach agents and tools. Workflow nodes, drafts, versions and runs no longer have vault secret binding fields; Credentials is where secrets reach agents and tools. Saving or publishing a workflow no longer stores vault secret bindings or a default vault, and stored ones are cleared; Credentials is where secrets reach agents and tools.

**2026-10-20**

Workflow builder: vault secret bindings removed.

* Produce and procedure nodes in the workflow builder no longer show a **Secret Bindings** section, and **Workflow Settings** no longer shows **Default Vault**. Nothing read those bindings when a workflow ran, so a vault secret picked there never reached the agent, tool or procedure.
* Secrets reach agents, tools and procedures through [Credentials](https://docs.gloo.com/forge/console/platform/credentials.md), which checks each credential's approval and expiry. A procedure node keeps its credential binding in the builder.
* [Vaults](https://docs.gloo.com/forge/console/platform/vaults) and [Environments](https://docs.gloo.com/forge/console/platform/environments.md) are unchanged: they hold secrets and push them to deployment targets.

**2026-10-20**

Workflows: vault secret binding fields removed.

* Workflow nodes no longer have a `secretBindings` field, drafts and versions no longer have `defaultVaultId`, and runs no longer have `vaultOverrides`. All of them were already empty, and nothing read them when a workflow ran.
* Secrets reach agents, tools and procedures through [Credentials](https://docs.gloo.com/forge/console/platform/credentials.md), which checks each credential's approval and expiry.

**2026-10-20**

Workflows: vault secret bindings no longer stored.

* Saving a workflow node no longer stores vault secret bindings, saving workflow settings no longer accepts a default vault, and publishing no longer copies one onto the new version. Bindings already stored are cleared on the next deployment. Nothing read them when a workflow ran, so no run changes.
* Secrets reach agents, tools and procedures through [Credentials](https://docs.gloo.com/forge/console/platform/credentials.md), which checks each credential's approval and expiry.
* [Vaults](https://docs.gloo.com/forge/console/platform/vaults) and [Environments](https://docs.gloo.com/forge/console/platform/environments.md) are unchanged.


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