The dashboard
aios serve opens the web dashboard at http://127.0.0.1:8017 — loopback-only by default (no network
exposure, no login). It is a faithful surface over the same engine as the CLI; nothing here needs the
Internet. The 🏠 ApocOS brand top-left is the Home link and returns you to the Map.
Map (Home)
The default view. The map is drawn from your own offline OpenStreetMap data — there is no tile server.
- Pan/zoom — drag to pan, wheel to zoom. A small centre crosshair marks the exact point that Set Home will adopt. The bottom-left readout shows the centre coordinates and feature counts.
- Go to place — jump to a place name or
lat,lon. Below it: Go Home (recentre on your saved location), Set Home, and Clear Home (forget it). Set Home offers a choice of source — From map centre or From GPS location (enabled only when a receiver has an actual fix) — and reports the result. Plus the current-location marker toggle and Follow GPS (a live moving position, when a receiver is present). - POI layers — tick the point-of-interest layers to show (grouped; survival essentials are on by default). Only ticked layers are drawn, each in full. See POI kinds.
- Nearest — the nearest features of a kind (or all within a radius in km), measured from the map centre by default (so it works with no location set — pan to where you care and search), or switch the from toggle to home / GPS to measure from your saved location.
- Route — turn-by-turn directions; blank “From” means your current location; tick Walking? for footpaths.
- Survey — the three terrain tools: Sightlines (what you can see), Best site (where to camp or settle), Signal (comms masts you can reach). They measure from whichever anchor the measure from control is set to — the same control Find Nearest uses — and every result says which one it used. With no location set, home / GPS is greyed out and everything measures from the map centre until you Set Home. Each of the three always runs when clicked, so you can move the map or change the anchor and click once to re-measure. While a tool’s result is on the map, a small ✕ appears beside its button to remove just that layer; the same layer also appears as a named chip in the Showing: strip under the map, which is where every other overlay (routes, traces, cascades, results) is cleared from.
Click any drawn feature to inspect it. Every feature gets the same card — what it is, where it is, your field marks, directions — and a power line, substation or water works adds buttons for its network analyses (Trace this network, What loses power, Full cascade, What loses water).
Whatever the map is currently showing — results, a route, sightlines, signals, a trace or a cascade — is listed in a Showing: strip above the panel, each with a ✕ to remove just that one. ✕ Clear all removes everything at once — the cards and whatever the map is showing. Removing a layer also retires the card that describes it, while dismissing a single card leaves the map alone, so you can tidy the panel without losing what you are looking at.
Library and Assistant
Two ways to ask, split by intent (ADR-0046) — both streamed live, both offline. The Library tab
(aios ask) is retrieval-first: type a query, it searches the offline corpora and answers grounded in
the passages it found, with the source shown prominently beneath (and Open full article ↗ where an
illustrated copy exists); if nothing matches it labels the answer unverified. The Assistant tab
(aios chat) is model-first: conversation, reasoning, and the map/system tools, with a deterministic
breakdown of how it got there — read-only by default, tick actions to let it run commands and write
files (like aios do), and open 📚 source passages under an answer to read the corpus text it drew on.
See Library & Assistant. (Add/manage corpora in Settings → Knowledge corpora.)
Settings
Machine awareness and admin: hardware cards (CPU/RAM/GPU/disk), installed models (with sizes and remove), regions and their elevation coverage, knowledge corpora, and the Data panel (where your data store resolves, and disk management). Admin actions are enabled only on a loopback server.
Chat model. A Chat model dropdown lets you pick which installed model chat/ask use, taking effect
immediately — pick a specific one, or Auto to follow the model the hardware recommends. (Same as
aios model use <name|auto>.) Switching is instant and needs no download, so it works in every mode.
Running live in RAM (ephemeral). If you’re on a live USB with no data drive, a banner explains that changes here won’t survive a reboot — so the actions that add or update data (fetch a region, add a ZIM, pull a model, update corpora) are disabled, since they’d be lost on reboot and a large model pull can exhaust memory. Browsing/searching the catalogues and switching between installed models still work. To keep changes, set up a data drive (Data panel) or install to disk.
Restart / shut down. On an appliance (a live-USB boot or an installed system) a Power section
near the top of Settings has Restart and Shut down buttons — a fullscreen kiosk has no other clean
way to power off. They ask for confirmation (and warn, on a live-in-RAM boot, that the session is lost).
They are not shown on a developer machine running aios serve, so the dashboard never reboots your
workstation.
Each item shows two clocks where they differ: when you ingested it and the data’s own vintage —
a region’s OSM snapshot date (with a ⚠ when it’s stale, hinting aios geo update), a corpus’s ZIM
snapshot, a model’s pull date. So you can tell a fresh install from a two-year-old offline snapshot.
Graph
A visual browser for the Entity Graph — a type overview, drill into a type, and inspect an entity’s
properties and relationships by clicking. The terminal equivalent is aios graph (see Exploring the
graph).
Terminal
On an appliance (a live-USB boot or an installed system) the nav bar shows a Terminal tab — a full
command-line terminal in the browser, so you can reach the CLI (aios doctor, aios geo …, nano, sudo
recovery, and the rest) without a separate keyboard app. This is what makes a touch-only, keyboard-less
box usable: with the on-screen keyboard (Touch mode) you can type into it like any other terminal.
The shell runs as the ordinary aios user — everyday commands just work, and anything that needs root
prompts for the account password through sudo, exactly as at a real console. If the session ends (you
type exit, or the connection drops) press Reconnect for a fresh shell.
For safety the terminal is available only on an appliance and only over the local loopback connection —
it is never exposed when the dashboard is bound to a network address, and it does not appear on a developer
machine running aios serve (set AIOS_TERMINAL=1 to opt in there). It grants no privilege the machine’s
own console wouldn’t: on a kiosk you already have physical access to a login prompt.
Touch mode
For a keyboard-less, touchscreen box, Settings → Display & touch has a Touch mode switch:
- Auto (default) — turns on automatically when the device is touch-capable and this is an appliance (a sold/kiosk unit); a developer machine with a mouse is unaffected.
- On / Off — force it either way.
Touch mode turns on three things: an on-screen keyboard (UK QWERTY by default, layout switchable to
US, no number pad; it pops up when you tap a text box or the ⌨ button, and it also types into the
Terminal), larger tap targets across the dashboard, and map touch gestures — pinch to zoom,
drag one finger to pan, tap a point to inspect it. The owner can preset it before shipping a unit with
aios ui touch on (and aios ui layout uk|us).
If you turn Touch mode off on a touchscreen unit, the dashboard asks you to confirm and reminds you that you can turn it back on here by tapping — no keyboard needed — so a keyboard-less box can’t get stuck.
Help
This manual — rendered offline from Markdown. Use the search box to filter pages; the active page expands its headings as a table of contents.