Browse documentation
Documentation

Choose your tools

Export and run your code outside Rigless

Download your source, run a Free project on your own computer, and prepare a hosted app for another environment.

Updated September 7, 2026 4 min read

Keep a copy of your source on your own computer, in your repository, or at another host. This guide walks through exporting a Free project and running it locally, then explains the additional steps for hosted projects.

What an export contains

Path

What you receive

Free Browser project: Export project ZIP

The project's current files and folders as a ZIP

Hosted project: Download workspace

A named project folder in a .tar.gz archive; Git metadata is removed

Hosted GitHub workflow

Changes pushed to your repository through the pull request flow

A workspace download is a copy of source files. It does not transfer Rigless's account settings, saved file history, agent conversation, published releases, or separately configured production variables. If you need Git history, use your GitHub repository.

An application may also need dependencies, database contents, uploaded files, and external-service configuration. Keep track of those separately when moving a running service. Any secrets you put directly in project files can travel with those files, so inspect the archive before sharing it.

1. Export a Free project

Use the tip calculator from Build and publish your first app, or another project made from plain HTML, CSS, and JavaScript. Finish the active run and check that the preview works.

In the project, open the three-dot Session menu and choose Export project ZIP. Your browser downloads a ZIP named after the project. Extract it into a new folder on your computer.

For the tip calculator, confirm that the extracted folder contains index.html, styles.css, and app.js. If your agent used a subfolder, open that folder. The paths in index.html should refer to the accompanying files.

2. Run it locally

For the plain tip-calculator example, open the extracted index.html in your browser. This runs your copy from your computer without signing in to Rigless.

If the project uses browser features that require HTTP, serve the extracted folder locally. With Python 3 installed, open a terminal in the folder containing index.html and run:

python3 -m http.server 8080 --bind 127.0.0.1

Open http://127.0.0.1:8080 in your browser. Keep the terminal open while using the app; press Ctrl+C there when finished.

3. Check your independent copy

For the tip calculator, enter a bill of 80, a tip of 20%, and 4 people. Expect a total of $96.00 and $24.00 per person. Try zero people and a negative amount to check validation.

Open index.html in a text editor, change the page title or heading, save it, and reload the local page. Seeing that change confirms you can edit and run this copy using your own tools.

This exported copy is separate from the Rigless project and its published release. Local edits do not update either one automatically. You can continue working locally or upload these static files to a host that serves ordinary HTML, CSS, and JavaScript.

Download a hosted project

Finish the current run, then open Advanced from the simple project view. On a phone, use the code icon beside the three-dot menu. Open Session menu and choose Download workspace. Extract the .tar.gz file into a new directory.

Open the project's README and dependency manifests before running it. A workspace download does not recreate the Linux machine, its system packages, or a running database. Install the language runtime and dependencies the project calls for, configure required values, and use the project's documented startup command.

Before exporting, you can ask the agent to make that setup explicit:

Update the README so I can run this project outside Rigless.
List the required runtime versions, dependency installation commands,
environment variable names with safe example values, database setup,
startup command, and relevant checks. Do not copy private credentials.
Run the commands you can verify here and identify anything still untested.

Run those checks on the new machine. For a deployed service, verify the new host's configuration and data before directing visitors there.

Keep work in GitHub

If your hosted project is connected to GitHub, use Changes → Create PR to send the reviewed work to the repository. Open the PR on GitHub and confirm it includes your changes. You can then clone or check out that branch with your normal tools.

Unpushed workspace edits are not present in the remote repository. A source download can preserve those edits, but it excludes .git; use the repository when you need branches and commit history. Follow the GitHub workflow.

If the exported project does not work

Problem

Check

The page has no styling or behavior

Confirm the asset files were extracted and that their paths match the HTML

Browser features fail when opening a file

Serve the project over localhost with the command above

A hosted app reports missing packages

Install the runtime and dependencies from its README and manifests

An API or database connection fails

Configure the new environment and move the required data separately

The download reports no workspace

Confirm the project has files and a completed run; contact support if it still fails

The repository is missing recent work

Check that you pushed the changes and opened the correct branch

Contact support@rigless.ai with the project URL and error if you cannot retrieve your files. Keep keys and private data out of the message.