An AI engineer that lives in your terminal
Nilux reads, writes, runs, and remembers — across sessions and across agents. Built for developers who never leave the command line.
Built like a Unix tool, not a chatbot.
One binary, four ideas. Composable with everything you already use — pipe it, script it, automate it, forget it's there.
It remembers your project. So you don't have to re-explain it.
A local-first context store that survives reboots, branches, and entire sprints. Pin facts, attach decisions, scope per-repo.
Spawn agents. Watch them work.
Hand off a task and keep coding. They report back when they're done.
Read. Edit. Search. Run.
Every tool you'd give a junior engineer, already wired up. No plugin marketplace.
Plug in everything else.
First-class MCP support — connect GitHub, Linear, Postgres, your internal services. Discovered tools become available to every agent automatically.
Three commands. Then it's just you and your terminal.
No GUI. No web dashboard. No “open in browser to continue.” Auth happens in your shell, configuration is a single JSON file, and everything streams back as text.
Pay for what you ran. That’s it.
No seats, no plans, no minimums. Top up $10 and use it for as long as it lasts.
Per-token pricing.
Same model. Same context. Same tools. You see exactly what every prompt cost — to the thousandth of a cent.
What developers say after a week.
Feedback from developers who made Nilux part of their daily terminal workflow.
Your terminal already knows what to do. Now it has help.
Works from any directory. Remembers your project between sessions.
Your code stays under your control
How Nilux handles your code — and keeps you in charge of every change.
File reads, edits, and command execution all happen locally. The server decides what to do; your machine does it.
Every edit is shown as a diff you approve or reject, and every command is shown before it runs. Four permission modes let you set how much it asks.
Destructive commands hard-stop for confirmation even in auto mode, and deletes carry extra protection.
It's sent to the model to process your request, held in memory for the session, cleared when it ends, and never permanently stored on our servers.