Reference
What doesn't work yet
Stated plainly, and read from the same flags the landing page reads — so this page cannot quietly claim something the front door contradicts.
Generated
Produced by
gen-limits.py from the RELEASE declaration in the landing page. Flip a flag there and regenerate; there is no second list to remember. A flag this generator has not been taught about aborts the build rather than disappearing from the page.
As of v0.9.5, 2 things are not what you might reasonably assume:
Desktop builds are unsigned
Beacon is not signed or notarised. Your OS will warn you, and it is right to.
Training on captured traces is not built
Trace capture works and oara export-traces writes them out. The loop that trains on them does not exist yet.
What does work
Stated with equal plainness, because a page of gaps with no counterweight is its own kind of dishonesty:
- Installing from git with
uvorpipx— one command, no system libraries, no compiler. See Install. - Installing from PyPI:
pip install oara-prometheusruns the daemon and pairs with Beacon; add[full]for Slack, Discord, MCP, the browser tool, the Anthropic provider and voice output. - Homebrew on Apple Silicon Macs (M1 and later):
brew install oaralabs/tap/oara, the full name — a barebrew install oarafails because the tap isn’t trusted. Intel Macs are not verified yet. It installs in a few minutes. Like a plain pip install, it runs the daemon and pairs with Beacon. - The daemon, the chat loop, tool calling, memory, the wiki, and the REST/WebSocket API Beacon talks to.
- Coding mode, sandboxed, opt-in. Telegram, Slack and Discord gateways.
- Running Beacon from source against a real daemon, which is how it is developed.
If something here is out of date, the flags in the landing page are the thing to fix — this page follows them.