List all available memory sections. Use this to discover what project context is stored. Returns section names and descriptions.

Read a memory section. Use this to retrieve stored project context such as architecture decisions, API contracts, conventions, bugs, todos, or glossary. Prefer reading memory before scanning unrelated source files.

Overwrite a memory section with new content. WARNING: This replaces the entire section. Use with care. Prefer append_decision or append_api_contract for adding entries. Only use write_memory when you need to restructure or rewrite a full section.

Record an architecture or design decision. Use this after making a significant technical choice. Stores a structured ADR (Architecture Decision Record) with context, decision, consequences, and related files. Do not store full source code — store only the rationale and outcome.

Use this tool after creating or modifying an API endpoint. Store only the durable endpoint contract: method, path, auth, request shape, response shape, side effects, frontend usage, and related files. Do not store full source code.

Use this tool before scanning the codebase when the user asks about project architecture, API contracts, decisions, bugs, conventions, or previous implementation choices. Searches all memory sections using keyword matching and returns matching lines with surrounding context.

Get a compact overview of project memory. Returns headings and short excerpts for each section. Use this for a quick orientation before diving into specific sections with read_memory.