> Source: Onevium official documentation
> Article: Memory, user rules, and work recaps
> Original URL: https://onevium.com/docs/memory-and-recap
> Language: English
> Updated: 2026-09-09
> Applies to: 1.1.22
> Feature status: Released

---

# Memory, user rules, and work recaps

Distinguish persistent memory, rule files, and recaps, then configure extraction, recall, cross-project scope, and budget.

## Distinguish 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       | Memories at the bottom of Personalization                 |
| 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 Briefing | An `@Recap` request or Daily Briefing in the sidebar      |

**`@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](https://onevium.com/docs/skills).

Check AI Autonomy and memory extraction in Personalization, then open Memories. Related controls may be hidden or unavailable while the master switch is off.

## First task: save and correct a memory

1. Open Settings → Personalization → Memories. To save a project fact, first select that project in the filter.
2. 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.
3. Search for the item and verify content and scope. **Adding without a specific project selected can create a global memory.**
4. 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.
5. 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 older missing configuration falls back to **$0.10/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 Briefing

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.

```text
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.
```

For recent activity across projects, open Daily Briefing from the sidebar. Its gear controls generation, model, schedule, today/yesterday scope, output language, and included projects. Check the scope of manual recaps and automatic briefings separately.

## 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.

## Common problems

- Missing saved item: check whether you used file-based `@Memory` or 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 briefing project: check projects and generation date in the briefing gear, not memory settings.

## Next steps

Use the [Personalization reference](https://onevium.com/docs/settings/reference#personalization), save repeatable procedures as a [Skill](https://onevium.com/docs/skills), and continue [projects and sessions](https://onevium.com/docs/projects-and-sessions) with a verifiable recap.