Memory

Memory stores project facts that should survive a single conversation. Use it for repository conventions, recurring deployment details, important paths, and team preferences that are useful but too specific for general documentation.

Memory versus rules

Rules tell NextOS how to behave. Memory tells NextOS what is true about the project.

Use rules for requirements such as “run bun typecheck from the changed package.” Use memory for facts such as “the public docs are served from packages/web.”

Good memory entries

• Stable facts that apply across many sessions.
• Short notes with enough context to be useful.
• Pointers to files, packages, services, or workflows.
• Decisions the team has already made.

Avoid secrets, temporary debugging notes, and instructions that should be enforced as permissions or rules.

In the desktop app

The desktop settings surface project memory beside providers, MCP servers, plugins, and permissions. Review memory when a session feels stale or when the agent keeps rediscovering the same fact.