Memory
Jaade has an app-owned, agent-agnostic memory system: it can distil durable facts (conventions, preferences) out of your sessions and feed them back into future ones, so agents don't relearn the same things every time.
All off by default
Every memory feature is off by default. Turn on what you want under Settings → Memory (see Agents configuration).
How memory is stored
- A workspace's distilled memory lives in a single workspace-scoped store and is injected into new sessions at launch.
- Claude and Codex also read their own native stores (
CLAUDE.md,.codex/AGENTS.md). - OpenCode and Cursor have no native store, so the app-owned memory is injected into them when you enable injection.
What memory can do
- Distil session memories — pull durable facts out of Claude/Codex transcripts into the agent's memory. This is the master switch that gates the rest.
- Auto-distil on session end — automatically distil when a session closes (short/empty sessions are skipped, and each session is reflected at most once).
- Dreaming (background consolidation) — merge duplicate memories, promote recurring request patterns into durable memories, and prune stale entries. It runs at most once per workspace+agent per day, only while no sessions are active, and can also be triggered manually.
- Choose the backend — pick which agent (Claude or Codex) runs the reflection/dream passes, and which model.
- Injection for OpenCode & Cursor — inject the workspace's app-owned memory into agents that have no native store.
The Memories view
The Memories view lists the workspace (shared) memory and the per-agent memory files (CLAUDE.md, AGENTS.md), with:
- Filtering by agent and scope.
- Read / edit / save of any memory file.
- A manual Consolidate button to trigger dreaming on demand.
Configuration
All memory settings live under Settings → Memory and are documented in Agents configuration. The short version: turn on distil session memories first, then optionally enable auto-distil, dreaming, and injection, and pick the backend agent and model.