Memory, user rules, and work recaps
Distinguish persistent memory, rule files, and recaps, then configure extraction, recall, cross-project scope, and budget.
Your workspaceDistinguish four purposes#
| What you want to retain | Use | Actual entry point |
|---|---|---|
| Stable preferences and recurring habits | User Rules | Settings → Personalization → User Rules |
| Project facts to retrieve later | Onevium memories | Settings → Personalization → Memory space |
| Project rules or Claude Code topic-memory files | An @Memory request | Insert the tag and send a request to create or edit files |
| What happened and what comes next | Recap / Daily review | A scoped recap request, or the separately installed Daily review Skill |
@Memory does not mean adding a row to Onevium's memory list. It can help write CLAUDE.md, rules, and topic-memory files. Verify database memories in the settings list.
Choose the scope before saving#
Keep lasting rules concise and stable. Do not store passwords or temporary tokens. A project-specific fact should not become a rule for every project. Repeated procedures belong in a Skill.
Check AI Autonomy and memory extraction in Personalization, then open Memory space. Related controls may be hidden or unavailable while the master switch is off.
First task: save and correct a memory#
- Open Settings → Personalization → Memory space. To save a project fact, first select that project in the filter.
- If no projects are available yet, practice with a genuine global preference, such as “Start answers with the conclusion, then give evidence.” Add it under the user category and save.
- Search for the item and verify content and scope. Adding without a specific project selected can create a global memory.
- Make a related request in a new conversation and check how the information is used. A saved item is not guaranteed to be recalled every time.
- Edit the old memory when the convention changes instead of only adding a contradiction. Disable an item temporarily or handle obsolete items through the list actions.
The project filter currently comes from existing project memories. If a new project is absent, work in that project with extraction enabled and check again once it has memories. Do not save a project fact globally to bypass a missing filter option.
Extraction: when new memories are written#
| Option | When to use it |
|---|---|
| High / balanced / economy | Attempt extraction each turn, every 3 turns, or every 5; coverage and cost differ |
| Extraction frequency off | Stop new extraction while retaining recall of existing memories |
| Deep extraction | Include reasoning, alternatives, and tradeoffs |
| Extraction language | Choose the language of new memories; Auto follows the interface |
| Included projects | Exclude projects that should not produce new memories |
These options govern new content, not deletion. Existing memories from an excluded project can still participate in normal recall.
Recall: what later conversations remember#
- Recall threshold: use Strict when irrelevant items appear; try Balanced or Relaxed when useful facts are missed. Fresh installs start Strict; older missing configurations fall back to Balanced.
- Cross-project search: enable when work needs facts from other projects. It is off by default and broadens retrieval, not blanket injection of every project.
- Memory context length: Compact, Balanced, or Detailed controls how much memory accompanies a request, not the model's context window.
- Synthesis frequency: Daily, Weekly, or Off controls summary organization and merging. Off does not stop old-memory decay.
Change one option, then compare similar questions in the same project rather than changing everything at once.
Budget and extraction model#
Select a working extraction model and daily budget near the bottom of Personalization. Start with a fast, inexpensive model. Deep extraction and higher frequency increase usage.
The fresh-install budget baseline is $10/day; an earlier installation that never set a budget falls back to $1/day. Your saved value may differ. This limits automatic extraction, not all chat, every model, or total account spending. Check the actual setting and today's usage.
Recaps and Daily review#
After a piece of work, insert @Recap, specify a date or task scope, and send. The tag helps the assistant perform a request; it does not directly open a settings page.
Recap today's work in this project.
Separate completed results, checks performed, unresolved issues,
and next steps. Point to files or conversations as evidence.
Do not describe unverified work as completed.
The built-in Daily Briefing was retired in 1.3.3. Its old database rows remain, but its page and dedicated trigger are no longer available. Install the official Daily review Skill for a configurable replacement: review selected work, save a short report and source-backed lessons in Space, and schedule it only when requested. Old briefing schedules are not migrated automatically.
Confirm the information is reliable#
Saved memories have the correct content and scope. Recaps point to real files and conversations. Before resuming, recheck changing facts such as code, running services, and deployments. An older summary is a lead, not proof of current state.
Rules, extraction, recall, and recaps are separate stages. Disabling one does not mean the other stages' history is deleted.
Trace a memory to its evidence
From 1.3.2, memories are extracted only from what you said or confirmed. Each memory shows its source conversation, evidence, and change history. Memory space lets you browse every memory, see how a memory connects to others, and check how often it is used and what it affects.
When an answer uses a memory, it is marked; open the marker to see the evidence. Content you forget is never recalled again. After an upgrade from 1.3.1, all memories are kept and the vector index is rebuilt in the background; keyword recall keeps working meanwhile.
Common problems#
- Missing saved item: check whether you used file-based
@Memoryor the database memory list. - Old facts after extraction is off: inspect recall and disable or correct the item in the list.
- Noisy memory: tighten the threshold and check cross-project search and scope.
- Missing Daily review: install the community Skill separately and confirm its enabled project scope. The old Daily Briefing page is retired.
Next steps#
Use the Personalization reference, save repeatable procedures as a Skill, and continue projects and sessions with a verifiable recap.