How Kombai's Infinite Canvases and Parallel Agents Work

Updated

Kombai's infinite canvases give you a scratch space to try design ideas before they touch production code, and parallel agents let you run several of those explorations at once. According to Kombai's site, you can "try different ideas on canvas, before they touch your production code," "run parallel agents in one or many canvases," and "precisely edit text, styles, and layout of any element." This fits teams that want to explore multiple directions quickly while keeping their repo's components, tokens, and hooks intact.

What the canvas is for

The canvas is a design-and-iterate surface, not your codebase. Kombai describes it as a place to:

  • Try different ideas before they reach production code
  • Work with live HTML, states, and animations
  • Create targeted variations or complete redesigns with AI

Because the canvas holds live HTML rather than static mockups, the states and animations you see are the ones you're actually working with. That matters when a design decision depends on how something behaves, not just how it looks.

Running parallel agents

Kombai lets you "run parallel agents in one or many canvases." In practice, that means you can point multiple agents at different explorations at the same time instead of iterating one idea to completion before starting the next.

  • One canvas, several agents: compare variations of the same screen or section side by side.
  • Many canvases: keep separate explorations isolated so a redesign in one doesn't disturb another.

The benefit is breadth: you can generate several directions, then narrow down, rather than committing to the first output.

Editing on the canvas

Once something is on the canvas, Kombai says you can "precisely edit text, styles, and layout of any element." The site's example controls include:

  • Improve Structure
  • Surprise me
  • Rearrange layout
  • Simplify
  • Enrich
  • Fix hierarchy
  • Adjust density

These sit alongside "Generate variations" and the ability to create targeted variations or complete redesigns with AI. So the loop is: generate, adjust a specific element directly, or ask for a variation of the whole thing.

Why it stays consistent with your repo

The canvas is where ideas are explored, but Kombai carries your existing decisions into new work. Its site states it "consistently reuses components, tokens, and hooks from your repo, npm package, or Storybook." It also references a Design System that "remembers your key design decisions" and Context Graphs that let it "code with your components, tokens, and hooks."

That's the point of separating exploration from production: you can experiment freely on the canvas, but the output is meant to fit the patterns already decided in your codebase rather than introducing new ones.

A concrete scenario

Say you're redesigning a landing page hero. You could:

  1. Open a canvas and generate a few hero variations.
  2. Run parallel agents to explore a split layout, a centered layout, and a scroll-reveal treatment at the same time.
  3. Use element-level edits to tune type scale, accent contrast, and hover interactions.
  4. Pick the direction that fits, knowing Kombai will reuse your repo's components and tokens when it moves into production code.

What to check before relying on it

Kombai lists availability for macOS, Windows, Linux, VS Code, and Cursor, and cites "600K+ installs and counting." It also notes support for multiple models (including Anthropic, xAI, Moonshot AI, and OpenAI options). For pricing and plan limits, check the pricing page directly, since the site's public description doesn't state cost or usage caps.