Spatial Canvas

Thinking in Infinite Space

Chat flattens parallel work into one scrolling timeline: variants, branches, and sub-tasks compete for the same column, and moving context between them means copy-paste. Spatial Canvas externalizes each AI context as a node on an infinite canvas — drag to arrange, draw an edge to pipe one node's output into another's context — so the structure of the work is the picture in front of you, not a memory of where things sat in the scroll.

Framing

The problem

Linear chat hides parallel context, branches, and relationships.

The pattern

Externalize AI work as spatial nodes on a shared canvas.

Why chat breaks here

Scrolling transcripts collapse many threads into one timeline.

Risks

Spatial systems can become visually chaotic without hierarchy and pruning.

Avoid when

The task is simple and spatial organization would just add overhead.

Use when

Users hold many parallel threads — variants, branches, sub-tasks — that chat history flattens.

DOPE evaluation

Directability
Drag nodes to restructure, draw or delete an edge to change what flows where — context routing is direct manipulation, not prompt engineering
Observability
Every context is a node on one surface and every dependency is a drawn edge — the shape of the work is read off the canvas, not remembered from the scroll
Predictability
An edge is a contract: connect Research to Review and Review consumes exactly that context; disconnect it and the contribution disappears from the output
Explainability
A downstream node names the inputs it consumed ("Review based on: research + brief"), so its output is traceable to specific upstream contexts

In the wild

  • tldraw computer (tldraw) — Text, image, and audio components flow through draggable arrows on an infinite canvas. AI work as a node graph rather than a transcript.
  • Miro Intelligent Canvas (Miro) — AI Sidekicks live directly on the canvas; Flows are drag-and-drop AI building blocks connected with arrows. Apr 2026 added PDF/Markdown drop-in.
  • ComfyUI (Comfy.org) — Node graph as the entire product surface — every step of an image generation pipeline is a connected node. Mar 2026 added App Mode for shipping workflows as apps.

FAQ

When should I use the Spatial Canvas pattern?

Users hold many parallel threads — variants, branches, sub-tasks — that chat history flattens.

When should I avoid the Spatial Canvas pattern?

The task is simple and spatial organization would just add overhead.

What problem does Spatial Canvas solve?

Linear chat hides parallel context, branches, and relationships.

Why is chat the wrong fit for this?

Scrolling transcripts collapse many threads into one timeline.

Related patterns

  • Often paired with: Parallel Alternatives — Branch alternatives spatially instead of cycling through them serially.
  • Extends: Editable Plan — Plan steps become spatial nodes you can rearrange and connect.
  • Alternative to: Generative UI — Many parallel AI contexts in space vs one rich interactive answer.

Browse all patterns