Sessions and context

What this accomplishes

Use sessions to separate conversations, keep project history, and control how much context each chat carries.

Changing between Canvas, Writer, Automation and Code does not change the active session. The full Chat view, side dock and compact dock are presentations of the same conversation. Create or select a different session only when you want a genuinely separate conversation.

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.

Steps

1. Click New session in the header or sidebar for a fresh thread.
2. Select a prior session from the sidebar history to resume it.
3. Use the session menu to rename, archive, or export history.

What success looks like

A clean compose view for a new session, or loaded messages and linked files for a resumed session. Opening another workspace leaves that session, its Plan and approval state intact.

Common failures and recovery

• Session feels slow or expensive: Start a new session to clear the active context buffer. Files on disk stay in the project.
• Accidental deletion: Recover archived sessions from Settings → Archived sessions.

Related next action

• Per-turn rewind — undo agent steps within a session.
• Memory overview — what persists across sessions.