Docs

Quickstart

MIOSA runs isolated Linux sandboxes and full cloud desktops for your code and your AI agents, then publishes the result to a live URL. This page takes you from install to an app that an agent built, in four steps.

Quickstart, explained 1:35

Let your agent drive MIOSA

Most people run MIOSA through a coding agent, not by hand. Your agent can run on your laptop and control the whole platform. It has four ways in:

Way inWhat to do
CLIYour agent runs miosa commands. Start it with the Agent operating guide.
MCP servermiosa mcp install --client claude (also cursor and gemini). OSA and Hermes use a config file instead: see MCP.
SkillsClaude Code skills for sandboxes, computers, and deploys. See Claude Code skills.
llms.txtPoint any agent at miosa.ai/llms.txt. It lists every docs page in plain text.

This works with OSA, Claude Code, Codex, OpenCode, Hermes, Kimi Code, and more. The rest of this page puts an agent inside a sandbox.

Already know what you need?

1. Install

The installer does these steps:

  1. Detects your OS and CPU.
  2. Downloads the matching miosa binary and checks its SHA-256.
  3. Installs it to ~/.local/bin/miosa (or /usr/local/bin when run as root).

Then run miosa login to sign in: it opens your browser, and the key for this machine is stored in ~/.miosa/config.toml. Prefer npm, Homebrew, or a manual download? See Install the CLI or SDK.

2. Start a sandbox

miosa create my-box --wait     # provision a sandbox and wait until it is ready
miosa list                     # see all your sandboxes

A sandbox is a fast, isolated Linux VM. Your agent writes files into it, runs commands, and opens ports as live preview URLs. Its filesystem persists when the sandbox pauses, so you can resume it later. Read Sandboxes for sizes, limits, and lifecycle.

3. Run an agent inside it

Pick your agent. MIOSA installs it in the sandbox and runs it there. The agent uses your own model account, so you pay your own provider. MIOSA credits never pay for the model.

Each agent has three parts: connect your account, start the agent, and give it a task.

If you have not connected an account, the run is refused or fails. MIOSA never falls back to its own keys.

4. See what it built

miosa preview create my-box 3000 --visibility public

Open the URL it prints. That is the page your agent built, served from inside the sandbox.

If nothing loads, the agent did not leave a server running. Start one yourself:

miosa process start my-box --name web --cwd /workspace -- python3 -m http.server 3000 --bind 0.0.0.0

Or do it by hand

You do not need an agent for this. Write a file, start a server, and open a preview yourself.

Open the preview URL MIOSA returns. Your index.html is served live from inside the sandbox.

Pick what you need

You want toProductStart here
Run code, builds, tests, and dev serversSandboxCreate and connect
Drive a browser, a desktop app, screenshotsComputerComputers overview
Ship an always-on app at a public URLDocker HostDeploy overview
Run an AI agent against a sandbox or computerAgent RunsAgent operating guide
Build a white-label product on MIOSAPlatform buildersPlatform overview

Next

Sandbox to deployment

The full first walkthrough: create a sandbox, write files, preview, publish to production, and prove the deployment is live.
Agent-driven build

Dispatch work to your agent, stream events, and collect artifacts from your backend, with external attribution.
Docker Host

Run containerized applications on a workspace Docker Host host.
Connect your own server

Run your first command on a Linux machine you operate.

Concepts Every MIOSA primitive in one architecture reference.
API reference Every endpoint, error code, and webhook.
Was this page helpful?