By the Lizard (lizard.build) team. Our October 9 update brings a full Linux desktop with Chromium in an isolated microVM through the desktop template. An agent clicks, types, and browses in its own remote session while you watch the actions live from your browser.
Pause preserves execution state, while the website controls its own authentication lifetime. The SDK quickstart says pause and resume queue work: wait for paused or running status before the next step. It also says open network connections close on pause. Reconnect and inspect the page after resuming; do not assume a signed-in tab proves the next action will be accepted.
Local cookies and files stay on your machine unless you deliberately supply data to the remote task. Isolation separates the agent’s execution environment from your local browser profile. Accounts signed in inside Lizard Sandboxes still have their authorized account powers; choose permissions that fit the task.
You can leave the task running, or pause and continue later. The SDK quickstart describes saving memory and processes on pause and restoring the same ID on resume. Wait for the requested status before continuing. Open network connections close on pause, and websites may require another sign-in after resume.
Our original October 9 announcement and the Sandboxes pause/resume guide provide the release and lifecycle context. Older runtime descriptions in the docs predate this update.
Responses
Join the conversation
Sign in to share your thoughts and interact with the author.
Sign In to Comment