Skip to content

Sessions

mikan separates platform chat history from pi-coding-agent structured session history.

PlatformsessionKey RuleNotes
Slacktop-level / DM: conversationId; thread: conversationId:threadTsthread sessions are fixed files bootstrapped from recent chat history
DiscordDM: channelId; shared top-level: channelId:messageId; reply/thread: rooted idreplies in shared channels continue the root message session
Telegramprivate: chatId; shared top-level: chatId:messageId; reply chain: root replyno native thread model; shared sessions are inferred from reply chains
  • log.jsonl is the platform-facing, human-readable message history.
  • sessions/*.jsonl is the structured pi-coding-agent context, including tool results.
  • sessions/current points at the active top-level session.
  • Thread/reply scopes use fixed session files derived from the scope id.

Use new / /new in chat to reset the current session. The previous files remain on disk for inspection unless manually removed.