Capabilities (light.aius.co/capabilities) lists everything Aius can use, exactly as each computer’s TUI reports it. It sits in the rail beside Connections, with a count for each part. Nothing lives on the platform: the page is the collection your computers report, sanitised, and a computer that runs an older TUI simply reports less — the page says so. Signed out, the same address shows the public catalogue — every connector AIUS knows, the full model list and the command inventory — with no account data. Signed in, it shows your own collection on top of that catalogue.
Capabilities — the All view: one tile per part of the collection, in the rail's order
The rail lists each part under Capabilities with a right-aligned count, in the same order the All view’s tiles use — Computers, Connect, Models, Commands, Skills, Agents, Tools, Interfaces — and every count on the page (rail, tab and tile) comes from one source, so they can never disagree.

What is in it

  • Computers — every machine that reports in: its folders, system, version, online state and how many connections it serves, plus the same set-up steps the empty Projects state shows, so a server or VM joins the same way.
  • Connect — your configured connections as tiles (logo, status, computer, tool count, each linking to its page and tool tree), above a catalogue of services AIUS knows but no computer has yet. Each card explains what the connector is for, how sign-in works, and has a Connect button that opens a conversation in the AIUS Launcher project with the request already typed. Credentials stay on the computer; AIUS Light only ever receives the connection’s name, status and tool list.
Connect — your configured connections above the catalogue of services AIUS can reach
  • Models — the same renderer and data as Prices: every chat and media model, the same search, category, price, lab and provider filters, with a mark on the models your computer’s TUI reports.
Models — the same table and filters as Prices
  • Commands — the full TUI and Light command inventory, ordered by how work starts: the most used first, then grouped by what each command works on — with aliases, a one-line description, and whether it also runs in Light.
Commands — the full inventory, most used first
  • Skills — the skills installed on your computers, plus the trusted public libraries Aius can pick from (anthropics/skills, obra/superpowers and the team’s own). The skill-explorer skill lists a trusted repository’s skills, shows each SKILL.md for your review, and installs the one you pick into .agents/skills/.
  • Agents and Tools — the agents your terminals report and the full tool inventory, grouped by where each tool spends its work.
A connection’s own page (for example light.aius.co/connections/clickup) lists where it runs, how it signs in and which computers serve it — then ends with What it gives Aius: the tools it offers, in a tree you can search (when there are more than ten) and collapse or expand at once. Each tool folds out prompts you can send.
A connection's page — status, sign-in, and the computers serving it
What it gives Aius — a searchable, collapsible tool tree with launchable prompts
  • Interfaces — the surfaces live today (the TUI, AIUS Light, dictation) and the always-on gateways that are designed but not built yet (WhatsApp, Telegram, Slack, Discord, Signal, iMessage), each marked clearly.

Try it — ask Aius

Every item carries example prompts behind a small Try it — ask Aius toggle. Clicking a prompt opens the AIUS Launcher project with that prompt ready to send — for example “make Claude Fable 5.2 my default model”, “connect Slack”, or “summarize what I missed in #team overnight”.
Tools — the full inventory, each with prompts that open the AIUS Launcher
The examples describe what the capability is for, so a prompt you pick is one Aius can actually act on.