Skip to content

Documentation

Everything you need to ship with it.

Start a task in two minutes. Then learn how to steer it, connect your tools, set the rules and take work to production.

Quick start

No setup. Open the workspace, describe what you want and the first machine starts on its own.

01

Open the workspace

Sign up, or try it as a guest. A blank project is ready straight away.

02

Describe the work

Type it or say it. Attach files, screenshots or a GitHub repository.

03

Review the plan

Untick anything you do not want. The rest stays visible as cancelled.

04

Check the result

Read the diff, open the live preview, then keep it or restore a checkpoint.

How a task runs

Every task follows the same seven steps. Three of them are yours; the rest happen on the project’s machine and are recorded as they go.

  1. 1AskDescribe the work in plain words
  2. 2PlanIt reads the code and writes a task list
  3. 3ApprovePick the tasks you want done
  4. 4EditA checkpoint is saved before each step
  5. 5RunCommands and tests on its own machine
  6. 6VerifyEvidence is matched to each task
  7. 7ReportDiff, preview and what is unproven
Waits for you

A task cannot mark itself finished while a deliverable is open. If something could not be proven, the report says so instead of saying done.

Modes and effort

The mode decides how much the agent may do before asking. Switch at any time from the box where you type.

Read only

Plan

Drafts an approach and never touches your files. Use it to think a change through.

Agree first

Brief

Reads the repository, proposes a task list and asks its open questions. Reply with changes as often as you like; once you approve, it builds the agreed list.

Default

Guided

You approve the plan and the files in scope once. Edits inside that scope, tests and builds run on their own. Installs, network access, deletes and edits elsewhere ask first.

Hands off

Auto

Runs builds without approvals. Deletes, history rewrites and force pushes still ask, and a few things are always refused.

EffortWhat it doesGood for
LowFast, light replies.Questions and small edits
MediumThinks hard when planning and when something fails, moves quickly through routine steps.Most work
HighReasons through every step.Tricky bugs and large changes
A real computer for every project.MACHINES, ROLES AND SKILLS

Machines

Each project gets its own isolated cloud computer with common languages, databases, Docker and a browser already installed. Dependencies are set up once and redone only when your manifest files change. Each browser check opens a fresh browser profile, so saved state such as localStorage is only kept within one check.

Free

2 CPUs · 4 GB

Scripts, quick fixes and questions.

Starter

4 CPUs · 8 GB

Everyday apps, tests and previews.

Pro

8 CPUs · 16 GB

Full-stack builds, Docker and databases.

Developer preview

Your laptop

Run the agent locally. Files never leave your computer.

Roles and skills

Give the agent a job title and it changes how it plans, what it checks and which skills it reaches for.

35 roles

Engineering roles

Frontend, backend, data, mobile, security, release and more. Pick one with /role, or let the task decide.

On demand

Skills

Short how-to guides for common stacks. Only a one-line summary is loaded up front; the full guide is read when a task needs it. Add your own with /skills.

Put a short notes file in your repository and every task reads it first: conventions, commands, things not to touch.

You set the boundary. It works inside it.APPS, SECRETS AND SAFETY RULES

Apps and secrets

Connect the tools your work already lives in. Sign in once and the agent can use them, with your approval, in any project.

446 apps

One-tap sign-in

Search for an app, sign in on its own page and come straight back. On a phone it opens in a sheet you can close.

GitHub

Repositories

Import a repository, keep it in sync both ways and open pull requests from a finished task.

Encrypted

Vault

Store keys once for your account. Commands receive them as environment variables; they are never pasted into code or shown in replies.

Actions in a connected app ask for approval even in Auto mode. Every write is scanned for secrets before it is saved or pushed.

Safety rules

Rules live in a file in your repository, so they are reviewed like any other change. A team can tighten them for everyone, never loosen them.

# .mlai/policy.yml
production:
  branch: main
  require_pr: true            # no direct pushes to production
  require_ci_green: true      # every check must pass before promotion
  min_approvals: 1
  block_paths_without_review: ["infra/**", "payments/**"]
agent:
  modes_allowed: [plan, brief, guided]
  commands:
    allow: ["npm test", "pytest*"]     # run without asking
    deny:  ["terraform apply*"]        # never run, in any mode
secrets:
  scan: true
  ignore_paths: ["tests/fixtures/**"]
Always refused for the agentWhy
Piping a download into a shell inside a workspaceRuns code nobody has read. The CLI install command is for you to run on your own computer; to read it first, download install.sh, open it, then run sh install.sh.
Publishing packagesReleases go through the release flow.
Force pushesRewrites history other people depend on.
Reading SSH keysCredentials stay out of the conversation.
Production deploys from the terminalProduction goes through the deploy review only.

Shipping

From a finished task to production, with a person in the loop where it matters.

01

Pull request

Open a draft from the task. It needs a passing check newer than the last change, unless you choose to publish without one.

02

Preview

Deploy a preview to Vercel, Netlify or Cloudflare and open it on any device.

03

Promote

Production needs a review. The card shows the checks, the diff and who may approve.

04

Roll back

Every deploy is listed. Go back to an earlier one in a tap.

Teams

Invite people by email and give each one a role. Shared projects show who started what, and a team audit log records approvals and deploys.

RoleCan
ViewerReads runs, changes, deploys and logs. Cannot start or approve anything.
ContributorStarts runs, approves plans and commands, edits files, opens pull requests.
MaintainerEverything a contributor can, plus connected apps, preview deploys, direct pushes and repository rules.
ReleaserEverything a maintainer can, plus production deploys, rollbacks and releases.
AdminEverything, plus members, invites, team rules and the team audit log.
OwnerCreated the team. Everything an admin can, plus deleting the team.

Apps and CLI

One account everywhere. Start on your phone, approve on the train, finish at your desk. See all downloads for what is available on each platform.

Browser

Web

The full workspace: projects, previews, diffs and a terminal side by side.

Phone

Mobile

Built for one hand. Voice input, approvals and previews on the go.

Terminal

Command line

Run tasks from your own shell and sign in with your account.

curl -fsSL https://mlai-mini-code.vercel.app/cli/install.sh | sh

Commands

Type a slash in the message box for shortcuts.

/goSkip the plan questions and build right away
/newStart a new project
/planSwitch to Plan mode
/buildSwitch to Guided mode
/roleChoose an engineering role
/diffOpen the changes
/scheduleSchedule a recurring task, e.g. /schedule weekdays 9am run the tests
/connectConnect an app
/mcpAdd a tool server
/skillsManage skills
/agentsOpen helper agents
/browserOpen the live preview
/importBring in an earlier session
/publishPublish a page, report or deck to a shareable link
/settingsOpen settings
/doctorRun a health check and fix problems
/centerSee every chat in one place
/helpOpen the command menu

Curious how it works inside?

The systems behind it, and what we have measured.