Durable AI coding without a development VM

A small HTML, CSS, and JavaScript project can be useful without a Linux development machine. You still want its files to be there when you return, and you want the agent's work to survive a closed tab. Rigless's Browser workspace separates those needs from the decision to allocate hosted compute.

Save the project to the account

Browser project files and the main conversation are saved privately to the Rigless account. Your browser keeps a synchronized copy for editing and static preview. When you sign in on another device, the interface can load the saved project again.

The main agent run is managed by the server. Closing a page does not make the tab responsible for finishing the model request or retaining the only copy of a file change. On reconnect, the interface catches up with the run's saved state. A run can still stop for a question, a usage limit, or an error; durability does not imply unlimited execution.

Match the tools to the workspace

Browser projects use the built-in Rigless agent with file and search tools. The agent can create a page, change its styles, or fix a calculation. It cannot install packages, execute a test command, start a backend, use Docker, or take runtime screenshots.

For a tip calculator, that is a useful division of work: the agent edits the files, and you enter a known bill, tip, and party size to check the result. If the project grows to require a server or build process, continue from its source in a hosted workspace.

The workspace guide explains how to choose and how to make that source handoff.

Keep publication and export explicit

Saving a project keeps it available to your account. Publishing creates a separate release that visitors can open. Downloading a ZIP gives you a copy of the current source files to use with your own tools. Each action serves a different purpose.

Free includes one bounded, branded static publication. Editing the private project does not automatically update that release. Likewise, an exported file edited on your computer does not update the Rigless project automatically.

Storage and AI allowances have limits, and side questions have a temporary lifecycle. Keep important decisions in the main conversation or source, and make a separate source copy at useful checkpoints.

Try the complete loop: build a static app, check it, and publish it, then run the exported files locally. The useful result is a project you can return to and source you can continue using elsewhere.