Canvas & Assets
Understanding how Virse organizes your work helps you get the most out of the MCP Skill.
Core Concepts
Virse is structured around three levels:
Workspace (Space) — Your top-level project container
Canvas (Project) — Each workspace has one canvas where elements live
Elements — Images, text, and other items placed on the canvas, connected by edges
Every canvas operation requires a canvas_id. The agent handles this automatically — just tell it which workspace you want to work in.
Layout
The agent can arrange elements on your canvas using three layout algorithms:
Grid — Elements arranged in rows and columns (up to 4 columns), with 20px gaps between items.
Flow (left to right) — Stages flow horizontally with 300px between stages and 30px between items within a stage. Good for workflows and pipelines.
Radial — Elements arranged in a circle with a 400px radius. Useful for showing relationships around a central concept.
Before placing new elements, the agent checks existing canvas contents to avoid overlapping your work.
Asset Management
Searching
If your first search doesn't find what you need, the agent will try different strategies:
Broaden — Removes overly specific terms
Synonymize — Tries alternatives ("logo" becomes "brand mark")
Decompose — Searches for individual components separately
Abstract — Moves to higher-level concepts
Folders
Asset folders use zero-copy links — adding an image to a folder doesn't duplicate it. The same image can live in multiple folders, and removing it from a folder doesn't delete the original.
Important Rules
Always confirm destructive actions — The agent will ask for your approval before deleting elements, edges, or groups.
Check balance before batch operations — The agent checks your CU balance before generating 3 or more images, so you won't accidentally overspend.
The agent can't see generated images — Refinement is based on prompt expertise and your feedback. Always share your thoughts between generation rounds so the agent can adjust.
One canvas at a time — The agent works on a single canvas per session unless you're running a cross-workspace workflow.
Last updated
