Security & Your Code

The Nilux CLI is a thin client that runs on your computer. Reading files, applying edits, and executing commands all happen locally, on your side. The server is the "brain" that reasons about your request and decides what to do — but it never touches your files or your shell directly. It can only propose an action; your machine carries it out.

Before Nilux modifies a file, it shows you the change as a diff and waits. You can approve it, reject it, or reject with a note so it revises the approach — nothing is written to disk until you agree. When it wants to run a command, it shows you the exact command first and runs it only after you approve.

Four permission modes let you set how much it asks:

• default — asks before edits and before commands.
• accept-edits — auto-approves file edits, still asks before commands.
• plan — proposes a full plan and touches no code until you accept it.
• auto — runs without stopping to ask; best kept for well-scoped, low-risk work you are actively supervising.

Some actions are hard to undo, so they get extra protection regardless of your permission mode. Destructive commands hard-stop for explicit confirmation even in auto mode, and deletes carry an additional safeguard — so a single command can never quietly wipe your work.

To answer you, Nilux sends your code context — relevant file contents and project structure — to the model for processing. That context is held in memory for the duration of your active session and cleared when the session ends. Nilux does not permanently store your code on our servers.

Command execution and file writes never leave your machine — only the context needed to reason about your request is transmitted. For full details on what data we collect and how it is handled, see our Privacy Policy.

If you have questions about how Nilux handles your code, reach us at [email protected].