Memory and context

Nock can use more than one kind of context. Knowing which one you mean helps you continue work or remove the right information.

Information	What it contains	Where to manage it
Nock conversation	Messages in one conversation with Nock	The left-side Chats panel
Nock’s durable memory	Facts or preferences Nock saved for use in later conversations	Ask Nock to remember or forget a specific detail; see Agent personalization
Chat Manager notes	Project notes, chat nicknames, and lessons used to find the right coding chat	Settings → Agent → What Nock remembers or the Chat Manager’s Notes button
Coding-chat history	The coding tool’s own conversation and session	The chat’s own window or the coding tool; see Chat windows
Team messages	Messages and handoffs between people and agents	Settings → Team → Messages and the Team inbox

These stores are separate. Starting a new Nock chat does not erase memory, coding-chat history, Team messages, or background task records.

Choose when a new Nock chat starts

In Settings → Agent → Start a new chat after, choose Never (default), 1 h, 4 h, or 24 h. When the selected quiet period passes, your next request starts a fresh Nock conversation without the previous messages. The old conversation stays in the Chats panel and can be reopened. This changes Nock’s main voice-agent conversation; it does not reset durable memory, stop workers, or change coding-chat history.

Keep chats for separately controls how long a Nock chat stays in the Chats panel after its newest message: 30 days, 90 days (default), 1 year, or Forever. When a chat expires, its messages and cards are deleted from chat history. Shortening this setting can remove already-expired chats the next time Nock checks retention; deleted conversations cannot be restored. This is not the coding tools’ session retention and does not clear long-term memory. See Privacy and data.

Continue the same Nock conversation

The Chats panel shows Nock’s saved conversations. Select the one you mean before sending a follow-up. Nock can continue the engine session when it is available; if not, it may use a short recap of recent exchanges. Restate details that are essential to the task, especially the project and the result you expect.

Choose + in Chats to start a new conversation. It gives Nock a fresh conversational thread but does not cancel work shown in Tasks. To stop a worker, use its Stop task control. To remove a saved conversation, use its own delete action and confirmation.

What Chat Manager remembers

Chat Manager has notes that help it recognize project names and coding-chat nicknames. For example, you can say “Remember that shop means the storefront” or “Call the billing chat the money one.” Use Notes in Chat Manager to review its notes. If one is wrong, ask it to forget that note or correct the nickname.

Chat Manager also uses coding-chat titles, short summaries, recent lines, and project names to identify the conversation you mean. It does not need to open every chat to answer “Which chats need me?” See Chat Manager commands.

Chat Manager notes are separate from Nock’s durable memory. Keys, passwords, email addresses, and long IDs are removed from saved notes and generated summaries; folder paths are reduced to folder names. A summary is a short aid for finding a conversation, not a copy of the full transcript; the coding chat itself remains in its own history. Review notes and summaries in Settings → Agent → What Nock remembers. For Nock’s ChatGPT-plan memory, see Personalize Nock.

Start fresh without assuming deletion

Use the history controls for saved chats and the appropriate memory controls for durable facts. Deleting one Nock chat is not a receipt that related details were removed from every other store or service. If you want Nock to stop using a particular fact, ask it to forget that fact; then check the relevant history and privacy controls for any separate records.

Context used to answer a request may be sent to the AI provider selected for that feature. Locally saved history does not mean the information is never sent when you use a cloud model. Do not store passwords, tokens, or other secrets as memory.

See Chats, Privacy, and Data and history.