Prometheus
Documentation
A sovereign agent daemon that runs on hardware you own. These pages cover getting it installed, getting it talking, and knowing when it is lying to you.
Start here
If you have
uv and something serving a model on localhost, the whole
first run is two commands. Install, then
first run.
Get started
InstallThe three real paths, and which one you actually want.
First run
oara setup — what it probes, what it asks, what it writes.
Connect BeaconPair the desktop app to a running daemon.
Verify it worksoara doctor and how to read its eleven checks.
Using it
Run it always-onStart, stop, logs, and installing the service unit.
Memory and the wikiWhat it remembers, where it lives, how to read it.
Builtin toolsThe fifty-odd tools the agent can call. Not the CLI.
Beacon
Panel tourMission, chat, loop, run, documents.
Models tabPoint Beacon at a different backend.
Beacon for iOSApprovals, grants, and what the phone can reach.
Reference
CLI referenceEvery subcommand, generated from the parser.
ConfigurationThe config file, the env file, and which wins.
OpenAI-compatible APIPoint Open WebUI, Continue or
curl at the daemon. One turn per request.
Tokens and the open web APIWhy oara token show matters before you expose a port.
TroubleshootingSymptom, cause, fix.
What doesn't work yetStated plainly, from the same flags the landing page reads.
How these pages are written
Terminal output is real text, not screenshots — you can select it, copy it, and search it, and it does not go blurry on a retina display. Screenshots appear only where the thing being shown is genuinely a picture, which in practice means Beacon.
Anything that does not work yet is named as not working rather than left out. A gap you can see is a gap you can plan around; a gap you discover after installing is a bug report.