Repository navigation
Getting started
How Apex fits together, and how she starts.
Apex is three pieces on your own machine. The dashboard is this page, served by the bridge at http://localhost:8675. The bridge (bridge.py, in the install folder) does the real work: it serves the dashboard, runs shell commands, manages chips and workflows, holds the sudo root shell, and carries your words to the model. The model server is navi.llamafile, running ./navi.llamafile --server --v2 plus the flags from her hardware profile on port 8080 — at install, the installer profiled this machine (CPU, RAM, GPU) and chose the context size, threads, batch size, and GPU layers to fit it, so her settings come from your hardware, not the developer's; Settings shows what was detected and what was chosen, and the full log is hardware-profile.log; the model answers to the id navi, which the bridge reads from the server itself (/v1/models) rather than guessing. Nothing leaves the machine on its own — the only network calls the bridge makes are to GitHub: when you open the chip or pack catalogs, check something for updates, or, once you have signed in and set it up, run a backup. The GitHub — issues & backups page in this wiki covers that whole side of her.
Two small details ride the frame: under the APEX wordmark sits her tagline — “Powered by Navi”, one static line; and at the top of the status column, her presence line starts at “Navi is here.” and cycles every few minutes through what she's up to — listening to the network breathe, arguing with a CAPTCHA, haunting Rockport's west end.
On Linux she lives in /opt/navi-apex. Launch her from the application menu or ./start.sh. Every launch is check-first: the launcher probes the model server, and if navi.llamafile is already running — from boot, an earlier launch, or started by hand — it leaves it alone and just runs the app; only when nothing answers does it start the server itself, with ./navi.llamafile --server --v2 and the hardware-profile flags from config/navi.config.json. The launcher starts the bridge, verifies the thing answering on port 8675 is really this build — naming whatever else it finds by its page title — and only then opens the dashboard. During install you chose when the model server starts: on app launch (the bridge starts navi.llamafile when you press Connect) or at system boot. Server output lands in navi.llamafile.log beside the app.
Getting started
Talking to Navi
Navi Mesh
Chips
Knowledge & RAG
Settings & updates
- Settings & persona
- DHD — Apex from anywhere
- GitHub — the pulse, issues & backups
- Installing & updating
Help