miton

In development. The beta will be a downloadable desktop app with automatic updates. Access is not open yet.Request an invitation.

Guide · 3 min read

Memory system overview

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

Product stage
Pre-release development
Last reviewed
2026-07-23
Successful result
The change is visible in the active project.

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”)
  • Project conventions it has learned from your instructions
  • Notes from previous sessions it may need later

You can also store things manually: select text in the transcript and click Save to memory, or use the /remember skill.

Viewing and editing memory

Open Settings → Memory (or the memory chip in the status bar) to see all stored items. Each item shows:

  • The content
  • When it was written
  • Which session wrote it
  • The confidence level (0–1)

Click any item to edit or delete it. Edits take effect immediately.

The memory chip in the status bar

The memory chip (second chip from the left in the status bar) shows the on/off state:

  • On (default) — the agent reads from and writes to the memory store this session
  • Off — the agent ignores the memory store for this session; no reads, no writes

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.

Corrections and conventions

Corrections can be stored as ordinary project memory. Open Settings → Memory to inspect the recorded instruction, edit its wording or remove it. Clearing project memory removes those entries and returns the next session to the project’s explicit rules and current conversation only.

Miton does not currently expose a separate convention-management or memory export/import workflow. Those are product-roadmap concerns rather than steps in this guide.

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.