Memory

What Nebula remembers across sessions — and how it is edited.

Nebula, the orchestrator, is the single holder of long-term memory. It reads your workspace through its read-only tools and updates memory through one structured tool: MemoryEdit.

This page is a preview skeleton — detailed content is being expanded.

What memory is for

  • User-level facts, preferences, and decisions that should survive across sessions
  • Anything recoverable from the repository (code, history) stays in the repository — memory holds what the repo cannot tell you

How memory is written

  • Through MemoryEdit — structured writes, not shell redirection
  • Memory files are never readable from sandboxed sessions — see the Sandbox

What this page will cover

  • The layout of memory files, what gets injected into a session and when, and how entries stay small — detailed content is being expanded