> ## 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.

# Workflow builder canvas

> Edit a draft workflow in the visual builder: read the situation panel, confirm or reject the Architect plan and proposed primitives, and add, branch, connect and delete steps.

When you open a draft from a workflow's detail page, the visual builder (`/production/workflows/convex/builder-v2`) shows three surfaces side by side: the situation panel down the left edge, the canvas in the middle, and the Architect chat. This page covers those three surfaces. [Graph Builder](https://docs.gloo.com/forge/console/production/graph-builder) covers the builder's modes, test runs and publishing, and [Step settings](https://docs.gloo.com/forge/console/production/workflows/step-settings.md) covers each step's **Properties** panel.

![Graph builder canvas](https://mintcdn.com/gloo-b243725a/Ndtg9NEpwGc2OULA/forge/images/console/production/graph-builder-light.png?fit=max\&auto=format\&n=Ndtg9NEpwGc2OULA\&q=85\&s=a045a6235a7de6552e68ef5dd71e56f1)

Graph builder canvas — Forge Console at `/production/workflows/convex/builder-v2`

## What you can do

* Follow what the Architect is doing in the situation panel: the brief, a live activity line, the manifest of steps with their states, and the judge verdict.
* Click a manifest row to select that step on the canvas and filter the Architect chat to the turns about it.
* Confirm, reject or edit the Architect's plan and each primitive it proposes, directly on the rail, and re-read resolved decisions in the **Decisions** ledger.
* Insert a step, add a branch, drag a step type from the palette, connect steps and delete them through controls placed on the canvas.
* Read validation problems on steps and connections, and use the step menu or the keyboard instead of the mouse.

## The builder situation panel

When you open the visual builder for a draft, a persistent **situation panel** runs down the left edge — a third surface alongside the canvas (the artifact) and the Architect chat (the conversation). It answers "where are we, where are we going, what are we waiting on" and mutates in place rather than scrolling away.

Top to bottom, the panel shows:

* **Brief** — the source ("From document" or "Pasted brief") and a one-line excerpt of the original brief that drove this workflow.
* **Activity ticker** — a live single line of what the Architect is doing right now (reading the brief, searching the catalog, drafting the graph). It fills the gap between submitting and seeing nodes land on the canvas.
* **Manifest** — each workflow step as a state row: a kind tag, name, rationale, and a state chip (`planned`, `catalog`, `needs you`, `confirmed`, `building`, `live`, `failed`). Rows with judge findings carry a `⚠ N` badge. A "Synthesizing N of M" header appears while steps are being built. **Click a row** to open that step: when the step is already on the canvas (`live`), the builder selects its node and shows its **Properties**, where its settings such as Timeout live. The click also filters the Architect chat to just the turns about that step, so the manifest doubles as a navigable index into the conversation. A "Showing *step* · N turns" banner appears above the chat on the **Architect** tab; click **Clear** (or the row again) to remove the filter. A step that is still only planned has no node yet, so its click filters the chat only.
* **Judge pill** — the latest health verdict for the drafted graph (`— → judging… → ✓ Healthy 87 / ⚠ Needs work 62 / ✕ 41`), updated in place. This pill is now the **only** place a judge verdict appears — verdicts no longer post into the Architect chat, so the conversation stays a story rather than mixing standing status into the stream.

The Architect chat is **quiet by default**: each batch of the Architect's tool calls collapses to a single changelog line (e.g. "drafted 3 nodes, 2 edges") and its reasoning stays behind a "show reasoning" disclosure. Use the **Trace / Quiet toggle** at the top of the chat to switch to the full tool-call and reasoning stream, or click any batch line to expand just that batch.

The panel and the Architect chat are both **resizable** — drag the grips on their inner edges; widths persist per user. While the canvas is still empty it shows "Composing your graph · N steps" instead of a blank grid; when the graph first lands, its nodes reveal in dependency order (entry → downstream) and the view zooms to fit.

## Confirming decisions in the rail

The Architect's confirmations happen **on the rail**, not as cards that scroll away in chat. When the Architect needs your sign-off, the affordance appears where the thing it describes lives — and once you act, the decision **demotes into a Decisions ledger** instead of disappearing.

* **Plan confirm.** While the Architect's plan is pending, a confirm strip sits above the manifest with the topology summary, the number of decisions to confirm, and a live **"expires in Nm"** countdown. **Confirm** accepts the plan; **Reject** sends it back for a re-propose; **Edit** opens the Architect drawer's plan editor. On expiry the strip shows **"expired — re-propose"** rather than vanishing.
* **Per-primitive confirm.** When the Architect proposes new primitives, the affected manifest rows turn **`needs you`** and gain an expand caret. Expanding a row reveals an **inline** confirm strip — what the primitive does, its cost, and any coherence violations — right on the step. **Confirm** accepts just that primitive (its dependencies are confirmed with it); **Reject** declines it; **Edit** navigates to the primitive editor. A blocking coherence error disables Confirm until it is resolved. Nothing pops a modal over the canvas.
* **Decisions ledger.** Below the manifest, every resolved decision lands as a demoted, re-expandable row — "✓ Plan · 5 steps · 2m ago", "✓ Confirmed 2 of 3". It is an audit trail of what you approved and when, so an approved plan or a confirmed primitive is never lost to the chat scrollback.

## Editing the builder canvas

**Agent** nodes assign work to an AI or human agent. In the properties panel, **Assigned to** offers **AI**, **Human**, and **Role**; **AI agent** selects an AI definition. An assignment badge shows AI, Human, Role, or Dynamic where known. A specific worker whose kind is unavailable reads Assigned (Unassigned if no worker has been selected). The API and stored graph continue to use `type: "produce"`.

The builder draws the draft on the same auto-layout canvas as the **Graph** tab. Steps are always arranged automatically — you don't drag them into position, and there is no layout button. You change the graph through controls placed on it:

* **Insert a step.** A small `+` sits on every connection ("Insert a step between A and B"), under each final step's **End** cap ("Add a step after S"), before a step where parallel lanes gather ("Insert a step before M"), and above a parallel group ("Insert a step between A and its 3 parallel steps"), which moves the fan-out onto the new step. Click it to pick a step type. **Add after** on a step whose lanes fan out does the same.
* **Add a branch.** An **Add a branch** control sits at the right end of a fork's rail, beside a parallel group, or beside a router's exit list. On an AI (route-option) router it adds a new route and its branch. On a rules router it opens the router panel so you add a rule, because every branch needs a condition.
* **Drag from the palette.** Drag a step type onto any `+` or **Add a branch** control; every drop target is highlighted while you drag. Dropping anywhere else shows "Drop on a + to place the step". An empty workflow shows a drop zone with an **Add a step** button.
* **Connect steps.** Drag from a step's bottom port to another step's top port. An AI router has one port per route (hover shows "Route *label*"), and a connection drawn from a route port carries that route's label.
* **Read validation.** A step or connection with a problem shows a red **✕** (error) or amber **!** (warning); hover it for the messages. A connection's glyph sits beside its `+`, and its line is tinted where it runs on its own. Click the glyph or the connection to select it.
* **Use the step menu.** Right-click a step, or focus it and press **Shift+F10** or the **ContextMenu** key: **Add after**, **Add branch** (forks), **Duplicate**, **Disconnect**, **Delete**. **Duplicate** places the copy directly after the step — after the merge step, for a fork.
* **Delete.** Use **Delete** in the step menu, press **Delete** or **Backspace** on a focused step, or press **Delete** on a focused connection's `+`. Every delete asks you to confirm. Deleting a step with exactly one connection in and one out reconnects its neighbours and keeps the incoming route label.

Keyboard: the steps are one **Tab** stop, and the arrow keys move along the graph; **Enter** opens the focused step's panel. Every `+`, branch and validation control is its own **Tab** stop after the steps.

> [!NOTE]
>
> The builder has no undo. **Cmd/Ctrl+Z** used to reset only the canvas, never the saved draft, so a refresh brought the change back; it is turned off until undo can restore the saved draft. To reverse an edit, delete the step or connection you added, or add back what you removed.

## Key state to watch

* **`needs you` rows** in the manifest — the Architect is waiting for you to confirm a primitive before it builds that step.
* **The plan countdown** — a pending plan shows **expires in Nm**; once it reads **expired — re-propose**, ask the Architect to propose again.
* **The judge pill** — the only place the drafted graph's health verdict appears.
* **Red ✕ and amber ! glyphs** — errors and warnings on a step or connection.
* **No undo** — reverse an edit by deleting what you added or adding back what you removed.

## Related surfaces

* [Workflows](https://docs.gloo.com/forge/console/production/workflows) — the catalog and each workflow's detail page.
* [Graph Builder](https://docs.gloo.com/forge/console/production/graph-builder) — builder modes, test runs and publishing.
* [Step settings](https://docs.gloo.com/forge/console/production/workflows/step-settings.md) — a selected step's **Properties**.
* [Use the Workflow Architect](https://docs.gloo.com/forge/build/use-workflow-architect.md) — the agent that drafts the graph.


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