A deterministic execution layer for AI-driven development.
Felix isn't just an AI helper - it's the control plane that makes AI development governable.
Five pieces. One coherent system.
Most AI coding tools are single-agent chatbots. Felix is a delivery system — each component solves a specific problem that the others depend on.
Powerful CLI
One command runs a complete requirement end-to-end. Planning, building, validation, and commit — all enforced without human intervention.
Bring Your Own Agent
Felix works with any LLM — Claude, GPT-4, Gemini, Grok, local models. Swap providers per project without changing how your delivery works.
Local Code. Always.
Your source code never leaves your machine. Felix runs inside your environment. The sync layer shares plans and status — never your repo.
Artifact-Based State
Progress lives in files, not chat history. Plans, patches, and validation reports are committed to your repo — inspectable, diffable, and auditable.
Optional Cloud Scale
Run a single agent locally or coordinate a swarm across machines. Team visibility, run history, and orchestration — without ever touching your code.
Core Platform Pillars
Built from the ground up to solve the hardest problems in autonomous software delivery.
Plan-Driven Execution
Planning and building are explicit modes. You cannot drift between them or bypass the workflow.
Backpressure Gates
Tests, builds, and linters are mandatory. Failures block forward progress.
Artifact-Based State
Plans, patches, and reports are stored as durable files for audit and reuse.
Autonomous by Default
Agents execute to completion with explicit outcomes instead of open-ended chat.
Collaboration Without Code Exposure
Share intent, plans, and artifacts while keeping source code inside your environment.
Governed Autonomy
Clear exit codes, explicit failure states, and recoverable runs keep execution controllable.
Built for engineers who need to trust their tools.
No magic. No black boxes. Felix runs on your machine, writes to your repo, and leaves a record of everything it did.
Your code stays local
Felix runs inside your environment. No source code is sent to external servers. The sync layer shares plans and status—never your repo.
Every decision is on record
Specs, plans, patches, test results, and validation reports are written as files in your repo. You can diff, revert, or audit any run.
You stay in control
Felix proposes. You review. Validation gates block bad changes before they land. Set your own pass criteria—Felix can't override them.