Skip to content

Memory


What Atoi remembers about you, how it proposes new memories, and how to review or remove them.

Memory is what Atoi carries between threads: the way you like things written, a convention a project uses, a constraint you stated once and expect forever.

#Keep only what lasts

Durable, reusable, and worth attributing: a writing style, a naming convention, a standing preference. Temporary details belong in the thread or the project. Secrets never belong in memory.

#Atoi proposes, you decide

When Atoi notices a pattern, it proposes remembering it and says what it observed and what would change. One interaction never silently becomes a permanent rule, and a project convention never quietly becomes an account-wide preference.

Something you state outright is stronger than something Atoi inferred.

#Review and remove

Open Settings → Memory. Each entry shows what it is and where it applies. Edit or remove anything wrong, stale, or too broad.

Capture pending: Settings, Memory, with entries and their scopecapture pendingSettings, Memory, with entriesand their scope1440×900/settings/memory
Settings, Memory, with entries and their scope

Removing a memory changes what Atoi does next. It does not rewrite past threads or receipts.

#Not everything is memory

Your theme, shortcuts, enabled models, and rules are settings, not memories. Change them on their own settings pages.

Read Asks and approvals for rules and Models and keys for model defaults.

Was this useful?