Quick start

From a new install to a running MicroVM with your repo cloned and Claude Code signed in. About ten minutes, five of them waiting for the starter image to build.

The whole walkthrough, narrated (3 and a half minutes). Watch on YouTube.
What this costs. A MicroVM bills while it runs: about $0.13 an hour at the smallest size. Nothing here needs a VPC or a NAT gateway.

Before you start

Steps

  1. Open the app

    The main window shows Get started: a short checklist. Your profile and its region are ticked already. Each line's button opens the place that does it.

    The Get started checklist: Add an AWS profile and Choose regions are ticked; Choose a default image and New workspace are still to do.
  2. Build the starter image

    Press Choose an Image…, then Build Starter Image… and Build. MicroVMs run from an image built in your own account; the starter has git, the GitHub CLI, tmux, Node.js, Python, the AWS CLI, Claude Code and Codex. The build takes about five minutes and you can close the sheet meanwhile. When it finishes it becomes the default image for new workspaces.

    The Build the Starter Image sheet, with the size choices and what the image includes.
  3. Sign in to GitHub

    In Settings → GitHub, press Sign In to GitHub…. The app shows a one-time code; Copy Code and Open GitHub takes you to GitHub, where you paste it and choose which repos the app may reach. MicroVMs get a token that lasts 8 hours and reaches only those repos.

    Settings, GitHub tab, listing the signed-in account and how many repos it reaches.
  4. Make a workspace

    Back in the main window, press New Workspace… and give it a name. A workspace is what every MicroVM you launch from it starts with. Quick start keeps it to a few fields: the image, the repos and the sign-ins.

  5. Choose a repo

    Press Browse Repos…. It lists the repos your GitHub sign-in reaches; search for the one to clone, tick it and press Add. (Add Repo takes a typed owner/repo instead.) Check Connection confirms the access, and says whether you can push.

    The Browse Repos sheet: a search for the repo, and the one match ticked.
    The New Workspace sheet with the repo added; under it, Can push and Connected as the account.
  6. Sign Claude Code in

    Under Claude Code, choose Token from claude setup-token and press Sign In with Claude…. Approve in the browser; the token is saved in your Mac's Keychain and sent only to MicroVMs of workspaces that use it. An Anthropic API key and Amazon Bedrock are the other choices.

    The Claude Code section of the workspace, with a saved token selected.
  7. Save and launch

    Press Save, then Launch. The MicroVM starts in a few seconds; the app then copies credentials and clones the repo, and the terminal opens.

  8. Work with Claude Code

    In the shell, cd into the repo and run claude. A MicroVM is a new machine, so Claude Code asks its first-run questions: a theme, and whether you trust the folder. It's already signed in with your token.

    A terminal in the running MicroVM: Claude Code, started in the cloned repo, answers a question about it.
  9. Copy files both ways

    Upload… copies files from your Mac into the MicroVM's home folder; you can also drop them on the terminal. Download… browses the MicroVM's files: choose one, or type its path, and save it on your Mac. Files are limited to 100 MB each.

    A notice over the terminal: Uploaded to the home folder.
    The Download from the MicroVM sheet, listing the home folder with a path typed.
  10. Suspend, resume, terminate

    Suspend pauses the MicroVM and its billing; it also suspends by itself after 5 minutes with no terminal connected. Resume and Reconnect brings it back with the session as you left it, Claude Code included. Terminate… stops it for good: anything you didn't push or download is lost, so the app asks first. The workspace stays for the next launch.

    A suspended MicroVM with the Resume and Reconnect button over its terminal.

Next

To keep files between MicroVMs, see A workspace that keeps its files. For everything a workspace can hold, see Workspaces.