Sessions and context.

Every conversation with Nilux is saved, so you can come back to it later. Conversations you have not opened for 30 days are deleted. This page covers continuing, undoing and keeping long conversations healthy.

Continue an earlier conversation

Type /resume to see the conversations in this project, newest first. Pick one with the arrow keys and Enter, or press / to search them. Nilux picks up exactly where you left off.

Each conversation gets a short name after the first reply, so they are easy to tell apart. You can turn this off in /config (Session Names).

Undo: go back to an earlier message

Made a wrong turn? Press Esc twice on an empty prompt, or type /rewind. Choose the message you want to go back to, then what to restore:

• Restore code and conversation: the files go back to how they were at that message, and the conversation continues from there.
• Restore conversation: only the conversation goes back; your files stay as they are now.
• Restore code: only the files go back.

The message you went back to reappears at the prompt, so you can change it and send it again. Rewind undoes changes Nilux made with its own editing tools. It does not undo changes made by commands it ran, or edits you made yourself. The exception: files deleted in Auto mode, which Nilux copied first, come back.

Start fresh

/clear starts a new, empty conversation. The old one is still in /resume.

Long conversations

Everything said in a conversation, plus the files Nilux has read, makes up its context: what the model sees each time it answers. The context has a maximum size, and the bigger it grows, the more each reply costs.

• /context shows what fills it: your instructions, tools, the messages, and how much room is left.
• /compact replaces the conversation so far with a short summary and keeps going. You can say what matters most: /compact keep the details about the payment API.
• Auto-Compact (on by default, in /config) does this by itself when the context is full, so long tasks are not interrupted. Turned off, Nilux stops when the context is full and asks you to run /compact or /clear.
• Context Limit in /config sets a smaller maximum, if you want to keep conversations cheaper.

The status line

The right side of the bottom line shows:

• the model you are using;
• how full the context is, as a percentage;
• how much this conversation has cost so far;
• peak 2x during peak hours, when usage costs more (see Billing).

The left side shows your git branch and how many files have changed.

In a long conversation you may also see cache expires in N min. Nilux keeps a recent conversation ready, which makes the next reply cheaper. After a while without messages that copy is dropped, and the next reply has to read the whole conversation again at the full price. The status line shows roughly what that would cost, so you can decide whether to continue or start fresh with /clear.