CLI reference.
Most users only ever type nilux — that starts an interactive session where you talk to the agent. The rest of this page covers everything else the CLI can do.
Commands
The CLI has two top-level commands:
bash# Start an interactive session in the current directory$nilux# Manage MCP server connections$nilux mcp add|remove|list|get# Version and help$nilux --version$nilux --help
That's it. There are no subcommands for auth, config, memory, or agents — those are all handled inside the interactive session through slash commands.
nilux mcp
Manage MCP servers without starting a session:
bash# Add a stdio server$nilux mcp add -s project my-server -- npx -y @org/mcp-server# Add an HTTP/SSE server$nilux mcp add -t sse -s user my-api http://localhost:8080/mcp# Add with env vars and headers$nilux mcp add -t http -e API_KEY=xxx -H "Authorization: Bearer ..." my-server https://example.com/mcp# List all configured servers$nilux mcp list# Show server details as JSON$nilux mcp get my-server# Remove a server$nilux mcp remove -s project my-server
Flags for nilux mcp add:
-s, --scope <scope>— where to save:user(default),project, orlocal-t, --transport <type>—stdio(default),sse, orhttp-e, --env <KEY=value>— pass environment variables to the server process-H, --header <header>— HTTP headers for network transports
Slash commands
Inside an interactive session, type / followed by a command name. These control the session without leaving it.
Session
/help— show all available commands/clear— reset conversation history and start fresh/compact— summarize the conversation to free up context. Optionally pass instructions:/compact focus on the auth module/resume— pick up a previous session from history/rewind— roll back file changes to an earlier checkpoint/logout— sign out and clear auth tokens
Configuration
/model— switch between Standard and Pro/config— toggle language, thinking mode, memory/agents— assign specific models to custom agents/workflow config— configure models for workflow roles
Tools
/mcp— manage MCP server connections/skills— list available skills/paste— paste image or text from clipboard/init— generate anilux.mdfor the current project/balance— check credit balance and context usage/sync memory— sync vector memory with cloud
Custom skills
Any skill with user-invocable: true in its frontmatter becomes a slash command. Type /skill-name to invoke it. For example, a skill at ~/.nilux/skills/commit/SKILL.md becomes /commit.
Keyboard shortcuts
These work during an interactive session:
- Esc — cancel the current operation (streaming, approval, or tool execution)
- Ctrl+C — press twice within 2 seconds to exit the application
- Ctrl+B — move the current workflow or long-running bash command to background
- Ctrl+O — toggle tool output view
- Alt+V — paste image from clipboard
- ↑ / ↓ — scroll through message history or navigate the bottom bar
- ← / → — cycle between background workflows, shells, and agents in the bottom bar
Approval flow
When Nilux wants to execute a tool (edit a file, run a command), it shows a numbered menu:
bashEdit src/auth/login.ts? Proceed?1. Yes2. Yes, and don't ask again for this file3. No, let me provide different instructions4. Send feedbackEsc to cancel
Option 2 creates a persistent allow-rule in .nilux/settings.json so you won't be asked again for similar operations. Option 2 is hidden for dangerous commands.
Environment variables
NILUX_SERVER_URL— override the API server. Default:https://api.nilux.devNILUX_GIT_BASH_PATH— custom Git Bash path (Windows only)