Alpha: Exporting your site to code is currently in alpha. This feature is subject to change and may have bugs, issues, and limitations. We're actively improving it based on your feedback.
Add to and change the pages, theme, and extensions of an exported site with a coding agent, then check that your changes can import back into Studio Two.
Make sure you have:
The exported site includes resources for coding agents. When you open the site's folder in a coding agent, the agent reads the instructions and follows the editing skill. You describe the change, and the agent makes it in a form Studio Two can import. After each change, the agent runs the project's lint, which checks the site's files against the import's rules, and fixes what it reports.
To edit with a coding agent:
Open the root of the exported site in your coding agent so the agent finds its instructions.
Start the preview so you can watch the changes:
Describe the change you want in plain language. For example:
Review the result in the preview at http://localhost:3000.
Repeat until you're satisfied, then import your changes.
The exported site includes a lint that checks the site package against the import's rules. A coding agent runs the lint after each change. If you change files yourself, run it after each change and before you import.
To check your changes:
In the root of the exported site, run:
The lint checks the pages that changed since its last passing run. To check every page, run yarn lint --full.
Fix each error that the lint reports, then run it again until it passes. Warnings don't fail the run.
A passing lint means the changes are likely to import, but the import itself is the final check.
Last updated: 2 November 2026