Bird turns this VPS into the place where every repo change gets planned, verified, remembered, and replayed.

The first objective is local stability: authenticated access, command-center UI, health checks, and the service backbone. Once that is solid, Bird connects outward to the rest of your VPS fleet.

Open Bird Health endpoint

Current state

Bootstrapping

Next milestone

Memory stack

Why this order

A working local control room gives you authentication, UI, service health, and a stable place to attach memory and audit. WireGuard and remote repo orchestration come immediately after.

Orchestrate

One request fans out into repo-specific work, validation, and follow-up coordination.

Remember

Bird keeps system dossiers, run memory, contracts, and repo context within reach.

Audit

Diffs, logs, command output, and verification traces stay attached to each run.