import{_ as t,o as a,c as o,ag as s}from"./chunks/framework.CAXxHpAX.js";const g=JSON.parse('{"title":"About Memoh","description":"","frontmatter":{},"headers":[],"relativePath":"about.md","filePath":"about.md","lastUpdated":1776332711000}'),i={name:"about.md"};function n(r,e,l,d,h,c){return a(),o("div",null,[...e[0]||(e[0]=[s('
Memoh is a multi-member, structured long-memory, containerized AI agent platform. You can create multiple AI bots, give each bot its own isolated workspace and long-term memory, and interact with them through Telegram, Discord, Lark (Feishu), QQ, Matrix, Misskey, DingTalk, WeCom, WeChat, WeChat Official Account, Email, or the built-in Web UI.
Every bot has its own execution environment, tools, memory configuration, and channel integrations. In practice, that means each bot behaves more like its own computer-backed agent than a shared chat preset.
Memoh is built for real sharing and real separation at the same time:
Each bot runs in its own isolated container workspace with a separate filesystem and network boundary. Bots can read and write files, run commands, and use tools inside that workspace without interfering with other bots.
Memoh separates two different problems:
This distinction is important: context compaction changes the active session window, while memory compaction rewrites stored memory entries.
Each bot maintains independent sessions that preserve context. Memoh currently uses five session types:
You can start or route sessions with slash commands such as /new, and the Web UI exposes a session status panel with metrics like context usage, cache hit rate, and used skills.
Memoh uses a unified channel adapter system so one bot can be reachable from many places at once.
Current user-facing integrations include:
Memoh also distinguishes between the personal WeChat QR-login integration and the webhook-based WeChat Official Account integration.
Bots can use a rich set of built-in capabilities, including:
Memoh supports multiple provider client types, including:
Models are also separated by role:
Image generation is configured through compatible chat/image models rather than a separate image-provider system.
The Web UI is designed so you can manage the whole system without editing config files by hand every day. It includes: