A Bot is an independent AI agent that comes with its own isolated container, persistent memory, and configurable personality. Bots can chat via various messaging platforms (Channels) and perform complex tasks using specialized tools.
allow_all or private_only.Once created, clicking on a bot card takes you to its Detail Page, where you can manage its entire lifecycle through specialized tabs.
| Tab | Description |
|---|---|
| Overview | Health checks for container, database, channels, and memory. |
| General | Core runtime settings: chat/title/image models, memory/search/browser/TTS bindings, timezone, language, reasoning, and danger zone. |
| Container | Container lifecycle (create/start/stop), snapshots, data export/import. |
| Memory | Browse, search, create, edit, and compact memories. |
| Platforms | Channel configurations such as Telegram, Discord, Feishu, QQ, Matrix, WeCom, WeChat, Misskey, DingTalk, and Web. |
| Access | ACL rules and default access behavior. |
| Email bindings and outbox. | |
| Terminal | Interactive terminal access to the bot's container. |
| Files | File manager for the bot's container filesystem. |
| MCP | MCP connection management (Stdio, Remote, OAuth). |
| Heartbeat | Heartbeat configuration, model selection, and execution logs. |
| Compaction | Session context compaction settings and logs. |
| Schedule | Cron-based scheduled tasks and execution logs. |
| Skills | Markdown-based skill files that define bot personality and capabilities. |
After creating a bot, the most important step is configuring its runtime settings. These settings are split across a few tabs instead of living in one giant form.
If you have not created these resources yet, set them up first:
The General tab contains the settings that shape everyday conversation behavior.
| Field | Description |
|---|---|
| Chat Model | The main LLM used for generating chat responses. |
| Title Model | Optional model used to generate session titles. |
| Image Generation Model | Optional model used by image-generation features. Pick a chat model that supports image-output. |
| Memory Provider | The memory backend assigned to the bot. The built-in provider can optionally define its own memory and embedding models. |
| Search Provider | The search engine used for web browsing capabilities. |
| TTS Model | Optional speech model used for text-to-speech output. Speech models come from the TTS Providers flow, not the normal chat provider flow. |
| Browser Context | The browser environment used for web automation, such as viewport, locale, and mobile behavior. |
| Timezone | Per-bot timezone. If empty, Memoh inherits the user timezone and then falls back to the system timezone. |
| Language | The bot's primary communication language. |
| Reasoning Enabled | Available when the selected chat model exposes reasoning compatibility. |
| Reasoning Effort | Set the level of reasoning effort (low, medium, high). |
Notes:
speech models such as Edge TTS voices.context_window influences session status reporting and Context Compaction.Heartbeat is configured from its own tab.
| Field | Description |
|---|---|
| Heartbeat Enabled | Enable or disable periodic autonomous activity. |
| Heartbeat Interval | How often the heartbeat runs, in minutes. |
| Heartbeat Model | Optional dedicated model for heartbeat tasks. This can differ from the main chat model. |
The Heartbeat tab also includes heartbeat execution logs, so you can review what the bot did during autonomous runs.
Compaction is now about session context compaction, not memory maintenance.
| Field | Description |
|---|---|
| Compaction Enabled | Enable or disable automatic context compaction. |
| Compaction Threshold | Estimated token threshold that triggers compaction. |
| Compaction Ratio | How aggressively the session context should be reduced. |
| Compaction Model | Optional dedicated model used to summarize old session context. |
The Compaction tab also exposes compaction logs so you can see recent successful, pending, or failed runs.
For the runtime behavior, see Context Compaction.
At creation time, the bot starts from an ACL preset. After that, use the Access tab for fine-grained control.
Two layers matter:
Use the Access tab to refine conversation, group, and thread rules after the initial setup.
Most users only need the chat and discuss behavior described in Sessions.
If you manage bot settings through the API or custom automation, the settings schema also includes discuss_probe_model_id for discuss-mode specific setups. Treat it as an advanced setting rather than a required field for normal bot creation.
The Terminal tab provides interactive shell access to the bot's container:
To permanently remove a bot and all its associated data (including container files and memory):
',51)])])}const b=e(n,[["render",s]]);export{m as __pageData,b as default};Warning: This action is irreversible. All persistent data for this bot will be lost.