Edit mode
Targeted AI changes to an existing workflow: what Edit mode does, how it differs from Build, proof revocation, and the undo checkpoint.
Edit is for changing a workflow that already exists: "also email me a copy", "make the retry wait longer", "swap the channel to #alerts". No plan, no walk — a direct, targeted change.
Build vs Edit
| Build | Edit | |
|---|---|---|
| starts from | a goal sentence | an existing graph |
| produces | a plan, then the whole graph | a targeted diff |
| verification | the full walk, every step | revalidates what changed |
| best for | new workflows | tweaks, additions, fixes |
The mode pill in the chat switches between them — and the switch is always yours; the AI never changes modes on you.
What Edit is careful about
- Verified steps are expensive to touch. An edit that rewrites a proven step revokes its proof — Max is steered to make the smallest change that satisfies the request, and tells you when a proof was revoked.
- Your selection is context. With a node selected, the chat's context pill scopes the request — "make this quieter" knows what this is.
- The graph is validated after every change — the same linter the build uses (missing refs, unwired branches, stale defaults) runs before the edit reads as done.
Undo
Every AI edit leaves a checkpoint. Undo Max's changes (on the canvas rail) restores the graph to exactly before the last AI turn — available until you activate, edit past it, or start another turn.
FAQ
Can Edit build a whole workflow? It can, but Build is better at it — the plan and walk exist precisely so big builds get verified step by step.
Does editing pause a live workflow? No — the live snapshot keeps serving until you re-activate with the changes.