Skip to main content
With MagicOS, you manage one ongoing conversation and let MagicOS coordinate a stream of related work for you. You tell it what needs doing and it either updates the relevant thread or starts a thread for each task. Threads run in parallel, and you can check on them and steer them accordingly. Without MagicOS, iterating on different designs means doing the coordinating yourself: you decide what each one works on, repeat the same background at the start of each, and check back to see which finished or needs an answer.

​
When to use MagicOS

MagicOS is our recommended go-to unless you are just looking for a single page or quick prototype.

​
When a single design fits better

  • One page or one idea. A landing page, a single feature prototype, or something to show a stakeholder this afternoon.
  • You’d rather not work on a canvas. A single design gives you one chat and one preview, the way Magic Patterns has always worked.
  • You need a design-only feature. Plan Mode, Controls, forking, merging, and inline comments are available on single designs. The team is working hard on bringing feature parity to MagicOS.
You can bring an existing design into a MagicOS later with File → Import Existing Design.

​
How MagicOS relates to other features

  • Designs: every design on a MagicOS canvas is a full interactive design. Visual Edit works on it the same way.
  • Design Systems: ask MagicOS to create a design system from a design on the canvas, then use it anywhere. See Design Systems.
  • Slide decks: decks can live on a MagicOS canvas as their own files. See Slide Decks.
  • MCP server: connect Claude, Cursor, or Codex so your coding agent can build from what’s on the canvas. See MCP server.