Niluxv1.0.33
/desktop

The app and the terminal.

The app and Nilux in the terminal are two ways into the same Nilux. Both read and write the same files, in the .nilux folder of your home folder and of each project, so you can use either one, or both.

What they share

  • Sessions. Sessions you start in the terminal are in the app's sidebar, and appear there while the app is open, without a restart. Sessions from the app are in the terminal's /resume. The app's search covers both.
  • Your sign-in. It is kept in ~/.nilux/config.json. If you are signed in in the terminal, the app opens signed in; logging out in the app removes the sign-in for the terminal too.
  • Settings. Most of them; Settings says which.
  • Trusted folders. A folder you trusted in one is not asked about again in the other.
  • Each project's own settings: isolation, the folders outside the project, and the rules saved with Always allow.
  • Instructions, agents, skills, hooks, MCP servers and project memory: the same files.

Continue a session in the other

To pick up a session from the app in the terminal, start Nilux in the project's folder and choose the session in /resume:

bash
$cd ~/projects/my-app
$nilux
❯/resume

To go the other way, open the project in the app: the session is in its list.

Keep each conversation in one place at a time. When Nilux is open in a terminal in a project, the app says A terminal is working here above that project's sessions.

Deleting

Deleting a session in the app deletes it from ~/.nilux, so the terminal no longer has it either. Sessions nobody has used for 30 days are deleted; a session you pinned in the app is kept, also when the terminal does this cleaning.

Commands that work differently in the app

  • /help opens the list of keyboard shortcuts.
  • /balance opens the account menu, with your balance.
  • /config opens Settings, and /resume the search.
  • /trust is not in the app: use Settings → Trusted folders.
  • /paste is not needed: paste into the message box with Command+V.

What still needs the terminal or a file

  • Adding an MCP server: nilux mcp add, or its configuration file. See MCP servers.
  • Writing hooks and skills, and your nilux.md: they are files. See Hooks, Skills and Project instructions. In the app, /init writes a first nilux.md for you.
← Previous · SettingsNext · Changes, files and preview →