Memory and context

Understand how Nucleus uses project context, what persists across a session, and the limits of its memory.

Nucleus is context-aware but not persistent between sessions. Understanding what it remembers, and what it does not, helps you work with it more effectively.

How Nucleus builds context

Every time you open Nucleus in a project, it loads the current state of that project: interview responses, scores, notes, and metadata. This is called the project context window. Nucleus uses this snapshot to answer questions and make suggestions.

The context window is built fresh each time you open a project or reload the page. Nucleus does not carry memory from a previous session.

What persists within a session

During a single session (while the project tab stays open), Nucleus remembers:

• The conversation thread, your previous questions and its responses within that session, so you can ask follow-up questions without repeating yourself.
• The project context snapshot, the data loaded when you opened the project.

If new data is added to the project while Nucleus is open (for example, a team member adds interview notes), Nucleus will not automatically pick up those changes. Reload the project to refresh the context window with the latest data.

What does not persist

Item	Persists?
Conversation thread from a previous session	No, resets on reload
Custom instructions or preferences	No
Edits suggested by Nucleus	No, you must apply them manually
Context from other projects	No

Context limits

Nucleus can only process a finite amount of project data at once. For very large projects with many interviews and extensive notes, Nucleus may prioritize the most recently updated content when constructing its context window.

If you notice answers that seem to miss older data, try asking a more targeted question that names the specific interview, section, or dimension you are asking about.

Multi-user projects (Team and Enterprise)

On Team and Enterprise plans, multiple team members can work in the same project simultaneously. Each person’s Nucleus session is independent, one person’s conversation thread is not visible to another. All team members share the same underlying project data, however, so answers reflect the combined state of the project for everyone.

Limitations summary

• No memory between sessions; context resets on reload.
• Does not auto-update when project data changes mid-session.
• Cannot access other projects or organization-wide data.
• Very large projects may result in partial context coverage.

Next steps

• What is Nucleus, a refresher on what Nucleus can do.
• Ask Nucleus questions, tips for phrasing effective prompts.