Workspace Templates

Save your entire canvas layout as a reusable template and apply it later from the command palette.

A workspace template is a saved snapshot of your canvas — which tiles you had, where they were positioned, and how they were connected. Unlike Flows, which are small two-node subgraphs for common agent pairings, a template captures your entire current layout: every tile and every connection between them, exactly as you left it.

If you find yourself rebuilding the same five-tile layout every morning, save it as a template once and apply it in one action next time.

What you can do with it

Save the whole canvas — every tile's type, position, size, and title, plus every connection between them with its trigger, transform, loop settings, and stop keyword.
Apply a template in one action — pick it from the command palette and the saved layout drops onto your current viewport, recentred so you do not have to hunt for it.
Keep note content — a note tile's body text is preserved so applying a template does not hand you a blank note.
Stay portable across projects — terminal working directories are stripped on save, so a template does not point at a path that only exists on your machine.
Delete templates you no longer need — from the command palette, with a confirm prompt.

How to use it

Build the canvas layout you want to reuse.
Open the command palette (Cmd+Shift+P) and run Save Canvas as Template…. (This entry only appears when the canvas has at least one tile.)
Type a name when prompted and confirm.
To apply later, open the command palette and search for Apply Template: <name> — one entry appears per saved template. Select it.
To delete, search for Delete Template: <name> and confirm the prompt.

Applying a template is additive: it adds the saved tiles and connections to whatever is already on the canvas. It does not replace or clear anything.

Common use cases

Morning standup layout — three Claude agents on different parts of the codebase, a Codex reviewer, and a note tile with the day's plan. Save once, apply every morning.
Onboarding demo — a pre-wired canvas you apply when showing a teammate how MadoHub works.
Reusable review setup — an author + reviewer + watcher pattern with custom routing settings that do not fit a built-in Flow.

Tips and best practices

Save a template after you have wired the connections and tuned their settings — that is the whole point of capturing the layout, not just the tiles.
Give templates recognisable names; the command palette filters by them.
Re-dropping a template does not refresh an existing instance — it adds a fresh copy. If you want to refresh a running Flow in place, use Flows instead.
Frames are not part of a template. Only tiles and the connections between them are captured; the template applies into whatever frame (or top-level canvas) you are viewing at the time.

Flows — small reusable two-agent patterns with a prompt-first kickoff; complementary to templates.
Command Palette — where you save, apply, and delete templates.
Connections — what the saved connections between tiles actually do.

Limitations

Deleting a template is permanent — there is no undo.
Terminal working directories are not saved, so applied terminals open with no pre-filled directory.
Templates capture tiles and connections, not frames. Apply a template inside whichever frame you want it to live in.