Why you should pay for the integrated AI chat

Brilliant's integrated AI chat is the best interface in the world for designing with an AI agent.

Are we objective? No. Is it the truth? Absolutely.

If you design in Brilliant without paying for the integrated chat, you are paying more, not less. You pay in tokens and you pay in time.

This doc explains why.

Context management is incredible

We save you hundreds of thousands of tokens per chat. That is not an exaggeration. Here is just a peek at what the orchestrator does on every turn, without you lifting a finger.

The end result? You can have longer conversations, and the cost per chat is lower.

Old images get dropped

A screenshot attached several turns ago can be 50,000 tokens. It is not helping the agent decide what to do now. Brilliant drops stale images automatically, leaving a short [Image cleared] stub in their place. The recent ones stay, because those are the ones that matter for the next move. Zero user effort, zero config.

Long tool results get collapsed

When the agent calls lookup and gets back a 20K-token canvas dump, it stays in context while you keep iterating. Once it goes stale, it collapses into [Tool result cleared], and only when collapsing actually saves enough to matter. Nothing is trimmed aggressively to manufacture an upgrade prompt. The savings are real.

Streaming catches bad output early

When the agent writes a broken Blueprint line mid-stream, Brilliant stops applying lines at the break point and surfaces the error, so the next turn course-corrects instead of piling another 300 lines of invalid tokens on top.

Much more

There is a lot more to add here around token efficiency and how it affects the quality of the agent's output, but let's just say: we take the AI chat experience and your token spend very seriously.

The UX is why you stop using everything else

Design work is contextual. Context includes locations, colors, elements, ordering and more.

Brilliant's AI chat is optimized exactly for this. No describing which element you're talking about. No trying to describe general locations on the canvas.

Want to reference an element? Just copy paste it to the chat. The agent sees the element, the structure and the hierarchy. No back and forth to fetch context, and no time wasted on describing.

Want to point at a place on the canvas? Drop a pin with the position picker.

Want to use an existing color? Toggle color picker and pick a color or open the color selector and try different colors until you get it right.

That's just a taste but there is a lot more.

Selection-aware inputs

Copy-paste any element as a reference chip, inline in the prompt.
@mention any layer with autocomplete from live layer names.
Eyedropper anywhere on screen with the color pick button or ⌃⇧C.
Position pick for "this spot on the canvas."
Paste images into the input with ⌘V.
Drag files onto the input.

Model switching mid-conversation

One dropdown. Anthropic, OpenAI, Google, OpenRouter, Claude Code CLI, all with unified thinking levels (off, low, medium, high, plus xhigh on Codex). The conversation carries through because the event stream is normalized behind the dropdown. Hit the hard turn with Opus, drop to Haiku for cleanup, back to Opus. No re-briefing.

Parallel chats with real keyboards

⌘N opens a new chat. ⌘1 through ⌘9 jump between them. Each has its own undo stack, its own canvas context, its own model. Experiment in one while the other stays intact. ⌘⇧I searches across all chats. Up and down arrows walk your prompt history in the input; ⌃R reverse-searches it.

Per-chat undo stack

We treat each agent like a user. Each agent has its own undo/redo you control. You can roll back to a specific part of the chat, or step back and forth change after change.

Separate from the canvas undo. The agent runs a 40-operation batch, and you can walk back just the agent's edits without touching the pen-tool work you did during the wait. This is not possible in any external editor.

Snap full-screen, bottom, left, right. Resize. Queue the follow-up while the agent is still working; it sends on completion. Edit a user message and resend. Copy the entire transcript as markdown with YAML front matter.

You can see what's happening

Progressive creation lands elements on canvas as the agent types them.
Thinking blocks are collapsible with a live elapsed timer.
Tool calls are expandable cards with clickable URLs and copy-JSON.
Skill badges show exactly what knowledge the agent loaded.
Element and canvas chips show exactly what element was updated and with what values. Same for Canvases. The agent can literally point you at the right element or canvas.

Every one of these is the difference between seeing what the agent does, live, and waiting 3 minutes just to see it didn't understand you properly.

Each element updates immediately as the agent streams the intent. You can stop the agent immediately if something seems off and point it at the right direction.

The output is actually better

External MCP agents get access to the same canvas tools, the same composition checks, and the same on-demand knowledge files that teach Brilliant-specific patterns (effects, shaders, tokens, typography scales). What they don't get is the streaming flow on top: composition warnings surfaced live as the agent builds (bad auto layout, wrong sizing modes, collapsed or overflowing elements), so the agent course-corrects mid-build instead of after.

Same model, better prompt, better output.

For teams

Team extends Personal with the admin layer you need to run a team.

One invoice for the subscription. Centralized billing for every seat's unlimited-chat access. Keys and API bills stay per-designer. Brilliant never marks up AI, for teams or anyone else.
Admin dashboard. Live per-seat usage, aggregated.
Aggregated usage only, never content. Admins see message counts and design counts. They do not see the content of any conversation or any design. We take that seriously because we run on our own tool.
User management. Invite, remove, role changes.
Single Sign-On on Enterprise.

The trade is one invoice instead of five, plus an admin who can see what the team is doing without seeing what the team is designing. Tidier, defensible, auditable.

Why this model

We want anyone and everyone to be able to use Brilliant. Our goal is clear: creating the single best design tool to have ever existed.

So how do we make money? We offer an incredible, optional experience. An experience so worthwhile that users actively choose to pay for it.

That's the reason Free includes 10 built-in chat messages a day. External agents over MCP stay unlimited on every plan. Try it out. Fall in love. Never look back.

Try it: Your First AI Chat walks through the basics.
Compare the plans: Plans and billing lays out Free, Personal, Team, and Enterprise.
Set up an external agent anyway: Connect an Agent covers Claude Code, Cursor, Codex, and the rest. Both paths live side by side.