Myrax docs

Getting started

Four steps between an empty machine and a finished build. Every step below was run end to end on a clean Linux user before this page was written, including the failures.

Four steps between an empty machine and a finished build. Nothing here needs a credit card, and your model accounts stay signed in on your own computer. Every step below was run end to end on a clean Linux user before this page was written, including the failures.

1. Install the Connector

The Connector is a small program that runs on the computer where your code should live. It detects the agents you already have (Claude Code, Codex, OpenCode, Ollama), keeps your provider credentials on that machine, and talks to this server over an encrypted connection. It needs Node 20 or newer and never asks for sudo.

Looking for the latest release…

The one-line script does four things and nothing else: it reads the release manifest for the exact version, downloads that archive into a temporary folder, compares its sha256 with the published one and stops if they differ, then extracts and hands over to the installer inside. A truncated or swapped download never gets executed. Full options live on the download page.

What is on this computer right now?

Checking this computer for the Connector…

2. Pair your computer

Run myrax-connector pair <server-url> and type the six-digit code it prints into your dashboard, under Your computers. The code expires in ten minutes. The computer then appears as a device you can rename or revoke at any time, and the token it received stays on that machine.

Then run myrax-connector daemon and leave it running. It sends a heartbeat every fifteen seconds and, on the same tick, asks whether anything is queued for this machine. While it runs, builds you start from the dashboard are picked up here, in your own folders.

3. Connect the accounts you already pay for

Sign in to Claude Code, Codex or OpenCode on that computer, or run a local model through Ollama. Myrax never sees those passwords and never stores the keys: it asks the harness on your machine to do the work. A provider API key you save in Providers is passed to the agent as an environment variable for that run only.

Before pairing, myrax-connector doctor prints what it found, in this shape:

[ok  ] Node.js                  v22.23.3
[ok  ] A writable home folder    /home/you
[ok  ] An agent to do the work    codex 0.169.0, opencode 1.19.6
[ok  ] Browser for the build test  google-chrome launched and rendered a page
[warn] A model to answer with     No Ollama or OpenAI-compatible server here
[FAIL] Paired with a server       No device token on this computer

The warn is normal if you plan to use a cloud agent. It only matters when the agent you selected has no credential, and the dashboard says that plainly as “needs a sign-in” instead of failing a build later.

4. Describe your first app

Pick a template, landing page, booking page, online store, or connect a repo you already have. The Lead agent turns your words into a plan, shows you the plan, and waits for your approval before any file changes. From there the Builder writes, the gate tests in a real browser, and one repair pass runs if a check fails. How a build works follows a single build through every stage and names the states you will see.

If a step fails

  • No agent is detected. Install Claude Code, Codex or OpenCode, or run a model in Ollama. doctor names the exact command.
  • Installed but not ready. The agent has no credential. Sign it in on that computer, or save a key in Providers.
  • A build waits for a machine. The daemon is not running, the computer is offline, or the chosen engine is not installed there. The dashboard card names which one.
  • The gate fails twice. The build is marked as needing another pass, with the failed checks and the value each one measured.

Removing it again

Each download is published with its sha256, and the installer proves the new version starts before replacing an older one, so a broken download cannot leave you with a Connector that never runs. To remove it:

myrax-connector uninstall --yes

Your device stays listed in the dashboard until you revoke it there, which is deliberate: an uninstall on one machine should not silently orphan a row the account owner can no longer see.

Already have payments wired up?

Connect the repo and ask for the specific fix. The agent maps your stack first, makes a checkpoint, and leaves your payment integration untouched unless you say otherwise.