Changes, files and preview.

Beside a session's conversation the app shows one panel at a time. The buttons at the right of the session's bar open them: the branch chip (what changed), Agents, Panel, the folder (the project's files), the terminal and the session details. The chips show only when they have something to open. A chat has none of them: it has no folder.

Drag the line between the conversation and the preview or the terminal to share the width. Where the pane is too narrow, a panel lies over the conversation; click the dimmed conversation to put it away.

Preview

When Nilux makes a page for you to look at, an HTML file it keeps in the project's .nilux/artifacts folder, the page appears as a card in the conversation, and the first one in a turn opens beside it by itself. Any other HTML page Nilux writes or edits in the project gets a Preview button on its line.

• The page is updated in place each time the file changes, at the same scroll position, and the bar says when it changed.
• Page width: Desktop (the panel's whole width), Tablet (768 px) or Phone (390 px).
• Show the code shows the page's source. Open in your browser opens the file with your Mac's default app for web pages.

The preview runs the page in a sandbox. It can use its own files and libraries from well-known public CDNs; other addresses on the network are blocked, and links out of the page do not open in the preview. Like everything in the project's .nilux folder, these pages are kept out of git.

Panel in the session's bar brings the panel back after you closed it.

Files

The folder button (The project's files) opens the Files tab: the project's folders and files. Pick a file to see it. A file that is not text, or is too big, is not shown here; open it in your editor instead.

Changes

The branch chip in the session's bar shows the git branch and how many files changed; it opens the Changes tab. The tab lists:

• Merge conflicts, while a merge, rebase, cherry-pick or revert is under way.
• Staged and Changes: each file with its state, and buttons to Stage, Unstage or Discard the changes. Stage all, Unstage all and Discard all act on a whole section. Click a file to see its diff.
• History: the commits, with a mark on those not pushed yet. Click one to see what it changed.

Commit

Write a message in the box and press Commit, or Command+Enter. The arrow beside it offers Commit and push and, while the last commit has not been pushed, Amend the last commit. Ask Nilux to commit asks this session to write the message and commit.

Branches and syncing

• The branch name at the top of the tab opens the list of branches, yours and those On the remote, and Create a branch….
• The button beside it sends and brings commits: Push, Pull, Sync (bring in, then send) or Publish (put a new branch on the remote). Up to date means there is nothing to do.
• More (…): Pull, Fetch, Stash the changes, Bring back the stash, Ask Nilux to review (the staged changes, before you commit) and Open in the terminal.

Discarding

Discarding asks first. What is not staged goes back to the last staged or committed version, and a file git does not track yet is deleted. The app keeps a copy, so Undo brings it back while the app is open; when there is too much to keep a copy of, the question says so before you discard.

Merge conflicts

When git stops on a conflict, the files in conflict are listed first. Open one to settle each place with Keep yours, Keep theirs or Keep both, then Mark as resolved; or press Ask Nilux to resolve. Once all are resolved, commit (or continue the rebase) to finish. Abort puts the files back as they were before it began.

No git yet

In a folder that is not a git repository, the tab offers Initialize a repository. On a Mac, git comes with Apple's Command Line Tools: if the tab says git is not installed, run this in Terminal, then press Refresh:

Terminal

The terminal button opens terminals beside the session, in the project's folder, with your own login shell. New terminal adds one, each in its own tab. Maximize gives the terminal the whole pane, Restore gives the conversation back. To open a link printed in a terminal, Command-click it.

A shell code block in a finished answer (bash, zsh and the like) has Run in terminal: it runs in a terminal of its own and its output shows under the block; Show in the terminal panel opens that terminal. A session's terminals close with it.

Session details

The last button in the session's bar (Show session details) opens cards about the session:

• Environment: the project folder (click it for its files, or copy its path), the branch and how many files changed, and Open in the terminal.
• Context: how full the context window is and what fills it, with Compact.
• MCP: the session's MCP servers and how many are connected.
• Tasks, Agents and Background tasks: the task list, the helper agents and the work running in the background.
• Outputs: the files the session wrote or edited. A page opens in the preview, any other file in Files.
• Servers: servers that a command started, such as a development server, each with a button to open its address in your browser.

The menu at the top (Arrange the session details) chooses which cards show, and dragging a card by its grip moves it.