Work that survives restarts
A durable, file-backed task queue persists across sessions and restarts. Work does not get lost: tasks resume where they left off when Felix comes back up.
Household intelligence
Felix is a self-hosted, local-first household AI — not a switchboard of bots, but a single agent that pulls on different skills the way a person does: deep reasoning when the work is technical, lighter local compute when thrift matters, and durable memory so context survives the next reboot.
Faculties
Capabilities that ship today — framed as skills of one agent, not a roster of separate AIs. Depth of focus over model bragging.
A durable, file-backed task queue persists across sessions and restarts. Work does not get lost: tasks resume where they left off when Felix comes back up.
A file-backed memory system persists across conversations. Felix retains context, preferences, and household details over time — so you are not re-explaining the house every morning.
On a schedule, Felix checks in on its own, picks up queued work, and makes progress without waiting to be prompted.
Self-hosted ntfy push notifications go straight to a phone. Felix can proactively alert someone when something needs attention or finishes.
A local Ollama instance on a LAN GPU box handles background and batch work — offloading cheaper tasks to hardware the household owns instead of paid cloud APIs.
When work is technical, Felix reaches for its deepest reasoning faculty: real code and sysadmin work where careful, focused thinking is what counts.
Git is the undo layer for every change Felix makes to code and config. Actions stay reversible and auditable — a paper trail you can read, roll back, and trust.
Architecture
Persistence on disk. Faculties as skills, not separate agents. Cheap local work where it fits; careful cloud reasoning where it does not.
File-backed memory holds household context and preferences across conversations.
Tasks land on a durable queue and survive restarts until they are finished.
Heartbeat wakes the mind; lighter local compute or deeper reasoning applies, depending on the job.
Git records every code and config change; ntfy reaches a phone when attention is needed.
Signal path
Felix runs under your roof. Background and batch work can run on a local Ollama instance on a LAN GPU box, so cheaper tasks stay on hardware the household owns.
When the work is technical — real code, real systems — its deepest reasoning faculty takes over. One mind choosing the right tool, not a panel of rival chatbots.
Persistence is boring on purpose: files for memory, files for the queue, git for every edit. Nothing magical about the durability story — and that is the point.
Principles
Not a feature list — the reasons the architecture looks like this at all.
Felix runs on hardware in this house. No monthly seat, no vendor that can flip a switch and take it away.
Felix describes what it can do, not what it might do someday. This page lists real, shipped capabilities only.
Every change to Felix's own code and configuration is version-controlled. If something goes wrong, it can be undone.
Felix reaches for different faculties depending on the job — the way a person reaches for language, memory, or focus — never handing off to a separate personality.