Wireframe locally with your agent

Your canvas, on your computer

Squig gives an external agent real editable UI components, shapes, text, images, freehand strokes and connectors. Your drawing already saves automatically in this browser. An agent with access to the same tab can work alongside you, using the same canvas, undo history and autosave. There is no signup, cloud canvas storage or Squig API key. Your agent uses its own model provider and account, including that provider's data handling and charges.

Invite an agent to this canvas

Open Connect agent in the canvas and give the copied instructions to your agent. It uses window.squig or supported WebMCP tools in your existing tab. No download, installation or companion is needed. The agent needs browser access to that tab: opening the website in another browser profile does not bring your drawing with it. The invitation includes a document ID so the agent can verify it has the right canvas.

Ask for distinct directions

Ask your agent to read the existing canvas, inspect the actual component catalog, and draw in small batches. Keep alternative directions side by side on the infinite canvas, with visible titles and tradeoffs. Components remain editable while you compare ideas and draw alongside the agent.

Use my open Squig canvas. Sketch a book club homepage in three directions: the next meeting first, the current book first, and a member-led reading journal. Use real copy and label the tradeoffs. Preserve my existing work.

Review and revise

Agent changes appear on the same canvas and join its normal undo history. Tell your agent which direction you prefer in the conversation, refine it together, then ask it to implement the design with its own coding tools. Changes save automatically as you work.

Optional: work with a disk file

For a chosen .squig.json file or a local MCP client, use Node.js 24 and pnpm 10 to build and run the companion. It opens one file and serves an editor whose edits save to that file. A missing file is created; an existing file is validated and opened. Keep the process running. Connect agent in that editor supplies the session details. To move a browser drawing to this workflow, export a copy explicitly and use its absolute path. Browser storage and a downloaded copy are separate.

git clone https://github.com/pablostanley/squig.git
cd squig
pnpm install --frozen-lockfile
pnpm build:local
pnpm squig serve /absolute/path/canvas.squig.json

What stays local

Website drawings stay in your browser's storage, and companion drawings save to your selected disk file. Clearing browser data can remove browser drawings; export a copy when you want a separate backup. The companion's disk history is capped at 50 snapshots and 16 MiB per file, and its local URL works only on that computer while it runs. The website still needs hosting, and an external agent may send relevant canvas content to its model provider according to its own settings.