Oleg Isonen
bc29c51be8
# Screenshot failures on Linux and fragment captures On the reported Linux host, Chrome aborted before screenshot capture. This PR keeps the normal launch unchanged and makes the existing second attempt use Chrome's shared-memory fallback on Linux. The original host is unavailable, so this is a best-effort recovery, not a proven fix for that host. On #6580's project, a fragment URL made Webstudio mark a navigation link active in the browser while the server rendered it inactive. That mismatch caused a React hydration warning, which the current MCP screenshot tool correctly rejected. The link now renders consistently during hydration and becomes active afterward. The exact project's managed MCP responsive capture then succeeded twice at desktop and mobile sizes; both PNG files existed. Closes #6587 Closes #6580 ## Work - [x] Add a Linux-only fallback on the existing browser startup retry. - [x] Add a regression test that fails without the Linux fallback. - [x] Make initial fragment-link rendering match server and browser during hydration; preserve active-link behavior afterward. - [x] Add a hydration regression test that fails before and passes after the fix. - [x] Verify the exact-project managed MCP fragment capture at 1440×900 and 390×844, `waitUntil: load`, `waitForSelector: img`. - [x] Review `docs/`: the existing link and screenshot instructions remain accurate; no docs edit is needed. - [x] Run focused Vision/CLI, link and router-link tests; relevant typechecks, formatting, lint, builds, and diff checks. - [x] Independently review the complete diff. - [x] Review required CI checks: all checks on `e79053414e` passed (visual regression was skipped by its workflow). Remaining costs and limits: a Linux browser still makes the first startup attempt before the fallback. The fragment capture still needs the generated preview and browser startup. The original CLI 0.306.0 second-viewport timeout and the Linux reporter's host were not retested with this patch. This PR does not add a diagnostic PNG on readiness timeout or a new section-scroll control. We are closing these reports on merge with those limits understood; if the symptoms recur, they need a new report.
Webstudio CLI
The Webstudio CLI helps you to link, sync and build projects from Webstudio Cloud. This README will guide you through the process of setting up a Webstudio project on your local machine and continually sync it with the cloud.
Prerequisites: Installing Node.js
You need Node.js to use the Webstudio CLI. If Node.js is already installed in your system, you can skip ahead to the section on installing the Webstudio CLI.
To install Node.js using NVM, first install NVM by running:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.5/install.sh | bash
Once NVM is installed, you can install Node.js version 22 by running:
nvm install 22
Verify your Node.js installation by checking its version:
node --version
Installing the Webstudio CLI
To get started with the Webstudio CLI:
-
Download and install the CLI using the following command:
npm install -g webstudio@latest -
Confirm the installation by checking the CLI version:
webstudio --version -
To keep your CLI updated, use the same command used for installation whenever a new release is available.
Initiating a Webstudio Project
Now, you can run a Webstudio project on your local machine using this command:
webstudio
This will initiate the flow to connect your Webstudio Cloud project and build it in your local computer. The default flow will guide you through the steps. You can also perform all the operations individually using independent commands.
Commands
Here is the list of independent commands:
- version
- help
- link
- sync
- build
link
The link command stores access to a Webstudio Cloud project. MCP clients use that connection to read and edit the latest Builder build directly; the project does not need to be published or synchronized first.
Shell-capable agents can call MCP tools directly as CLI subcommands immediately after linking. This does not require MCP client configuration or a client restart:
webstudio meta.index
webstudio components.search '{"brief":"button"}'
webstudio insert-fragment --input-file .temp/insert-fragment.json --dry-run
.temp/insert-fragment.json:
{
"parentInstanceId": "<parent-id>",
"fragment": "<section />"
}
The explicit equivalent is webstudio mcp single-op-call <tool> '<json>'.
Use webstudio connect <client> only when you want persistent native MCP tools
inside Claude Code, Codex, Cursor, or VS Code. A persistent client may need to
reconnect after its configuration or cached tool catalog changes.
See the Webstudio MCP documentation for setup, discovery, editing, verification, and safety guidance.
You can link a project from Webstudio Cloud with the following command:
webstudio link
This command will prompt you to paste a link which you can create using the Share option in your project.
Make sure to provide Build access when generating the link in Webstudio Cloud.
sync
Once the project is linked, use the sync command to sync it with the cloud:
webstudio sync
Sync downloads the current saved Builder project and its asset files, then prepares the local content index. Publishing is not required.
Use the export with webstudio build or webstudio import --to "<target-share-link>". Sync is not required for MCP editing.
build
Now, you can build your project with the build command:
webstudio build
During this phase, the CLI establishes the necessary routes and pages, scaffolding the entire application using the default Remix template. Additionally, all assets, such as images and fonts are downloaded to the assets folder inside the public directory.
Once the project is scaffolded, you can run npm install and then npm run dev to run your app in development mode.
If you want to build a production version of the app, you can run npm run build.
Deployment
Vercel
Once you've built the project locally, you can use the Vercel CLI to deploy your project directly to Vercel:
vercel deploy
Follow the instructions here to install the vercel CLI. We plan to add more deployment targets in future.
Netlify
If you want to deploy to netlify, you can use Netlify CLI to deploy your project directly to Netlify:
netlify deploy
You can configure the project to support netlify serverless/edge-functions respectively, as deployment target at the time of initially setting up your project. Please check the initiating-a-webstudio-project section.
You can manually change it using the build command. For serverless functions:
webstudio build --template netlify
Important Notes
If you use vercel build before vercel deploy, make sure to clean your app folder in the project afterward.
Vercel injects a few files to support and deploy Remix using their CLI, but these files are not necessary for your project when you use it locally.