> ## Documentation Index
> Fetch the complete documentation index at: https://oximy.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Memory

> What Sidekick remembers across threads and how to manage it.

Sidekick can hold on to durable facts about you and carry them into threads you haven't started yet. This page covers what gets remembered, how to manage it, and who can see it.

## What Sidekick remembers

Memory is context that's true beyond a single thread: a preference, an ongoing project, something you'd otherwise have to re-explain every time. Once a fact is saved, later threads can draw on it without you restating it. This is what gives Sidekick continuity from one thread to the next instead of starting cold every time.

## Manage what's remembered

<Steps>
  <Step title="Save a fact">
    Tell Sidekick to remember something in the middle of a thread, or add it directly under Settings → Memory.
  </Step>

  <Step title="Correct a fact">
    If something saved is wrong or out of date, tell Sidekick the correction in a thread, or edit the fact directly under Settings → Memory.
  </Step>

  <Step title="Forget a fact">
    Ask Sidekick to forget something, or delete it directly under Settings → Memory. Once it's gone, later threads stop drawing on it.
  </Step>
</Steps>

<Note>
  Memory is per-user. What Sidekick remembers about you belongs to you: nobody else in your workspace can see it, and it never feeds anyone else's threads.
</Note>

## Where to go next

<CardGroup cols={2}>
  <Card title="The thread and composer" icon="message-square" href="/docs/sidekick/use/thread-and-composer">
    How a thread holds a conversation and how the composer starts and steers it.
  </Card>

  <Card title="Governance model" icon="shield-check" href="/docs/sidekick/concepts/governance-model">
    How consent gates and admin approval keep external and sensitive actions in bounds.
  </Card>
</CardGroup>