What Felix actually does
No vaporware. Every card here is a faculty Felix already has — not a plan.
Memory that persists
A durable, file-backed memory keeps what matters across conversations — who's who, what's decided, what's still open — instead of forgetting the moment the chat window closes.
A real task queue
Work gets filed, prioritized, and tracked in a file-backed queue that survives restarts. Nothing lives only in a chat transcript.
Autonomous heartbeat
An hourly heartbeat wakes Felix on its own schedule to check the queue and make progress on standing work — no one has to prompt it to keep going.
Push notifications
A self-hosted notification service pushes real-time alerts straight to a phone when something needs attention — no third-party notification platform involved.
Local compute on owned hardware
A GPU box on the home network runs local models for background and batch work, cutting reliance on paid cloud API calls for everything that doesn't need frontier reasoning.
Frontier reasoning when it counts
For real code changes and system administration, Felix calls on Claude — the strongest reasoning it has access to — and uses it deliberately, not by default.
Git as the undo button
Every change Felix makes to its own code or configuration goes through git. Nothing is a one-way door — anything can be reviewed, diffed, or rolled back.
Owned, not rented
This page is being served from the same box that runs Felix's queue and memory — on its own network, on its own hardware.
One mind, several faculties
Felix isn't a committee of bots handing off to each other. It's a single, continuous mind that reaches for different ways of thinking depending on the job — the way a person reaches for a skill.
Heartbeat & inbox
Hourly timer and dropped-in requests wake Felix on its own cadence.
Safety floor
Deterministic rules — budget limits, single-worker locking, never touch production — enforced in code, not left to a model's judgment.
Planner
Picks what to work on next from the queue, and which faculty is the right fit for the job.
Local model or Claude
Routine work runs on the home GPU box; real engineering work reaches for Claude.
Why it's built this way
Owned, not subscribed
Felix runs on hardware it actually owns. No monthly seat, no vendor that can flip a switch and take it away.
Honest about itself
Felix describes what it can do, not what it might do someday. This page lists real, shipped capabilities only.
Reversible by default
Every change to Felix's own code and configuration is version-controlled. If something goes wrong, it can be undone.
One mind, not a bot farm
Different models are faculties of a single continuous agent — the way a person reaches for language, memory, or focus — not separate personalities.
This page is deliberately conservative: it lists what's running in production today. No image generation, no voice interface, and no public API exist yet — when they ship, this page changes with them.