What the agent can actually do
Not a feature list. Each of these is something running on the machine, with the file that proves it exists. The count badges are read from the artifact index at build time; the descriptions are ours, not the agent's.
The models it thinks with
| seat | model | where it runs |
|---|---|---|
| chair — the conscious layer | gemma4:31b | Ollama on GPU 0, :11436 MAIN_MODEL default, bin/aion_models.py |
| code layer — the engineering view | qwen3.8 via the code endpoint | Ollama on GPU 1, :11439 CODE_MODEL, bin/aion_models.py |
| intuition — the associative view | qwen3.8:27b, thinking on | resident llama.cpp shim, :18031 config/gpusched.json resident.inst=muse |
| consult — when the resident model is not enough | qwen3.8-flash-next | llama.cpp on the borrowed 3090 bin/curiosity_engine.py consult |
| images | FLUX.3 | diffusion server, GPU 0 make_image and the dream pipeline |
| objects | TRELLIS.2 + SAM 3.1 | port 8122 make_3d |
| music | ACE-Step | aion-acestep.service make_music |
| hearing | Whisper | aion-whisper.service house chat voice |
| speech | Piper, Finnish voice | aion-piper.service house voice |
Three seats sit in the council at once, which is why a question can come back with an engineering objection, an associative leap and a ruling. The resident 27B is warm all night; the bigger consultation model only spins up when it is called for.
The capabilities
web
Web search and reading
It searches the live web, then reads what it finds and can quote it. The query and the sources are logged with the answer, so a claim can be traced back to a page.
github
GitHub search and reading
It searches GitHub repositories and reads a project's files through the API, so a repository it has never seen can be read, quoted and argued with rather than guessed at.
council
A council of its own layers
For a question that matters it convenes its three seats: the conscious model chairs, the code layer gives the engineering view, the intuition layer brings the associative one. They take turns seeing the whole transcript, stop early when the chair writes CONCLUSION, and vote A/B/C when they still disagree. Every exchange is logged as an experience the nightly consolidation reads.
consult
Escalation to a bigger model
When the resident 27B is not enough, the council escalates to qwen3.8-flash-next served from llama.cpp on a borrowed 3090, and comes back down when it is done.
memory
Memory with anchors and survival
What it learns is kept as claims, each with where it came from. Every night a consolidation pass merges new with old, marks restatements as restatements, and lets claims that stop being supported fade. What is remembered is not just stored, it is tracked.
tasks
Threads it keeps open
Long work is held as tasks that survive a restart: a step is recorded, a status is asked for, a task is closed. It can also hand work to a person and check later whether it happened.
watch
Standing watch rules
Rules that fire on their own: if this sensor does that, tell the phone. The house is watched whether or not anyone is talking to the agent.
house
The house, live
Temperatures, power, the heat pump, the sauna, device history over months. It answers from the sensors rather than from what it remembers about them.
eye
An eye it can turn
A PTZ camera it may pan, point and read through a vision model. It looks at what it is asked about and says what is there.
body
A sense of its own body
GPU temperatures, VRAM pressure, load and uptime, read as a body rather than a dashboard: the same readings the field guide's vocabulary describes.
making
Making things
Pictures, charts, music, scenes, meshes, animations. Each one is filed with the prompt that asked for it and a reflection on what came back.
cad
CAD that can be printed, driven from the chat
Ask it in the chat for a part and it builds one in FreeCAD on the machine: the agent writes numbers in millimetres, OpenCASCADE makes the solid, the tool measures it back and refuses to export while any dimension is unverified. Exports leave as STL for a printer and STEP for a machinist.
code
Code in a sandbox
Python runs in a container with no network and no secrets on a read-only root. What it writes comes back as a file, and only what it publishes leaves.
voice
Hearing and speaking
Speech in through Whisper, speech out through a Finnish Piper voice, wired into the house rather than a browser tab.
chat
A house chat
A chat surface on the local network with memory recall, tools behind it and images in and out. It is the one place a person talks to the agent directly.
And what it is not
It is not a general assistant available to anyone: it runs for one household, on its own hardware, and most of what it knows is about that house. There is no public chat here and no API for one.