Your AI team.
A crew of agents that plan, build, review each other, and ship — for you. Many tasks at once, each sandboxed on your own machine.
Today that's shipping software — real PRs, in‑app review, live previews. Built to do far more.
The model
Four ideas that make Uai a team, not a tool.
01A team, not a chatbot
Design reusable agents — a name, an @handle, a brief, an
engine, skills, and memory that carries across tasks. Group them into
teams. They draft the backlog and review each other before anything
reaches you.
02Parallel & reviewable
Run many tasks at once — each in its own container and
git worktree. Follow the chat, steer mid-run, and review
every diff in-app, split or unified, before it ships.
03Your machine, but never loose on it
Tasks run on your own hardware, with your keys, in your name — yet each is sealed in a throwaway container and fresh worktree. The cloud stays secret-blind: it holds an env schema, never your keys or tokens.
04Multiplayer
Invite teammates into a task's chat. @mention people and
agents in the same channel and the orchestrator routes to each. When
an agent @mentions you, it pushes to your browser or phone.
Get started
Three steps to your first task.
- 1
Add a host
Install the host on a machine you control —
npm i -g @runuai/host, or the Uai Host app — and pair it with a one-time enroll code. That's your unbilled compute; bring your own AI keys, never marked up. - 2
Design your crew
Create personas —
@handle, engine, skills, permissions, memory — and group them into teams. Design once, reuse across every task. - 3
Start a task
Point a crew at a repo and set the goal. Each task spins up its own container and worktree; watch it run, review the diff, and open the PR — as you.
In-app review
Review every diff before it ships.
Not "go check GitHub." A diff drawer inside Uai spans every repo in
the task, viewable split or unified, comparing
task/<slug> against your default branch. Approve
what's right; send the rest back with a message.
Every running task also exposes a live preview URL — open the app on your phone or hand it to a teammate while the work is still going.
How Uai compares
One chat, or a team?
Most tools give you one agent, one task, one chat. Uai gives you a team running many — and you review every diff before it ships.
| Devin · Cursor Agents | Aider · Continue | Claude Code · Codex alone | Uai | |
|---|---|---|---|---|
| Team of agents | One agent | One agent | One agent | A crew that reviews each other |
| Parallel tasks | In their cloud | One at a time | One at a time | N isolated, on your machine |
| In-app review | On their platform | In your editor | In your terminal | Diff drawer, every repo, before it ships |
| Attributed PRs | Bot-authored | You commit | You commit | Your git identity, your name |
| Where it runs | Their cloud | Your machine | Your machine | Your machine |
| Per-task isolation | Their sandbox | Your working copy | Your working copy | Throwaway container + worktree |
| Multiplayer | — | — | — | Humans + agents in one chat |
Run a team, not one chat.
Design a crew, point it at your repo, and watch tasks ship in parallel — on your machine, with your keys, in your name.