Memoh/assets/getting-started_sessions.md.CaVKbfb5.js

import{_ as s,o as t,c as n,ag as o}from"./chunks/framework.DXGyWiRo.js";const u=JSON.parse('{"title":"Sessions","description":"","frontmatter":{},"headers":[],"relativePath":"getting-started/sessions.md","filePath":"getting-started/sessions.md","lastUpdated":1774787421000}'),a={name:"getting-started/sessions.md"};function i(r,e,h,l,d,c){return t(),n("div",null,[...e[0]||(e[0]=[o('<h1 id="sessions" tabindex="-1">Sessions <a class="header-anchor" href="#sessions" aria-label="Permalink to &quot;Sessions&quot;">​</a></h1><p>A <strong>Session</strong> is an independent conversation thread between a user and a bot. Each session maintains its own context window and message history, allowing the bot to focus on a specific topic or task without interference from other conversations.</p><hr><h2 id="concept-conversation-isolation" tabindex="-1">Concept: Conversation Isolation <a class="header-anchor" href="#concept-conversation-isolation" aria-label="Permalink to &quot;Concept: Conversation Isolation&quot;">​</a></h2><p>When you chat with a bot, your messages are grouped into a session. The bot uses the session&#39;s history to maintain context. Starting a new session resets this context, giving you a fresh conversation without losing the previous one.</p><p>Sessions are scoped per bot — each bot manages its own set of sessions independently.</p><hr><h2 id="session-types" tabindex="-1">Session Types <a class="header-anchor" href="#session-types" aria-label="Permalink to &quot;Session Types&quot;">​</a></h2><p>Memoh uses four session types to separate different kinds of bot activity:</p><table tabindex="0"><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><strong>Chat</strong></td><td>Standard user-initiated conversations. This is the default session type when chatting with a bot.</td></tr><tr><td><strong>Heartbeat</strong></td><td>Automatically created when a bot&#39;s heartbeat triggers. Contains the bot&#39;s periodic autonomous activity.</td></tr><tr><td><strong>Schedule</strong></td><td>Created when a scheduled task fires. Contains the bot&#39;s execution of a cron-triggered command.</td></tr><tr><td><strong>Subagent</strong></td><td>Created when the bot delegates a task to a subagent. Contains the subagent&#39;s independent work context.</td></tr></tbody></table><p>Only <strong>Chat</strong> sessions are directly created by users. The other types are system-managed and appear as read-only records in the session list.</p><hr><h2 id="starting-a-new-session-with-new" tabindex="-1">Starting a New Session with <code>/new</code> <a class="header-anchor" href="#starting-a-new-session-with-new" aria-label="Permalink to &quot;Starting a New Session with `/new`&quot;">​</a></h2><p>The <code>/new</code> slash command creates a fresh chat session, resetting the conversation context. This works across all channels:</p><h3 id="in-external-channels-telegram-discord-feishu-etc" tabindex="-1">In External Channels (Telegram, Discord, Feishu, etc.) <a class="header-anchor" href="#in-external-channels-telegram-discord-feishu-etc" aria-label="Permalink to &quot;In External Channels (Telegram, Discord, Feishu, etc.)&quot;">​</a></h3><p>Send <code>/new</code> as a message to the bot. The bot will:</p><ol><li>Create a new chat session.</li><li>Route all subsequent messages from you to this new session.</li><li>The previous session&#39;s history is preserved but no longer active.</li></ol><p>This is especially useful when:</p><ul><li>You want to change topics without the bot referencing old context.</li><li>The conversation has become too long and you want a clean start.</li><li>You are switching between different tasks.</li></ul><h3 id="in-the-web-ui" tabindex="-1">In the Web UI <a class="header-anchor" href="#in-the-web-ui" aria-label="Permalink to &quot;In the Web UI&quot;">​</a></h3><p>The Web UI provides a session sidebar where you can:</p><ul><li>Click the <strong>New Session</strong> button to create a fresh chat session.</li><li>Switch between existing sessions by clicking on them.</li><li>Search sessions by content.</li><li>Filter sessions by type (chat, heartbeat, schedule, subagent).</li><li>Rename or delete sessions.</li></ul><hr><h2 id="managing-sessions" tabindex="-1">Managing Sessions <a class="header-anchor" href="#managing-sessions" aria-label="Permalink to &quot;Managing Sessions&quot;">​</a></h2><h3 id="viewing-sessions" tabindex="-1">Viewing Sessions <a class="header-anchor" href="#viewing-sessions" aria-label="Permalink to &quot;Viewing Sessions&quot;">​</a></h3><p>In the Web UI, the session sidebar lists all sessions for the currently selected bot. Each entry shows:</p><ul><li><strong>Title</strong> — The session name (auto-generated or user-defined).</li><li><strong>Type</strong> — The session type icon.</li><li><strong>Last Activity</strong> — When the session was last active.</li></ul><h3 id="renaming-sessions" tabindex="-1">Renaming Sessions <a class="header-anchor" href="#renaming-sessions" aria-label="Permalink to &quot;Renaming Sessions&quot;">​</a></h3><p>Click on a session title to rename it. This helps organize conversations by topic.</p><h3 id="deleting-sessions" tabindex="-1">Deleting Sessions <a class="header-anchor" href="#deleting-sessions" aria-label="Permalink to &quot;Deleting Sessions&quot;">​</a></h3><p>Remove sessions you no longer need. Deleting a session removes its message history permanently.</p><hr><h2 id="how-sessions-relate-to-other-features" tabindex="-1">How Sessions Relate to Other Features <a class="header-anchor" href="#how-sessions-relate-to-other-features" aria-label="Permalink to &quot;How Sessions Relate to Other Features&quot;">​</a></h2><ul><li><strong>Heartbeat</strong> sessions are created on each heartbeat trigger. You can view what the bot did during its autonomous activity by opening the corresponding heartbeat session.</li><li><strong>Schedule</strong> sessions are created when a scheduled task runs. Check these to see the results of cron-triggered commands.</li><li><strong>Subagent</strong> sessions track delegated tasks. They show the independent work context of each subagent invocation.</li><li><strong>Memory</strong> is shared across all sessions for a bot — memories extracted from one session are available in all others.</li></ul>',34)])])}const b=s(a,[["render",i]]);export{u as __pageData,b as default};