Memory system overview

What this accomplishes

How Miton’s memory store and convention learning work, how to manage them, and how they persist across sessions.

Miton keeps two kinds of long-term context for your project:

1. Memory store — a local database of facts, context, and notes
2. Convention learning — tracks stylistic corrections and applies them automatically

Current availability

This page documents behaviour verified in Miton development builds. Miton is still pre-release and is not publicly downloadable; invited beta users will receive a signed desktop build with automatic updates.

Before you start

• A Miton development build and an active project.
• A connected cloud or local model, plus any credentials or local runtime required by this task.

Memory store

The memory store is a local SQLite database scoped to your project root (<project-root>/.miton/memory.sqlite).

What gets stored

The agent writes to the memory store automatically when it identifies something worth remembering:

• Facts you state explicitly (“My deployment target is Railway”)
• Corrections and project rules learned from your instructions
• Turns, tool calls, and file operations from earlier sessions it may need later

You can also add a fact directly in chat (“Remember that we use strict types”).

Viewing and editing memory

Open the Memory panel in the right sidebar to see every stored item — facts, corrections, project rules, and session memory in one list. Filter by category (All, Preferences, Project, Corrections, Patterns, Session). Each item shows where it came from and its scope (project-bound, personal, or global). Hover an item to edit or delete it, or to jump back to the conversation that created it. Edits and deletions take effect immediately.

The memory chip in the status bar

The memory chip in the status bar shows the current memory setting for this session:

• On — the agent reads from and writes to the memory store this session
• Off — the agent ignores the memory store this session; no reads, no writes
• Automatic (default) — Miton decides based on the task

Use Off when you want an isolated session that starts without prior context — useful for testing, one-off tasks, or sensitive work.

Privacy

The memory store is local-only. No memory data leaves your machine unless you export it yourself (see below) or share the project with someone else.

Corrections and conventions

Convention learning tracks stylistic corrections you make and the patterns the agent infers from them, separately from ordinary facts. Open Settings → Project knowledge → Convention memory to review every accepted or rejected pattern, its recency-weighted confidence, and its history. Ignore a pattern to silence it without deleting its record, or delete it outright.

Export and delete

Settings → Project knowledge → Project memory has a Memory data section with two actions:

• Export portable copy — saves the project’s memory as an NDJSON file you choose the location for.
• Delete all project memory — permanently clears the local memory store for this project.

Bringing memory in from a shared project

When you receive memory from a shared project, the incoming entries land in a quarantine area first, not straight into your live memory. Review them at Settings → Safety & privacy → Imported memory review, where you can accept items one at a time (or all at once) into your project’s memory, or reject them. Anything left unreviewed is purged automatically after 30 days.

What success looks like

How Miton’s memory store and convention learning work, how to manage them, and how they persist across sessions. The result remains attached to the active project when you move to another workspace.

Common failures and recovery

• Confirm the correct project and model are active.
• Read the exact error and the requested permission before retrying.
• Retry only the failed step so completed project work remains intact.

Related next action

• Sessions — how sessions interact with memory
• Routing profiles — how memory feeds into routing decisions