Put your codebase on an infinite canvas, inside VS Code. Build it yourself, or let your AI agent build it for you over MCP.
- Map a repo. Services grouped into domains. Zoom in to see each one's entry points, then the real code.
- Trace a bug. Put the stack trace next to the code it points at, test hypotheses, and mark the root-cause line.
- Follow the data. Connect the real call sites hop by hop and label each edge with the payload it carries.
- Diff data over time. Chain diff cards (
order.0.jsontoorder.1.jsontoorder.2.json) under the code that changes them. - Draw diagrams. Flowchart, UML, C4, ERD, architecture and BPMN shapes, alongside your code.
Canvases are plain *.canvas.json files that you commit next to your code. They store paths and line ranges,
never file contents.
- Run VS Canvas: New Canvas, or open any
*.canvas.jsonfile. - Drag an arrow out of any card and drop it to add the next one. Double-click a card to edit it.
- Press Shift+S for the shape palette, or Cmd/Ctrl+K to search the canvas.
Each window runs a local MCP server; the status bar shows its port.
- VS Code agent mode finds it automatically.
- Claude Code: run VS Canvas: Set Up Claude Code for This Workspace, then start
claudein the project. - Teach your agents the canvas: run VS Canvas: Install Agent Skills to add a short guide for Claude Code,
Copilot, Cursor, Windsurf, Cline, Gemini CLI or
AGENTS.md, so they know when and how to use it.
Then ask, for example: "Map this repo's domains" or "Why does checkout charge twice? Build an investigation board."
