Avio

Cloud agent swarm

Send your agents to the cloud.

The CLIs you already pay for, on a machine per task. A thread pushes, opens the pull request, fixes what CI complains about, shows you a preview and stops at the merge. You tap, from the laptop or the phone. One website, nothing to install.

  • On the subscription you already pay for
  • Claude CodeClaude Code
  • CodexCodex
  • opencodeopencode
app.avio.run/#/thread/412

The same panel in a desktop browser and on a phone.

Your own seat

The subscription you already pay for.

Avio rents no model tokens and resells no seat. You sign in to Claude Code, Codex or opencode once on your own machine, with your own plan, and every thread runs that binary unmodified. The model bill stays yours. Ours is the machine.

  • No credits to buy, no markup on tokens
  • One login per person, never a shared seat
  • Switch harness per thread from the composer

What a thread does

One machine each. As many as you want.

A preview of its own

Every thread runs the dev server on its own machine. The panel shows it, the agent screenshots it into the pull request and writes a checklist of what to look at.

Ten threads are ten machines

A machine is cut when a thread opens and billed while it runs. Its own port 3000, its own database, its own disk. Nothing shares a worktree with anything.

No VPS to keep

Nothing to provision, patch or ssh into. Sign in to each CLI once, on a home machine in the panel's terminal. Every thread is a fork of that home.

How it works

Your subscription. Our machines.

  1. 01

    GitHubSign in with GitHub

    Install the Avio App on the repositories you pick. Avio never holds a token of yours.

  2. 02

    Claude CodeCodexopencodeLog in to your CLIs once

    Claude Code, Codex, opencode. Your own seat, on your own home machine, the way you would on a laptop.

  3. 03

    Open a thread

    From a prompt on your phone, or from a trigger you approved once: a Sentry issue, a failed check, a schedule.

  4. 04

    Tap merge

    The thread stops at the merge with checks green and a checklist you can walk. One tap, or a teammate's.

The team

The thread is shared. The seat is not.

A teammate sees what a thread is, where it stopped and its preview, and can walk the checklist. Every person runs their own login on their own machine. No shared seat, which is what the vendors' terms ask.

Open the panel