Getting started
Choose Browser or hosted compute
Choose the workspace your project needs, continue from another device, and understand source handoffs and Browser storage limits.
Choose a workspace based on what your project needs to run. Browser works for static web projects and is available on Free. Hosted adds Linux tools and the broader agent selection on a paid plan. Both save the main project's files and conversation to your Rigless account.
Choose the workspace for your task
Your task | Workspace |
|---|---|
Build a calculator, landing page, or browser game using plain HTML, CSS, and JavaScript | Browser |
Install packages, compile source, or run a framework development server | Hosted |
Work on a GitHub repository and open a pull request | Hosted |
Run a backend, database process, Docker container, or automated browser checks | Hosted |
Try Codex, opencode, Pi, or Oh My Pi alongside the built-in Rigless agent | Hosted |
Browser projects use the built-in Rigless agent. It can read and edit project files, search the source, and ask questions. You check the result in your browser. It cannot run a shell, install dependencies, start a backend, or inspect the running page with screenshot tools.
A hosted workspace provides an isolated Linux environment. The selected agent can use the tools its integration supports, and you can inspect files, command output, and changes yourself. A hosted plan provides compute; successful setup still depends on the project's dependencies and configuration.
Start in the right place
On Free, open Create and describe a static app. The default Browser workspace is already selected. Build your first app provides a complete example.
For hosted work, open Developer workspace. Choose a hosted agent above the task field, then choose a compatible model. Connect a repository if your project uses GitHub. Follow Choose your agent and model for the controls and compatibility limits.
Continue a Browser project with hosted tools
Moving to hosted compute is a source handoff. Finish the active run and use Session menu → Export project ZIP to save the current files. Extract and inspect the copy before continuing.
One reproducible path is to put those files in a GitHub repository you control, then open that repository in a new hosted project using the GitHub workflow. Tell the new agent what works, what you want to add, and which checks it should run.
The new project has a separate conversation. Moving source does not transfer the old agent's history or move a published app, its data, or production configuration. Keep the original project until you have checked the replacement.
Return from another device
Sign in with the same account and open the project from your recent projects. Browser files are saved on Rigless; your browser keeps a synchronized cache for editing and preview. The main agent run can continue after the tab closes and the interface catches up when you return.
Side questions have a separate, temporary lifecycle. Copy decisions you want to keep into the main conversation or project files.
Understand Browser storage
Verify your email before creating or saving Browser projects. The account limits below include Browser side-conversation sessions while they remain stored.
Plan | Project/session limit | Saved file data, including history | Saved files |
|---|---|---|---|
Free | 5 | 100 MiB | 10,000 |
Starter | 20 | 500 MiB | 25,000 |
Pro | 50 | 1 GiB | 50,000 |
Max | 100 | 2 GiB | 100,000 |
An individual Browser workspace allows up to 100 MiB of current files, with a 10 MiB per-file limit. Archived projects still count. Export important work before deleting an unused project to reclaim its files and history. If a side question hits the project limit, discard an unneeded side question or free a project slot.
Publishing has separate limits. Free includes one branded static site of up to 25 MiB. A published release is separate from your editable source; export a copy or push hosted changes to GitHub when you reach a useful checkpoint.
Was this guide helpful?