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

> The workflow builder draws on the same auto-layout canvas as the Graph tab; you insert, branch, connect and delete steps through controls on the graph. The builder's agent readiness robot shows a ✕ or ! as well as its colour, and the in-app Slack help page describes /forge and the current Slack integration. Explicit Customer case authoring, exact-key lookup, bounded search excerpts and scoped retrieval previews. The direct-message routes no longer answer 409 for a person with many conversations. Links to the retired workflow designer and the legacy definition viewer open the workflow catalog or the workflow's Graph tab instead of a missing page. The MCP server registers only the tools of its listing jobs; a call to a retired tool is refused with its forge_call_operation equivalent. Below desktop width, the run page lists the run's steps from the same run state as the canvas, with branches, routes and End shown as they ran. The step library detail panel no longer shows Use in Designer, which never added the step to a workflow and opened a broken page. The Graph tab and version compare draw workflows as readable blocks, and compare marks every added, removed and changed step and edge. Produce nodes are now labeled Agent, with clearer assignment controls. The run header stacks at phone width and shows the workflow's name, old runs show a date, readiness markers differ by shape, and Compare explains when it needs a second version. Correct Freshservice assignments reach the MFA workflow and use clearer sidebar labels.

**2026-10-29**

Workflow builder: auto-layout canvas with inline edit controls.

* The builder draws the draft on the same auto-layout canvas as the **Graph** tab. Steps are always arranged automatically; you no longer drag them into position, and the **Auto Layout** buttons are gone.
* A `+` on every connection, under each final step's **End** cap, before a step where parallel lanes gather, and above a parallel group inserts a step. **Add a branch** sits beside forks, parallel groups and routers; on a rules router it opens the router panel so you add a rule.
* Drag a step type from the palette onto any `+` or **Add a branch** control; drop targets are highlighted while you drag.
* AI routers have one port per route, and a connection drawn from a route port carries that route's label. Steps and connections with validation problems show a red **✕** or amber **!**.
* Right-click a step, or press **Shift+F10**, for **Add after**, **Add branch**, **Duplicate**, **Disconnect** and **Delete**. Every delete asks you to confirm, and deleting a step with one connection in and one out reconnects its neighbours.
* Builder undo (**Cmd/Ctrl+Z**) is turned off: it reset only the canvas and never the saved draft. See [Editing the builder canvas](https://docs.gloo.com/forge/console/production/workflows/builder-canvas.md#editing-the-builder-canvas).

**2026-10-29**

Builder readiness glyph and the Slack help page.

* In the workflow builder, the robot beside a step's validation marker now carries a small ✕ when the step's agent can't run and a ! when it needs attention, so the state no longer rests on red or amber alone. A ready agent still shows no robot.
* The in-app help page **Communication Surfaces** now describes the current Slack integration: the `/forge` command and its `run`, `status`, `approvals` and `help` subcommands, human-task cards and direct messages, the current endpoints, and the credential-based setup.

**2026-10-29**

Customer SOP authoring and import verification.

A Personal MCP key can explicitly select one active linked Customer for case creation, listing, reading, updating and scoped search under current Gloo-root authority. Customer partitions stay outside ambient discovery. Cases also support exact namespace/key lookup for duplicate checks.

MCP search returns bounded discovery excerpts with explicit truncation metadata. A privileged agent retrieval preview can select one namespace under both viewer and agent authority. The [manual SOP import procedure](https://docs.gloo.com/forge/reference/http-api/knowledge#manually-importing-an-sop) covers stable section keys, full read-back and cross-customer verification.

**2026-10-29**

Direct-message lookup has no conversation ceiling.

The two direct-message routes in the [Chat API](https://docs.gloo.com/forge/reference/http-api/chat), the one between two people and the one with a worker, find the pair's direct message by its participants alone. A Personal key whose owner holds more than 500 conversations no longer gets a `409 conflict` from either route. Both routes answer the existing direct message, or create one.

**2026-10-29**

Old workflow designer and definition links now redirect.

* The legacy definition viewer (a workflow address ending in `/definition`) is retired. Saved links to it open the workflow's page, whose **Graph** tab shows the same definition on the current canvas.
* Saved links to the retired workflow designer (`/production/workflows/designer` and `/execution/designer`) open the [workflow catalog](https://docs.gloo.com/forge/console/production/workflows) instead of a missing page. Start a new workflow there with **+ New Workflow**.

**2026-10-29**

Forge MCP: the retired tools' code is removed.

* The code of the tools retired from the MCP listing is removed. The server registers only the listed tools: the `start` job and the seven other listing jobs. Selecting the `extended` toolset registers nothing more.
* A call to a retired tool's name is refused with `isError` and names the `forge_call_operation` call that does the same thing, for example `forge_call_operation("updateAgent")`.
* Reach any operation without a listed tool with `forge_search_operations`, then `forge_describe_operation`, then `forge_call_operation`, using your connection's own credential. See [Reaching any other operation](https://docs.gloo.com/forge/reference/mcp-server.md#reaching-any-other-operation).

**2026-10-29**

Run page on a narrow screen: the same steps as the canvas.

* On a phone or a narrow window, the run page lists the run's steps with the same status as the canvas. **End** now reads **Reached** when the run finished there, instead of always reading **Pending**.
* Parallel branches are listed as **Branch 1 of 3** and so on, and a router's routes are listed under it with **Taken** or **Not taken**. An ended run folds routes it did not take into one **N steps not run** row; tap it to list them.
* Each step shows its kind, duration and cost, or its error as a sentence. Tap a step to see its details.

**2026-10-29**

Step library: the broken Use in Designer button is removed.

* The step library's detail panel no longer has a **Use in Designer** button. It never added the step to a workflow, and it had started opening a broken run page. **Edit**, **Duplicate** and **Delete** are unchanged. To build a workflow, use **+ New Workflow** in the [workflow catalog](https://docs.gloo.com/forge/console/production/workflows).

**2026-10-29**

Workflow graph and version compare: readable blocks.

* The **Graph** tab and version previews draw the published workflow as blocks, top to bottom, at 80% zoom or closer. The frame is as tall as the graph, up to most of the window.
* **Compare** draws both versions on one canvas. Steps, routes and edges carry **+ Added**, **− Removed** or **\~ Changed** marks, and the panel lists each kind with a count; a changed condition shows its before and after text.
* Switching which version is shown changes only which steps are drawn solid. Nothing moves.
* Compare and the rollback summary no longer report every step as removed and re-added after a publish, and an edge whose condition, label or error route changed now counts as a change.

**2026-10-29**

Agent nodes can be assigned to AI or people.

Workflow **Produce** nodes are now called **Agent** nodes. In workflow properties, use **Assigned to** to choose AI, Human, or Role. The editor and run graph distinguish known assignment kinds with a badge, while unresolved specific workers remain labeled Assigned.

Existing workflows keep their behavior and stored `produce` type. The AI agent registry and Workforce terminology stay the same. See the [workflow guide](https://docs.gloo.com/forge/console/production/workflows).

**2026-10-29**

Workflow and run pages: phone layout, names and readable times.

* A run's header shows the workflow's name instead of "Workflow".
* On a phone the run header stacks: the name and badges, then cost, duration and steps, with nothing overlapping. A failed run's banner text uses the full width, and **Retry from failed step** and **Fix with Architect** sit below it.
* "started … ago" counts days past one day and shows the date past a week ("started on Oct 13, 4:39 PM"), in the runs table's style.
* An agent step's readiness marker is a ✕ when the agent is blocked and a ! when it needs attention, on the Graph tab, in the org chart and in the builder's agent picker. Ready stays a small neutral dot.
* On **Versions**, a workflow with one published version shows **Compare** turned off with the reason: it needs a second published version.
* On the **Graph** tab, a graph wider than the pane shows the minimap so the hidden branches are visible; drag to pan. Scrolling over the graph still scrolls the page.

**2026-10-29**

Wycliffe MFA sidebar identity and labels.

The Wycliffe Freshservice sidebar now compares the assigned technician's user ID with the
ticket's responder ID, so a different internal agent-record ID no longer rejects a correct
assignment. The app also preserves the clicking human's separate identity and the assigned
technician's name and email.

The section is titled **Forge Wycliffe MFA Reset**, describes sending the ticket to the Wycliffe
MFA reset Forge workflow, and offers **Run MFA Reset**. App source and offline regression tests
are now versioned with the repository. Operators install the new ZIP as an update to the
existing custom app; merging source does not install it or run a reset.


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