An open-source zero-human ops platform 🦾🩶
English | ç®€ä½“ä¸æ–‡
UFO orchestrates AI sessions into a zero-human ops loop for complex work, not just coding. Work lands on the board, context keeps compounding, and each run can hand off cleanly to the next while workspaces and credentials stay on machines you control.
- Operate together. Missions frame projects; operations move through Kanban, list, and lane views with comments, assets, labels, relationships, signals, crews, and membership.
- Run pilots locally. Rovers use supported AI CLIs on machines you control. Code and secrets stay local, and every run gets an isolated worktree.
- Keep work moving. Routines pulse now or on a schedule and can continue their Loop after an operation is done. Optional auto-commit supports unattended legs with stall and fail-closed guards.
- Learn and ship. Mission learning carries reusable experience into shared docs and skills for future operations. Forges connect GitHub or GitLab so rovers can push and ship pull requests with a host-side token.
No cloud account is required.
Needs: Docker and
Rust/Cargo, plus at least one
supported AI CLI on PATH.
git clone https://github.com/fengsi/ufo.git
cd ufo
scripts/dev.sh upOpen http://localhost:3000 and create an account. UFO opens a personal fleet and a default Launch Bay mission.
scripts/dev.sh rover enroll
scripts/dev.sh roverApprove enrollment in the browser when prompted.
- Open a mission (project frame on the fleet).
- Create an operation and assign a pilot.
- Watch the board: queued → accepted → running → review/done, with live updates and a diff when code changed.
That's the loop. Routines, skills, crews, and auto-commit all build on it.
Both rover commands need a running Hub. Today's public beta path is a local
Hub from scripts/dev.sh up; use either the dev wrapper or the released CLI
binary to connect a rover to it.
# macOS / Linux
curl -fsSL https://getufo.dev/install.sh | sh
# or: brew install fengsi/ufo/ufo-cli
# with the local Hub already running from scripts/dev.sh up
ufo rover enroll --hub http://localhost:8080
ufo rover startTo connect the same host to another Hub, enroll again with that Hub URL (or
use repeated --config entries with enrollment codes). ufo rover start
loads the stored enrollments from ~/.ufo/rovers.json. Set units per rover
to accept concurrent operations while reusing the same local AI CLIs.
Windows: download the matching archive from
Releases, put ufo.exe on PATH,
then the same enroll / start commands. Details:
apps/rover/README.md.
Release artifacts cover macOS, FreeBSD, Linux, and Windows. Routine CI tests run on macOS, Linux, and Windows.
| Word | Plain meaning |
|---|---|
| Fleet | Trust boundary: people, rovers, missions, and operations |
| Hub | Control plane: API and fleet state |
| Board | Web UI for the fleet |
| Mission | Project frame on a fleet (codes like MSJ-123) |
| Operation | One work item on the board |
| Rover | Local runtime connector that accepts work and runs pilots |
| Pilot | Local AI CLI the rover runs |
| Routine | Reusable operation definition with an optional Pulse schedule and Loop policy |
| Skill | Reusable instruction pack bound to ops or crews |
| Crew | Pilots + humans under one assignment target |
flowchart LR
human["Human"] --> board["Board"]
board --> hub["Hub"]
hub --> rover["Rover"]
rover --> pilot["Pilot"]
rover -- telemetry --> hub
| Piece | Role |
|---|---|
apps/web |
Board |
apps/api |
Hub (auth, queues, OpenAPI) |
apps/rover |
Rover (ufo-cli): local runtime that runs pilots |
flowchart TD
web["Board<br/>Next.js"] <--> api["Hub<br/>Go API"]
api <--> db["PostgreSQL<br/>fleet state"]
api <--> rover["Rover<br/>Rust host"]
rover --> pilot["Pilot CLI<br/>Claude / Codex / Grok"]
Trust note: Anyone in a fleet can dispatch work to that fleet's rovers. Pilots run with the privileges of the OS user that started the rover. Use a dedicated account or host for serious fleets. See SECURITY.md.
Copy .env.example to .env for overrides.
| Variable | Default | Who |
|---|---|---|
UFO_HUB_URL |
http://localhost:8080 |
rover, web |
UFO_HUB_DATABASE_URL |
local Docker PostgreSQL | api |
UFO_HUB_JWT_PRIVATE_KEY |
required in production | api |
UFO_HUB_JWT_ALLOW_EPHEMERAL |
set 1 for local-only |
api |
UFO_HUB_MIN_ROVER_VERSION |
current release | api |
UFO_HUB_MAX_ROVER_VERSION |
unset | api |
UFO_ROVER_FORGE_TOKEN |
unset | rover (forge ship) |
Rover version bounds use semver. Invalid bounds, or a maximum below the
effective minimum, stop the Hub at startup. Rovers wait for a reachable,
compatible Hub and recheck compatibility after reconnecting; upgrade with
ufo rover upgrade when the Hub requires a newer rover.
UFO_ROVER_FORGE_TOKEN is the default env name for a forge credential on the
rover host (GitHub PAT, GitLab token, etc.). Integrations can point at another
env name; export that name where ufo rover start runs. The Hub stores the
name only, never the secret.
Production template: .env.production.example.
Go ≥ 1.26 and Node ≥ 26 on the host; PostgreSQL still via Docker:
scripts/dev.sh db
scripts/dev.sh api
scripts/dev.sh web
scripts/dev.sh rover enroll| Symptom | Try |
|---|---|
| Web won't load | docker compose ps · docker compose logs -f web api postgres |
| API can't reach DB | scripts/dev.sh up or db; check UFO_HUB_DATABASE_URL |
| Browser calls fail after login | Set UFO_HUB_ALLOWED_ORIGINS to the web origin; secure cookies only on HTTPS |
| Rover won't enroll | --hub must be the API origin; approve in the browser |
| Online but idle | Pilot assigned? CLI on PATH? Tags match? |
| Wipe local Docker data | scripts/dev.sh down -v && scripts/dev.sh up (destructive) |
| Doc | For |
|---|---|
| Rover CLI | Install, enroll, TUI, headless |
| OpenAPI | HTTP contract |
| Security | Fleet trust and rover risk |
| Changelog | Releases |
Issues and PRs are welcome. See CONTRIBUTING.md for setup, checks, and project conventions. When release notes mention a schema reset, back up or wipe local Hub databases before upgrading.
UFO is licensed under BSD 3-Clause. Third-party license notices are listed in THIRD_PARTY_NOTICES.md.