Memory and context

Nock can use several kinds of context. They help with continuity, but they are not interchangeable and none guarantees perfect recall.

Three things to distinguish

Kind	Purpose	What a new chat does
Current conversation	The exchanges used to answer your next question.	Starts a fresh conversation.
Saved chat history	The conversations you can reopen from the Chats panel.	Leaves older saved chats available according to retention.
Durable memory	Facts or preferences the agent saved and can retrieve later.	Does not automatically erase them.

Settings → Agent → About you supplies your name as another source of context. Review it separately from chats if you want to change how Nock addresses you.

Continue a conversation

Select the intended chat from the side panel before asking a follow-up. The main engine can resume a stored conversation when it is still available. Otherwise, recent exchanges may be used to reconstruct context rather than replaying the entire history.

For an important task, restate the target, constraints, and desired outcome. “Do the same thing as last time” is less reliable than naming the project or artifact and explaining what should stay the same.

Start fresh without losing work

Use + in Chats or the new-chat command. This is useful when changing subjects, separating projects, or recovering from a confused conversation. It does not cancel every background worker; use the task’s stop control for that.

If you want automatic separation after inactivity, check Settings → Agent → Start a new chat after. The candidate offers Never and several idle durations. This is a conversation preference, not a retention or privacy control.

Correct a remembered fact

State the correction clearly and ask the agent to forget the specific old fact when appropriate. Check its response and behavior. Do not treat a verbal acknowledgment as a universal deletion receipt covering saved chats, coding-agent sessions, provider records, and backups.

Use the appropriate history and retention controls for saved conversations. For a wider data-removal request, consult Data and history and Support. Deleting application files or changing internal identifiers is not a supported substitute for understanding what each store contains.

Limits and privacy

Memory behavior depends on the active engine. A fallback may retain less context or lose it on restart. Background task summaries can also be shorter than their full results; open the task when exact details matter.

Context retrieved for an answer becomes part of the model request. Locally stored history does not imply that none of its contents can be sent to a cloud model during use. Avoid storing secrets as conversational preferences.

See Chats, Agent personalization, and Privacy.