The questions that come up most — about the model, the storage, the price and the limits. Each answer is short and points at the page that goes deeper.

Does 1DesignTool have its own AI model?

No — the agent doing the design work is a coding-agent CLI you install: Claude Code, Codex, Cursor Agent, Devin and twelve more. The app is the studio around it — the live preview, the design kit, the steering tools — and the runs bill to your own agent account, not through a service the app owns. See Supported coding agents.

Where does my work live?

On your disk — a project is a folder you picked. Nothing is uploaded to an account or a sync service; the preview server is local and default-deny. Deleting a project deletes its folder. See Privacy: what leaves your machine.

What does the free tier limit?

Volume, not features — every template, tool and export runs free. The caps are lifetime counters: 300 prompts, 50 renders, 3 live versions per project, 4 variant builds, 3 saved design systems, plus a watermark on rendered output. ZIP/HTML code export is never metered. See Free vs Pro.

How much is Pro?

$29 / $59 / $89 for 1, 3 or 5 devices — one-time, covers 12 months of updates, and the build you have keeps working after that. Pro lifts the caps and removes the render watermark.

Can it export to PowerPoint or Figma?

Exports are ZIP, HTML, PNG, PDF and MP4 per the template — there's no PPTX export, and Figma import is a render target (an image placed on the canvas), not editable layers. Export formats lists what each template ships.

Does it work offline?

Mostly — projects, previews and history are fully local. What needs the network is your agent CLI (runs go to its service), license checks, and update downloads. Steering, browsing and exporting local work runs without it.

Is my code or design sent anywhere?

Only to your agent CLI — a turn carries the brief plus the context it needs to your own CLI's service. Licensing and updates make their own narrow calls. Nothing goes through a 1DesignTool server for the work itself.

Can I use it on a repo I already have?

Yes — adopt a repo registers the codebase on an app-owned 1design/<slug> worktree branch, so the agent designs inside your real UI without touching your checkout. Adopt a code repo covers the model.

Tip: Most "can it do X?" questions land on a docs page — the sidebar is the map; start with What is 1DesignTool? for the shape of the whole thing.