39 lines
1.9 KiB
Markdown
39 lines
1.9 KiB
Markdown
---
|
|
name: memory
|
|
description: Search conversation history and understand Dream-managed profile and memory files.
|
|
---
|
|
|
|
# Memory
|
|
|
|
## Structure
|
|
|
|
- `SOUL.md` — Bot personality and communication style. **Managed by Dream.** Do NOT edit.
|
|
- `USER.md` — User profile and preferences. **Managed by Dream.** Do NOT edit.
|
|
- `memory/MEMORY.md` — Long-term facts (project context, important events). **Managed by Dream.** Do NOT edit.
|
|
- `memory/history.jsonl` — append-only JSONL, not loaded into context. Prefer the
|
|
built-in `grep` tool to search it.
|
|
|
|
## Search Past Events
|
|
|
|
Use the absolute `History log` path shown in the system prompt. Always pass it to
|
|
`grep`; never substitute a project-relative `memory/history.jsonl`, which may belong
|
|
to the selected project. Each JSONL line contains `cursor`, `timestamp`, and `content`.
|
|
|
|
- For broad searches, start with `output_mode="count"` or the default
|
|
`files_with_matches` mode before expanding to full content
|
|
- Use `output_mode="content"` plus `context_before` / `context_after` when you need the exact matching lines
|
|
- Use `fixed_strings=true` for literal timestamps or JSON fragments
|
|
- Use `head_limit` / `offset` to page through long histories
|
|
|
|
Examples (replace `<history-log-path>` with the absolute path from the system prompt):
|
|
- `grep(pattern="keyword", path="<history-log-path>", case_insensitive=true)`
|
|
- `grep(pattern="2026-04-02 10:00", path="<history-log-path>", fixed_strings=true)`
|
|
- `grep(pattern="keyword", path="<history-log-path>", output_mode="count", case_insensitive=true)`
|
|
- `grep(pattern="oauth|token", path="<history-log-path>", output_mode="content", case_insensitive=true)`
|
|
|
|
## Important
|
|
|
|
- **Do NOT edit SOUL.md, USER.md, or MEMORY.md.** They are automatically managed by Dream.
|
|
- If you notice outdated information, it will be corrected when Dream runs next.
|
|
- Users can view Dream's activity with the `/dream-log` command.
|