From ee75613d31863c01137111acfcac68666df9610d Mon Sep 17 00:00:00 2001 From: tmatup <51425734+tmatup@users.noreply.github.com> Date: Fri, 13 Nov 2026 20:04:24 -0800 Subject: [PATCH 1/5] docs(uipath-maestro-flow): drop the format step now that compile lays out MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit compile now lays out a flow or subflow with no .layout() the way `uip maestro flow format` does, and sizes every node by its canvas shape (UiPath/builder-sdk#2035). Retire the "run format on greenfield" step, the hand dim(288, 96) for agents, and dim() for default-size containers. Keep "never format a merged brownfield file". Studio Web overrides updated to match. 🤖 Generated with Claude Code Co-Authored-By: [Claude](mailto:noreply@anthropic.com) --- .../studioweb/uipath-maestro-flow/SKILL.md | 1 - .../references/CLI-LOOP.md | 2 +- .../references/diagnose.md | 14 +++---- .../uipath-maestro-flow/references/operate.md | 12 ++---- skills/uipath-maestro-flow/SKILL.md | 2 - .../references/CLI-LOOP.md | 14 +++---- .../references/diagnose.md | 21 +++++----- .../references/extract-document-node.md | 4 +- .../uipath-maestro-flow/references/operate.md | 40 +++++++------------ 9 files changed, 43 insertions(+), 67 deletions(-) diff --git a/skill-flavors/studioweb/uipath-maestro-flow/SKILL.md b/skill-flavors/studioweb/uipath-maestro-flow/SKILL.md index d046f73265..6604d12530 100644 --- a/skill-flavors/studioweb/uipath-maestro-flow/SKILL.md +++ b/skill-flavors/studioweb/uipath-maestro-flow/SKILL.md @@ -96,7 +96,6 @@ uip maestro flow decompile new.flow -o .flow-sdk/new.flow.ts --no-pipeline # Add your steps to it: uip maestro flow check .flow-sdk/new.flow.ts --source uip maestro flow compile .flow-sdk/new.flow.ts -o new.flow -uip maestro flow format new.flow --output json uip maestro flow validate new.flow --output json ``` diff --git a/skill-flavors/studioweb/uipath-maestro-flow/references/CLI-LOOP.md b/skill-flavors/studioweb/uipath-maestro-flow/references/CLI-LOOP.md index 4ca5d84612..539ddaf6dd 100644 --- a/skill-flavors/studioweb/uipath-maestro-flow/references/CLI-LOOP.md +++ b/skill-flavors/studioweb/uipath-maestro-flow/references/CLI-LOOP.md @@ -17,7 +17,7 @@ Studio Web does not use these gates. Its loop is `check --source --baseline` against the canvas copy, each `prepare` it names, `compile` into `/tmp/flow-draft///edited/`, `merge` into the target `.flow`, then `validate`. A new flow runs `check --source`, each -`prepare` it names, `compile` into its `.flow`, `format`, then `validate`. There is no compiled-artifact `check`; `validate` is that rung. +`prepare` it names, `compile` into its `.flow` (compile lays it out), then `validate`. There is no compiled-artifact `check`; `validate` is that rung. Warnings require deliberate review; whether one blocks a release comes from the surrounding task or release policy. diff --git a/skill-flavors/studioweb/uipath-maestro-flow/references/diagnose.md b/skill-flavors/studioweb/uipath-maestro-flow/references/diagnose.md index 100ad2deb8..05084b0780 100644 --- a/skill-flavors/studioweb/uipath-maestro-flow/references/diagnose.md +++ b/skill-flavors/studioweb/uipath-maestro-flow/references/diagnose.md @@ -30,12 +30,10 @@ there is no partial scaffold to repair. If a Flow folder is missing from -**Misshapen nodes on the canvas.** `compile` writes a placeholder -`ui.position` on each node — all of them on one row — and no top-level `layout` -block. In Studio Web this shows only on a new `.flow` that `compile` wrote -straight, with no merge: `merge` keeps the layout of the original and places -each added node, moving others to fit it; leave them where it put them. Fix such a new file once with -`uip maestro flow format .flow` — see -[`operate.md`](operate.md#lay-out-the-emitted-flow-first). Never run it on a -merged file: it lays out the canvas of the user again. +**Misshapen nodes on the canvas.** A source with no `.layout()` is not the +cause: `compile` lays it out the way `uip maestro flow format` does and gives +every node its canvas size ([`operate.md`](operate.md#layout-of-the-emitted-flow)). +`merge` keeps the layout of the original and places each added node, moving +others to fit it; leave them where it put them. Never run `format` on a merged +file: it lays out the canvas of the user again. diff --git a/skill-flavors/studioweb/uipath-maestro-flow/references/operate.md b/skill-flavors/studioweb/uipath-maestro-flow/references/operate.md index 16bc2a1f34..2fb1f26da6 100644 --- a/skill-flavors/studioweb/uipath-maestro-flow/references/operate.md +++ b/skill-flavors/studioweb/uipath-maestro-flow/references/operate.md @@ -11,14 +11,10 @@ positions of the user, and `merge` keeps them and places each added node, moving later nodes right or down and growing containers only to fit added ones. `format` lays out every node again and discards them. -A new `.flow` that `compile` wrote straight, with no merge, is different. -`compile` writes a placeholder `ui.position` on each node, all on one flat row, -and no top-level `layout` block. So run `format` once on such a file, before -the user opens it, unless its source sets `.layout()` (below): - -```bash -uip maestro flow format .flow --output json -``` +A new `.flow` that `compile` wrote straight, with no merge, needs no `format` +either. For a source with no `.layout()`, `compile` lays out every node the way +`format` does and gives each its canvas-shape size: a container (a loop, for example) 560 × 320, an +agent node 288 × 96, every other node 96 × 96. diff --git a/skills/uipath-maestro-flow/SKILL.md b/skills/uipath-maestro-flow/SKILL.md index 4390fd4e5a..2f67690e5b 100644 --- a/skills/uipath-maestro-flow/SKILL.md +++ b/skills/uipath-maestro-flow/SKILL.md @@ -103,8 +103,6 @@ The `uip maestro flow` commands delegate their semantics to the installed `@uipa ```bash ( cd "/" && uip maestro flow compile .flow-sdk/.flow.ts -o .flow ) uip maestro flow validate "//.flow" --output json -# Greenfield only (never a merged or .layout() file), before upload/debug/a designer: -uip maestro flow format "//.flow" --output json # Stated runtime claim; ask per references/operate.md ( cd "" && uip solution resources refresh --solution-folder . --output json ) ( cd "" && uip maestro flow debug --log-level error \ diff --git a/skills/uipath-maestro-flow/references/CLI-LOOP.md b/skills/uipath-maestro-flow/references/CLI-LOOP.md index c6318f3f8f..b6bcfdbf0a 100644 --- a/skills/uipath-maestro-flow/references/CLI-LOOP.md +++ b/skills/uipath-maestro-flow/references/CLI-LOOP.md @@ -133,14 +133,12 @@ uip maestro flow validate .flow --output json Warnings require deliberate review; whether one blocks a release comes from the surrounding task or release policy. -Layout is deliberately absent from this sequence. `uip maestro flow format` -is not an authoring gate — `validate` passes without it and nothing upstream -reads a position. For a greenfield file (one `compile` wrote from scratch), run -it before the file reaches anything that draws it: `solution upload`, -`flow debug`, or a person opening the project in a designer. Do not run it on a -merged brownfield file, or on one whose source sets `.layout()`: `format` -re-lays out every node, so it discards the positions the author chose. See -[`operate.md`](operate.md#lay-out-the-emitted-flow-first). +Layout is not a step in this sequence. `compile` lays out a source with no +`.layout()` the way `uip maestro flow format` does, so the file is ready for +`solution upload`, `flow debug`, or a designer. Do not run `format` on a merged +brownfield file, or on one whose source sets `.layout()`: `format` re-lays out +every node, so it discards the positions the author chose. See +[`operate.md`](operate.md#layout-of-the-emitted-flow). These authoring verbs require a prerelease of `@uipath/cli` that exposes them. diff --git a/skills/uipath-maestro-flow/references/diagnose.md b/skills/uipath-maestro-flow/references/diagnose.md index f240813207..217fc4de03 100644 --- a/skills/uipath-maestro-flow/references/diagnose.md +++ b/skills/uipath-maestro-flow/references/diagnose.md @@ -119,19 +119,16 @@ the flag silently returns a plain Flow. -**Misshapen nodes on the canvas.** `compile` writes a placeholder -`ui.position` on each node — all of them on one row — and no top-level `layout` -block. The canvas uses a node's `layout.nodes[]` entry when there is one -and its `node.ui` otherwise, so a greenfield file draws at the placeholders. -Symptom: the flow behaves correctly and is unreadable, a switch's arms strung -out in a line instead of side by side. This is not a run-time fault and no -check reports it — `validate` passes, because layout is not an authoring -concern. Fix, for a greenfield file only: `uip maestro flow format .flow`, -which is owed before an upload, a debug, or anyone opening the project in a -designer — see [`operate.md`](operate.md#lay-out-the-emitted-flow-first). Do not -run it on a merged brownfield file; it re-lays out the author's canvas. +**Misshapen nodes on the canvas.** Symptom: the flow behaves correctly and is +unreadable: nodes overlap, or a node is drawn at the wrong size. This is not a +run-time fault and no check reports it — `validate` passes, because layout is +not an authoring concern. A source with no `.layout()` is not the cause: +`compile` lays it out the way `uip maestro flow format` does and gives every +node its canvas size ([`operate.md`](operate.md#layout-of-the-emitted-flow)). +Do not run `format` on a merged brownfield file; it re-lays out the author's +canvas. -When the source sets `.layout()`, the misshapen node is the one with no entry, an entry at the wrong coordinates, an agent node (`inlineAgent`, `conversationalAgent`, `voiceAgent`) without `dim(288, 96)`, or a container whose `dim()` no longer holds a body that grew. +When the source sets `.layout()`, the misshapen node is the one with no entry, an entry at the wrong coordinates, or a container whose `dim()` no longer holds a body that grew. In a greenfield source: add or move its `at(x, y)`, resize with `dim(width, height)`, and recompile rather than running `format`, which would discard every other entry too. In a merged brownfield file only an added node's entry lands; fix an existing node's position or size in the merged `.flow`'s `layout.nodes` ([`operate.md`](operate.md#lay-out-from-source-instead-layout-at-dim), [`brownfield.md`](brownfield.md#designer-shapes-decompile-keeps)). diff --git a/skills/uipath-maestro-flow/references/extract-document-node.md b/skills/uipath-maestro-flow/references/extract-document-node.md index ee6118d519..1606951805 100644 --- a/skills/uipath-maestro-flow/references/extract-document-node.md +++ b/skills/uipath-maestro-flow/references/extract-document-node.md @@ -46,7 +46,7 @@ that lives in Studio Web and has to be pulled down first — ask them for its UR 1. **Check the tenant can run it:** `uip maestro flow extraction check --output json`. An answer other than `Available` stops the loop here, and a check that settles nothing is a question for the user ([Check the tenant can run it](#check-the-tenant-can-run-it)). 2. **Declare the file the flow takes in,** unless it already has one: `uip maestro flow variables create invoice -d in -t file --description ''`. Its `TriggerNodeId` is the `` in `$vars..output.invoice`, so it comes before the node that reads it. -3. **Add the node** with `--label` naming what it extracts, and `--input` carrying `fileRef`, laid out per [operate.md](operate.md#lay-out-the-emitted-flow-first). +3. **Add the node** with `--label` naming what it extracts, and `--input` carrying `fileRef`, laid out per [operate.md](operate.md#layout-of-the-emitted-flow). 4. **Connect it in the graph** with `edges create` ([Wiring the file it reads](#wiring-the-file-it-reads)). 5. **Write the taxonomy** — [extract-document-taxonomy.md](extract-document-taxonomy.md). 6. **Bind the result to a flow output** so the extraction leaves the flow — [Returning the result](#returning-the-result). @@ -161,7 +161,7 @@ The `error` port carries failures. Wire it with `edges create --source-port erro Extraction that nothing reads is not much use, so the flow usually declares an output carrying it. That takes three steps, and the last one has no CLI command — write it into the `.flow` file directly rather than going looking for a verb that does it. -Declare the output global, then add an End node ([laid out](operate.md#lay-out-the-emitted-flow-first)) and wire the extract node to it: +Declare the output global, then add an End node ([laid out](operate.md#layout-of-the-emitted-flow)) and wire the extract node to it: ```bash uip maestro flow variables create extractedData -d out -t object --description 'The structured data extracted from the document' --output json diff --git a/skills/uipath-maestro-flow/references/operate.md b/skills/uipath-maestro-flow/references/operate.md index b5b85d921e..b5b0f37172 100644 --- a/skills/uipath-maestro-flow/references/operate.md +++ b/skills/uipath-maestro-flow/references/operate.md @@ -10,28 +10,18 @@ Authoring is upstream. Do not ship a flow whose source has not been through the loop in [`CLI-LOOP.md`](CLI-LOOP.md) — `check` on the source, `compile` to emit, `validate` on the emitted `.flow`. -## Lay out the emitted flow first +## Layout of the emitted flow -```bash -uip maestro flow format .flow --output json -``` +`compile` lays out the flow. For a flow or subflow whose source has no +`.layout()`, each node gets the position `uip maestro flow format` would give +it, so a four-armed switch arrives with its arms on their own rows. Running +`format` on the compiled file moves nothing; skip it. The file is ready for +`solution upload`, `flow debug`, or a designer as `compile` wrote it. -**Greenfield files only.** Layout is not an authoring concern — nothing -upstream needs it, and `validate` passes without it. It becomes one here, the -moment a file `compile` wrote from scratch is opened by something that draws -it: `solution upload`, `flow debug`, or a person opening the project in a -designer. Run `format` before any of those, on the artifact as last emitted, -unless its source sets `.layout()` (below). - -`compile` writes a placeholder `ui.position` on each node and no top-level -`layout` block. The canvas places each node from its `layout.nodes[]` -entry when there is one, and from `node.ui` otherwise, so a greenfield file -draws at the placeholders. They are one flat row: a four-armed switch arrives -as a single 3,000px line with the arms in sequence rather than side by side. -`format` builds `layout`, fans the arms onto their own rows, sizes each node by -its canvas shape, and reports `NodesRepositioned`. Skipping it on a greenfield -file is the most common cause of misshapen nodes in Studio Web. +Every node also gets its canvas-shape size, unless `.layout()` sets one: a +container (a loop, for example) is 560 × 320, an agent node (`inlineAgent`, +`conversationalAgent`, `voiceAgent`) 288 × 96, and every other node 96 × 96. **Never format a merged brownfield file.** The original's `layout` already holds the canvas author's positions, and `merge` keeps them, moving later @@ -48,13 +38,13 @@ distinct position. With an author-chosen layout, skip `format` and pass ### Lay out from source instead: `.layout()`, `at()`, `dim()` -The builder can place the nodes itself, so the emitted file never needs `format` — provided every node that is not 96 × 96 carries its size (rule 1). +`.layout()` replaces compile's layout with positions you choose. `.layout({ nodes })` on the flow takes one entry per node, keyed by node id; `at(x, y)` writes an entry, and `dim(width, height)` the size a container needs. A step's id is its name. The trigger's is `start` unless `.triggerId()` renamed it. An End's is the `name` its `.return` gave it, and an unnamed End is `end`, then `end2`, `end3`, … in emission order, so a flow with several unnamed Ends has that many keys to write. Use it when the request asks for a particular arrangement, or when a decompiled source already carries one ([`brownfield.md`](brownfield.md#designer-shapes-decompile-keeps)). -Otherwise `format` is less work and lays out as well. +Otherwise leave it out: compile lays out the flow itself. ```ts import { at, dim, flow } from '@uipath/maestro-builder-sdk'; @@ -65,7 +55,7 @@ export default flow('invoice-intake') nodes: { start: at(256, 144), fetch: at(448, 144), eachInvoice: at(640, 144, dim(576, 320)), extract: at(144, 96), route: at(336, 96), // inside eachInvoice, relative to it - review: at(1312, 144, dim(288, 96)), // an agent node carries its size + review: at(1312, 144), // an agent node: compile gives it 288 × 96 done: at(1696, 144), onFailure: at(448, 528), end: at(640, 528), // below the container, not beside its body }, @@ -77,9 +67,9 @@ Rules: 1. **Use the canvas grid.** A node is 96 px square; a column is 192 px, a row 160 px: `x = 256 + 192 × column`, `y = 144 + 160 × row`. The main path goes on row 0 left to right; an error handler or a side arm takes the row below. - Compile writes 96 × 96 on every node and the designer draws the persisted size, so a node whose canvas shape is larger must carry it: an agent node (`inlineAgent`, `conversationalAgent`, `voiceAgent`) is `at(x, y, dim(288, 96))`, and the next column starts 384 px to its right; a container carries its `dim()` (rule 2), and the row below it starts one row gap (64 px) under its bottom edge, not at the next 160 px row. -2. **A child's position is relative to its container.** A loop or do-while body starts at `at(144, 96)` inside the container's padding, and the container needs a `dim()` that holds the body: the right edge of its rightmost child plus 144, by the bottom edge of its lowest child plus 96, never smaller than `format`'s `dim(560, 320)`. - For one row of 96 px nodes that is `dim(max(560, 192 × bodyNodes + 192), 320)`; a body with an inline agent, a second row or a nested container is measured from its own entries, not from the node count. + Compile gives a node without `dim()` its canvas-shape size: an agent node (`inlineAgent`, `conversationalAgent`, `voiceAgent`) is 288 × 96, so the next column starts 384 px to its right; a container is 560 × 320 unless its `dim()` makes it larger (rule 2), and the row below it starts one row gap (64 px) under its bottom edge, not at the next 160 px row. +2. **A child's position is relative to its container.** A loop or do-while body starts at `at(144, 96)` inside the container's padding. The container's 560 × 320 holds a small body; give it a `dim()` only when the body needs more: the right edge of its rightmost child plus 144, by the bottom edge of its lowest child plus 96. + For one row of 96 px nodes that is `dim(192 × bodyNodes + 192, 320)` from two body nodes on (two nodes: `dim(576, 320)`, as `eachInvoice` above); a body with an inline agent, a second row or a nested container is measured from its own entries, not from the node count. 3. **Name every node, or none.** A missing entry falls back to compile's one-row placeholder, which lands on top of your layout; an unknown key fails `compile`. 4. **Never `format` a file whose source sets `.layout()`.** `format` re-lays out every node and discards the source's positions, exactly as it does to a merged brownfield file. From 0bea9efa06e5cb8811052d29b20974f9f09c6856 Mon Sep 17 00:00:00 2001 From: tmatup <51425734+tmatup@users.noreply.github.com> Date: Fri, 13 Nov 2026 20:37:04 -0800 Subject: [PATCH 2/5] docs(uipath-maestro-flow): add the older-SDK fallback for compile layout MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Address review: state that compile layout needs an SDK with builder-sdk#2035, and keep the format / dim() fallback for an older SDK, with an upgrade flavor block (Studio Web: tell the user). 🤖 Generated with Claude Code Co-Authored-By: [Claude](mailto:noreply@anthropic.com) --- .../uipath-maestro-flow/references/diagnose.md | 4 +++- .../uipath-maestro-flow/references/operate.md | 8 ++++++-- skills/uipath-maestro-flow/references/diagnose.md | 4 +++- skills/uipath-maestro-flow/references/operate.md | 10 ++++++++++ 4 files changed, 22 insertions(+), 4 deletions(-) diff --git a/skill-flavors/studioweb/uipath-maestro-flow/references/diagnose.md b/skill-flavors/studioweb/uipath-maestro-flow/references/diagnose.md index 05084b0780..d791ed0fd3 100644 --- a/skill-flavors/studioweb/uipath-maestro-flow/references/diagnose.md +++ b/skill-flavors/studioweb/uipath-maestro-flow/references/diagnose.md @@ -32,7 +32,9 @@ there is no partial scaffold to repair. If a Flow folder is missing from **Misshapen nodes on the canvas.** A source with no `.layout()` is not the cause: `compile` lays it out the way `uip maestro flow format` does and gives -every node its canvas size ([`operate.md`](operate.md#layout-of-the-emitted-flow)). +every node its canvas size. The exception is an SDK without builder-sdk#2035, +which leaves every node on one row; the fallback is in +[`operate.md`](operate.md#layout-of-the-emitted-flow). `merge` keeps the layout of the original and places each added node, moving others to fit it; leave them where it put them. Never run `format` on a merged file: it lays out the canvas of the user again. diff --git a/skill-flavors/studioweb/uipath-maestro-flow/references/operate.md b/skill-flavors/studioweb/uipath-maestro-flow/references/operate.md index 2fb1f26da6..e780e22436 100644 --- a/skill-flavors/studioweb/uipath-maestro-flow/references/operate.md +++ b/skill-flavors/studioweb/uipath-maestro-flow/references/operate.md @@ -13,8 +13,8 @@ moving later nodes right or down and growing containers only to fit added ones. A new `.flow` that `compile` wrote straight, with no merge, needs no `format` either. For a source with no `.layout()`, `compile` lays out every node the way -`format` does and gives each its canvas-shape size: a container (a loop, for example) 560 × 320, an -agent node 288 × 96, every other node 96 × 96. +`format` does and gives each its canvas-shape size: a container (a loop, for +example) 560 × 320, an agent node 288 × 96, every other node 96 × 96. @@ -168,3 +168,7 @@ connection that is not in the solution fails at run time with a binding error. tell the user to chat with it from the Studio Web designer. The host returns no chat link. + + +or tell the user: Studio Web owns the SDK copy. + diff --git a/skills/uipath-maestro-flow/references/diagnose.md b/skills/uipath-maestro-flow/references/diagnose.md index 217fc4de03..99497a65bf 100644 --- a/skills/uipath-maestro-flow/references/diagnose.md +++ b/skills/uipath-maestro-flow/references/diagnose.md @@ -124,7 +124,9 @@ unreadable: nodes overlap, or a node is drawn at the wrong size. This is not a run-time fault and no check reports it — `validate` passes, because layout is not an authoring concern. A source with no `.layout()` is not the cause: `compile` lays it out the way `uip maestro flow format` does and gives every -node its canvas size ([`operate.md`](operate.md#layout-of-the-emitted-flow)). +node its canvas size. The exception is an SDK without builder-sdk#2035, which +leaves every node on one row; the fallback is in +[`operate.md`](operate.md#layout-of-the-emitted-flow). Do not run `format` on a merged brownfield file; it re-lays out the author's canvas. diff --git a/skills/uipath-maestro-flow/references/operate.md b/skills/uipath-maestro-flow/references/operate.md index b5b0f37172..72b7a54129 100644 --- a/skills/uipath-maestro-flow/references/operate.md +++ b/skills/uipath-maestro-flow/references/operate.md @@ -30,6 +30,16 @@ re-lays out every node and discards them. Upload or debug the merged file as `merge` wrote it. +This needs a `@uipath/maestro-builder-sdk` with builder-sdk#2035. An older SDK +writes every node 96 × 96 on one row at y = 144 (an agent node's `ui.size` is +96 × 96, not 288 × 96). With such an SDK, run +`uip maestro flow format .flow --output json` once on a greenfield file +(never on a merged or `.layout()` file), and in a `.layout()` give each agent +node `dim(288, 96)` and each container at least `dim(560, 320)`; + +or upgrade with `npm install -g @uipath/maestro-builder-sdk@latest`. + + `nodes create` without `--position`, or a hand edit that adds nodes, leaves every new node at `layout.nodes[].position` 0,0. After such an edit to a file with no author-chosen layout, run `format`, then confirm each node in `layout.nodes` has a From f57a2c3027ffdc3710e89e95c5e92bf31ca7488c Mon Sep 17 00:00:00 2001 From: tmatup <51425734+tmatup@users.noreply.github.com> Date: Sun, 15 Nov 2026 08:54:22 -0800 Subject: [PATCH 3/5] docs(uipath-maestro-flow): a decompiled new.flow drops its trigger-only .layout() before compile MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Review on #4723: the Studio Web new-flow loop starts from a decompiled new.flow, whose .layout() names the canvas trigger, so compile kept every added step on the placeholder row. The loop and the operate-format override now say to delete that call first. Also trims two operate.md lines that changed nothing. 🤖 Generated with Claude Code Co-Authored-By: [Claude](mailto:noreply@anthropic.com) --- skill-flavors/studioweb/uipath-maestro-flow/SKILL.md | 1 + .../studioweb/uipath-maestro-flow/references/operate.md | 4 +++- skills/uipath-maestro-flow/references/operate.md | 4 +--- 3 files changed, 5 insertions(+), 4 deletions(-) diff --git a/skill-flavors/studioweb/uipath-maestro-flow/SKILL.md b/skill-flavors/studioweb/uipath-maestro-flow/SKILL.md index 6604d12530..0eb814aab4 100644 --- a/skill-flavors/studioweb/uipath-maestro-flow/SKILL.md +++ b/skill-flavors/studioweb/uipath-maestro-flow/SKILL.md @@ -93,6 +93,7 @@ Schema-dynamic operations (`loadByDefault`, dependent dropdowns, `customFieldsRe ```bash cd /solution/ uip maestro flow decompile new.flow -o .flow-sdk/new.flow.ts --no-pipeline +# Delete its .layout({ ... }) call (the canvas trigger's one entry), so compile lays the flow out. # Add your steps to it: uip maestro flow check .flow-sdk/new.flow.ts --source uip maestro flow compile .flow-sdk/new.flow.ts -o new.flow diff --git a/skill-flavors/studioweb/uipath-maestro-flow/references/operate.md b/skill-flavors/studioweb/uipath-maestro-flow/references/operate.md index e780e22436..9042798733 100644 --- a/skill-flavors/studioweb/uipath-maestro-flow/references/operate.md +++ b/skill-flavors/studioweb/uipath-maestro-flow/references/operate.md @@ -14,7 +14,9 @@ moving later nodes right or down and growing containers only to fit added ones. A new `.flow` that `compile` wrote straight, with no merge, needs no `format` either. For a source with no `.layout()`, `compile` lays out every node the way `format` does and gives each its canvas-shape size: a container (a loop, for -example) 560 × 320, an agent node 288 × 96, every other node 96 × 96. +example) 560 × 320, an agent node 288 × 96, every other node 96 × 96. A +decompiled `new.flow` carries a `.layout()` with the canvas trigger's entry: +delete that call before you compile, or every other node stays on one row. diff --git a/skills/uipath-maestro-flow/references/operate.md b/skills/uipath-maestro-flow/references/operate.md index 72b7a54129..319b5c9be6 100644 --- a/skills/uipath-maestro-flow/references/operate.md +++ b/skills/uipath-maestro-flow/references/operate.md @@ -15,9 +15,7 @@ loop in [`CLI-LOOP.md`](CLI-LOOP.md) — `check` on the source, `compile` to emi `compile` lays out the flow. For a flow or subflow whose source has no `.layout()`, each node gets the position `uip maestro flow format` would give -it, so a four-armed switch arrives with its arms on their own rows. Running -`format` on the compiled file moves nothing; skip it. The file is ready for -`solution upload`, `flow debug`, or a designer as `compile` wrote it. +it. Running `format` on the compiled file moves nothing; skip it. Every node also gets its canvas-shape size, unless `.layout()` sets one: a container (a loop, for example) is 560 × 320, an agent node (`inlineAgent`, From 9465f2a6113ba04c931a33f9be9de3b33392683f Mon Sep 17 00:00:00 2001 From: tmatup <51425734+tmatup@users.noreply.github.com> Date: Sun, 15 Nov 2026 09:20:13 -0800 Subject: [PATCH 4/5] docs(uipath-maestro-flow): keep the Studio Web lifecycle section inside its size budget MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 🤖 Generated with Claude Code Co-Authored-By: [Claude](mailto:noreply@anthropic.com) --- skill-flavors/studioweb/uipath-maestro-flow/SKILL.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/skill-flavors/studioweb/uipath-maestro-flow/SKILL.md b/skill-flavors/studioweb/uipath-maestro-flow/SKILL.md index 0eb814aab4..3397c958a9 100644 --- a/skill-flavors/studioweb/uipath-maestro-flow/SKILL.md +++ b/skill-flavors/studioweb/uipath-maestro-flow/SKILL.md @@ -93,8 +93,7 @@ Schema-dynamic operations (`loadByDefault`, dependent dropdowns, `customFieldsRe ```bash cd /solution/ uip maestro flow decompile new.flow -o .flow-sdk/new.flow.ts --no-pipeline -# Delete its .layout({ ... }) call (the canvas trigger's one entry), so compile lays the flow out. -# Add your steps to it: +# Delete its .layout() call so compile lays it out, then add your steps: uip maestro flow check .flow-sdk/new.flow.ts --source uip maestro flow compile .flow-sdk/new.flow.ts -o new.flow uip maestro flow validate new.flow --output json From 62cc584fd8d1d94662024c18baedbc8b69ee337f Mon Sep 17 00:00:00 2001 From: tmatup <51425734+tmatup@users.noreply.github.com> Date: Sun, 15 Nov 2026 14:28:08 -0800 Subject: [PATCH 5/5] docs(uipath-maestro-flow): name the SDK release that lays out compile output (6.113.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit builder-sdk#2035 shipped in @uipath/maestro-builder-sdk 6.113.0, so the gates name that version instead of the PR. The Studio Web override tells the user the version rather than installing it. 🤖 Generated with Claude Code Co-Authored-By: [Claude](mailto:noreply@anthropic.com) --- .../studioweb/uipath-maestro-flow/references/diagnose.md | 2 +- .../studioweb/uipath-maestro-flow/references/operate.md | 2 +- skills/uipath-maestro-flow/references/diagnose.md | 2 +- skills/uipath-maestro-flow/references/operate.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/skill-flavors/studioweb/uipath-maestro-flow/references/diagnose.md b/skill-flavors/studioweb/uipath-maestro-flow/references/diagnose.md index d791ed0fd3..bf562541ab 100644 --- a/skill-flavors/studioweb/uipath-maestro-flow/references/diagnose.md +++ b/skill-flavors/studioweb/uipath-maestro-flow/references/diagnose.md @@ -32,7 +32,7 @@ there is no partial scaffold to repair. If a Flow folder is missing from **Misshapen nodes on the canvas.** A source with no `.layout()` is not the cause: `compile` lays it out the way `uip maestro flow format` does and gives -every node its canvas size. The exception is an SDK without builder-sdk#2035, +every node its canvas size. The exception is an SDK older than 6.113.0, which leaves every node on one row; the fallback is in [`operate.md`](operate.md#layout-of-the-emitted-flow). `merge` keeps the layout of the original and places each added node, moving diff --git a/skill-flavors/studioweb/uipath-maestro-flow/references/operate.md b/skill-flavors/studioweb/uipath-maestro-flow/references/operate.md index 9042798733..8a2300c56a 100644 --- a/skill-flavors/studioweb/uipath-maestro-flow/references/operate.md +++ b/skill-flavors/studioweb/uipath-maestro-flow/references/operate.md @@ -172,5 +172,5 @@ chat link. -or tell the user: Studio Web owns the SDK copy. +or tell the user the flow needs `@uipath/maestro-builder-sdk` 6.113.0 or later: Studio Web owns the SDK copy. diff --git a/skills/uipath-maestro-flow/references/diagnose.md b/skills/uipath-maestro-flow/references/diagnose.md index 99497a65bf..9898f76d57 100644 --- a/skills/uipath-maestro-flow/references/diagnose.md +++ b/skills/uipath-maestro-flow/references/diagnose.md @@ -124,7 +124,7 @@ unreadable: nodes overlap, or a node is drawn at the wrong size. This is not a run-time fault and no check reports it — `validate` passes, because layout is not an authoring concern. A source with no `.layout()` is not the cause: `compile` lays it out the way `uip maestro flow format` does and gives every -node its canvas size. The exception is an SDK without builder-sdk#2035, which +node its canvas size. The exception is an SDK older than 6.113.0, which leaves every node on one row; the fallback is in [`operate.md`](operate.md#layout-of-the-emitted-flow). Do not run `format` on a merged brownfield file; it re-lays out the author's diff --git a/skills/uipath-maestro-flow/references/operate.md b/skills/uipath-maestro-flow/references/operate.md index 319b5c9be6..af12fdb4fe 100644 --- a/skills/uipath-maestro-flow/references/operate.md +++ b/skills/uipath-maestro-flow/references/operate.md @@ -28,7 +28,7 @@ re-lays out every node and discards them. Upload or debug the merged file as `merge` wrote it. -This needs a `@uipath/maestro-builder-sdk` with builder-sdk#2035. An older SDK +This needs `@uipath/maestro-builder-sdk` 6.113.0 or later. An older SDK writes every node 96 × 96 on one row at y = 144 (an agent node's `ui.size` is 96 × 96, not 288 × 96). With such an SDK, run `uip maestro flow format .flow --output json` once on a greenfield file