In-app AI

Fanta includes an Agent Panel for design work inside the desktop editor. The panel can read the current design and design system, make structured edits, inspect comments, capture screenshots, and place generated images. Source-capable modes can edit saved FNX and managed JSON files.

Start with the document

Open a Fanta project or imported Figma file, then describe the page, frame, or selection you want changed. Give the agent dimensions, content, style, reference images, and constraints where they matter. Ask it to inspect the design and show a screenshot after each meaningful change.

The built-in design tools include design_state, design_system, design_edit, design_screenshot, design_comments, prepare_design_asset, and place_generation. Read design_system before creating variables or components. design_edit paints ordered operations on the live canvas one by one, then commits a labeled batch as one undo step. A failed or canceled batch rolls back its preview. Build one visible component or screen section at a time; inspect each milestone before continuing.

Use a project-root fanta.md to give the native designer a product brief, visual direction, layout and asset preferences, design-system conventions, and acceptance checks. It reads that file before each model round. Nested specifications refine workspace rules, with a 64 KiB combined limit; direct user instructions and the selected mode's permissions take precedence. See project context.

In current source, a native Agent turn is limited to 64 model requests across tool continuations, agent-managed retries, model fallback, and automatic compaction. Provider-internal retries are outside this count. At the limit, the turn stops with a visible message and keeps completed work. Send a new message to start a fresh turn. This is a request limit, not a credit or spending cap; the release recordings do not establish native acceptance of this limit.

Choose an agent mode

Edit Visual applies undoable canvas operations. Write and Full Access can edit saved FNX and managed JSON source. Ultra coordinates specialists on larger tasks. Plan and Review preserve the scene while they inspect and advise; Plan can read comments but cannot reply or resolve them. Available tools depend on the selected mode and model.

After a successful completed Plan response, the panel offers Apply plan and Keep planning. Applying switches that thread to Write mode and sends an implementation request for the plan; keeping it open lets you continue discussing it. The actions appear only after a successful completed Plan response.

Plan & build in Build mode

The editor's Build mode opens a separate Plan & build inspector sidebar. Enter a design brief and choose Plan & build. Fanta sends the current page scene, supported design operations, and the project's fanta.md context to its v2 agent service. The service plans tasks and returns canvas operations for the current task. Fanta applies those operations as one undoable preview for you to review.

Choose Accept to send the resulting scene back for a lint and critique check; Fanta then moves to the next task or offers revised operations when a check fails. Retry can include notes and requests new operations after undoing the latest preview. Skip removes that preview and moves on. Stop ends the session and keeps work already applied. If you turn on Accept each task automatically before starting, the panel accepts previews as they arrive; this switch is off by default. The panel shows task status, reported issues, and credits used.

Build mode requires Fanta sign-in, available credits when charged, and a configured server that offers /v2/agent/sessions. Preview and dev channel defaults target the v2 service; the stable channel default still points to the older API, so Build may report that the v2 API is unavailable. A failed operation batch rolls back; choose Accept to send its errors back to the agent. If you edit the canvas after a preview, Retry or Skip will leave it in place rather than undoing your later edits; use Undo manually if you want to remove it.

Build mode's task-by-task session is separate from the Agent Panel's Plan mode and Apply plan action above.

The Thinking control appears when the selected model reports support for reasoning effort; it changes the request but does not expose private reasoning. The built-in agent can read source files, and source-capable modes can save small, complete FNX subtrees or typed JSON changes. The Code workspace itself edits the selected page or component FNX and its page.json or def.json companion. For other managed JSON, use file tools and validate the complete candidate before writing. See FNX source.

Follow visible work

The agent reports its current action and focus. Follow can move with it across canvas pages, component tabs, variables, and source files; the Code workspace can reveal the reported FNX or JSON path. While an agent reports activity for the open project, the Canvas workspace shows a pulsing edge around the canvas alongside the agent controls. Distinct agent names and colors help identify the lead agent and specialists. In Ultra mode, specialists receive the lead chat's reference images when their model supports image input. The lead can give specialists separate components or pages, and their names remain stable during the work.

Use Pause follow to stop automatic source scrolling while inspecting a file. Activity indicators expire when an agent stops reporting, and the agent should clear its activity when finished. These indicators show focus; they are not cross-agent edit locks.

For an image or SVG icon, the agent can call prepare_design_asset to open a draft in Fanta's generation composer. You review available models and submit it there; preparing a draft does not run generation. place_generation can fetch a generated image URL and place it in the project.

AI provider and account

Fanta's default settings include a managed Fanta AI provider. After sign-in, the provider reads the current chat-model catalog from the service and shows each model's supported tools, images, context size, and credit information when supplied. The app also exposes settings for connecting your own supported provider credentials. Provider availability and model choices can change, so inspect Settings → AI & Models for the options available to your account.

The displayed model price, output limit, and agent profile do not set a total spending cap for a session: tool calls, retries, and auxiliary requests can add usage. Review available credits and the active model before sending. Paid-request pricing and caps have not passed live acceptance in the release coverage report.

Preview and dev channel defaults point Fanta's account, model, edit-prediction, and hosted MCP settings at its v2 backend. Their fanta-design hosted tool connection is enabled in the channel defaults; the stable default enables the account-backed fanta generation connection and lists fanta-design disabled. Service availability and account access still determine what appears in the app.

The Fanta-hosted MCP connections use the signed-in account when their endpoint matches the configured backend and no explicit authentication header is set. A managed connection that receives 401 asks you to sign out and sign in again; a startup timeout leaves an unused OAuth session cached for that endpoint. This is separate from the local canvas MCP bridge. The authentication failure paths have isolated tests, while live managed-tool execution and recovery still need verification.

The built-in agent also registers evaluate_with_jev for typed decisions about supplied text or structured state. It can ask one to eight named boolean, choice, or score questions and returns structured answers instead of a chat reply. The request is limited to 8 KiB, requires Fanta sign-in, and is unavailable in restricted agent mode. The tool describes a minimum charge of one Fanta credit for a successful call; actual availability and billing depend on the connected service. This is an in-app agent tool, not one of the thirteen external canvas MCP tools.

Fanta-hosted chat and generation require sign-in and purchased credits for public accounts. Subscriptions and one-time packs are purchased through web Billing. Public trial, signup, and referral credits are not offered; only designated founder accounts retain complimentary hosted access. Supported provider keys use the connected provider's own billing. See pricing and credits, media generation, and Settings.

Review what changed

Inspect updated layers, source diffs, comments, and screenshots in the editor. Continue with manual canvas tools, request a revision, or undo an edit batch. Structured design operations can create variables, bind compatible properties, combine and edit component variants, set gradient fills, arrange grid layouts, and set exposed instance properties. For individual rich-text runs or another property outside the operation vocabulary, work through FNX source.