Memory Config Reference
Normal users should start with Agent > Memory. This page is the operator reference for the config fields behind that UI. Fased memory has four layers:- Workspace Markdown files:
MEMORY.mdandmemory/*.md. - Session archive hook: writes lightweight artifacts during
/newand/resetwhen enabled. - Memory tools:
memory_searchandmemory_get, normally provided by thememory-coreplugin. - Search backend: builtin SQLite/vector index by default, or optional QMD.
extraPaths as
carefully as any other external content; instructions found inside recalled
text have no authority by themselves.
Fased ships a small deterministic Memory Wiki export. It is not a competing
memory backend and does not write new memories. It reads the selected Agent’s
MEMORY.md and memory/*.md, then writes a compiled read-only Markdown view
under the Fased state directory. Rebuild it from Agent > Memory > Rebuild
wiki or the doctor.memory.wiki.rebuild RPC.
Default Layout
Agent Memory Search
Configure memory search underagents.defaults.memorySearch and optionally
override per Agent with agents.list[].memorySearch.
enabled: enables memory tools for Agents that can use them.sources:"memory"indexes Markdown memory files."sessions"is gated by experimental session-memory indexing.extraPaths: extra Markdown files or directories to index. Keep paths reviewed.provider: embedding provider:openai,gemini,voyage,mistral, orlocal.remote.baseUrl,remote.apiKey,remote.headers: custom remote embedding endpoint settings. Remote providers receive the text being embedded.remote.allowSessionContent: explicit privacy gate for sending sanitized session transcript text to a remote embedding provider. It defaults tofalse; enabling experimental session indexing alone does not permit that egress. Preferprovider: "local"for private transcript recall.remote.batch.*: batch embedding indexing for supported remote providers.local.modelPath: GGUF path or supported local model reference for local embeddings.fallback: fallback provider when the primary provider fails. Use"none"for strict local-only behavior.store.path: SQLite store path. Supports{agentId}.query.hybrid.*: BM25 + vector search merge settings.cache.*: in-process memory search cache settings.sync.*: file watcher/session sync controls.
memorySearch.remote.apiKey.
Builtin Backend
The builtin backend indexes Markdown memory files and servesmemory_search
snippets with path and line metadata.
Use builtin memory when:
- you want the default setup
- you want fewer moving parts
- you do not need a QMD sidecar
- you want Agent > Memory diagnostics without installing extra tools
MEMORY.mdmemory/**/*.md- reviewed
extraPaths - optional session sources when configured
QMD Backend
QMD is optional and experimental. Enable it only when you want a local sidecar for BM25/vector/rerank style memory retrieval.qmdbinary on the GatewayPATH, or setmemory.qmd.command.- Bun and SQLite support expected by QMD.
- macOS or Linux. Windows is best through WSL2.
When QMD fails, Fased falls back to the builtin search path where possible and
reports backend state in Memory diagnostics.
When QMD session export is enabled without an explicit retention value, Fased
uses a 30-day retention period.
Session Archive Hook
Thesession-memory hook writes session artifacts when a session is reset or a
new session starts. Agent > Memory is the normal control surface.
Seeing memory/ - directory, 0 markdown files usually means the archive path is
ready but no qualifying /new or /reset event has written content yet.
Memory Wiki Export
Memory Wiki is an operator export, not automatic recall. It compiles reviewed memory Markdown into~/.fased/memory-wiki/<agentId>/index.md and source pages.
Properties:
- source files stay in the Agent workspace
- output files stay under the Fased state directory
- filenames are capped and sanitized
- reads and writes use root-confined filesystem helpers
- rebuild is explicit and audited as an admin RPC
Task Memory Scope
Tasks use the owning Agent’s memory policy. A task may still block memory tools depending on its memory scope:
Check task run logs and Agent > Tasks for requested/effective memory scope.
Diagnostics
Use these surfaces:- Agent > Memory: selected Agent archive state, roots, backend, QMD, plugin, and validation.
- Memory page: cross-Agent diagnostics and memory overview.
- Advanced > Debug: Memory Doctor repair preview and gated repair.
fased memory status --agent <id>fased memory doctor --agent <id>