MonoClaw

Sessions

Mona remembers your conversations across restarts. Sessions are stored locally in ~/.monoclaw/sessions/ and are fully under your control.

Session basics

Every conversation creates a session. Sessions contain:

  • The full message history
  • Tool call results
  • File attachments and context
  • Session metadata (model used, start time, platform)

Resume a session

monoclaw --continue       # Resume the most recent session
monoclaw -c               # Short form
monoclaw --continue <id>  # Resume a specific session

List and search sessions

monoclaw sessions list              # List recent sessions
monoclaw sessions search "docker"   # Search session history
monoclaw sessions show <id>         # Show full session transcript

Session management

monoclaw sessions rename <id> "New name"
monoclaw sessions delete <id>
monoclaw sessions export <id> > session.md

Per-platform sessions

Mona tracks separate sessions per platform:

  • CLI sessions are private to your terminal
  • Telegram sessions are tied to your Telegram user ID
  • Discord sessions are tied to your Discord user ID
  • Gateway DMs vs group chats have separate sessions

This means you can have a work conversation in Telegram and a personal coding session in CLI without them interfering.

Session limits

Sessions are only limited by your disk space. Old sessions can be archived or deleted manually. There is no automatic expiration.

Tips

  • Use /save during a chat to give the session a memorable name
  • Use /fork to split a session into a new branch for experimentation
  • Use monoclaw sessions export to create shareable markdown transcripts