# Memory

> Use private Daily Desk memory without confusing it with public hub previews.

Source: https://docs.thalovant.com/workspace/memory/

---
{/* Last Edit: Claude Opus 5.5 - 2026-09-28 - Motive: Free keeps one memory item; kid-labelled hubs and previews keep none. */}

Memory is private workspace context for Daily Desk and other workspace assistants. Use it for notes, preferences, and facts that should persist across sessions.

Public hubs don't store personal memory. The one exception is public Daily Desk, which keeps a short chat memory for each connected client, so it can answer “what was the last joke you told me?”, and forgets it when you say “forget what I said”. The web preview on the site keeps none, and it never reads private workspace data. Daily Desk in the public catalog is the showroom: it lets people try the style, prompts, and everyday skills before they move to a private workspace.

## Public Showroom vs Private Memory

| Surface | Stores personal memory? | Good for |
| --- | --- | --- |
| Public Daily Desk | Only a short chat per connected client, cleared on request; none for the web preview | Trying the public hub, starter prompts, and everyday voice flow. |
| Free plan memory | One durable personal memory item | Letting the assistant remember one useful thing before you upgrade. |
| Private Daily Desk memory | Yes, inside the workspace boundary, with no item limit on paid plans | Preferences, notes, and facts for a Home, Family, or Work plan. |
| Kid-labelled hubs and preview sessions | No | Children and anonymous visitors. No memory, transcript, or IP address is kept. |

  Don't put customer secrets, credentials, payment details, or regulated records into memory. Keep memory short, intentional, and easy to delete.

## Private Memory Setup

1. **Confirm the plan.** The private memory skill runs on your own hub, so it needs Home, Family, or a Work plan with private runtime capacity.
2. **Open Memory.** Create or review private notes, preferences, and facts.
3. **Create a runtime token.** Use the Memory page to create a scoped token with `memory:read` and `memory:write`.
4. **Install the memory skill.** Add `thalovant-skill-memory` to the private skill set that serves the hub.
5. **Set the skill secret.** Store the runtime token in the skill secret field named `access_token`.
6. **Test save and recall.** Ask the private hub to remember one harmless preference, then ask for it later.
7. **Revoke when needed.** Revoke the runtime token from Memory and confirm the skill can no longer read or write memory.

## What To Store

  
    Communication style, preferred briefing order, default city, or recurring work habits.
  
  
    Stable workspace facts that help the assistant answer without asking again.
  
  
    Short private context that should be reviewed or deleted when it's no longer useful.
  

## Runtime Token Rules

- Create tokens from the Memory page, not from screenshots or chat logs.
- Use only `memory:read` and `memory:write` for the memory skill.
- Store the token in the private skill secret field.
- Copy the token once, then treat it as secret.
- Revoke tokens that are unused, copied to the wrong place, or no longer needed.

## Verification Checklist

A private memory setup is ready when:

- public Daily Desk still says its memory is per client, can be forgotten, and never reaches private workspace data;
- the private workspace can create a scoped runtime token;
- the memory skill can save and recall a harmless test preference;
- the Memory page shows the saved item;
- deleting the item removes it from normal recall;
- revoking the token makes runtime memory access fail.