OpenAB MiMoCode

OpenAB bridges Discord, Slack, or gateway platforms to ACP-compatible coding CLIs. This template runs the MiMoCode variant via mimo acp.

Important Notes

• Image tag: This template tracks ghcr.io/openabdev/openab:beta-mimocode.
• Persistent storage: /home/node is mounted as a persistent volume. MiMoCode config, SQLite state, credentials, and OpenAB config survive restarts.
• SQLite locking: Do not run manual mimo commands while the bot is handling a request. MiMoCode stores state in SQLite and only one process should access it at a time.

Setup

1. Create a Discord bot at https://discord.com/developers/applications, enable Message Content Intent, and paste the token into DISCORD_BOT_TOKEN.
2. Deploy the template. By default, startup writes a MiMoCode config that disables auto-detected Bedrock providers and selects mimo/mimo-auto.
3. Startup runs mimo auth login --provider mimo --method "MiMo Auto (free)" unless MIMOCODE_AUTO_AUTH=false.

For Slack, set SLACK_BOT_TOKEN and SLACK_APP_TOKEN. For Telegram, LINE, Feishu/Lark, Google Chat, Teams, or WeCom, deploy the OpenAB Gateway template and add GATEWAY_URL / GATEWAY_PLATFORM to this service.

Customization

File	Description
/home/node/.config/openab/config.toml	OpenAB config
/home/node/.config/mimocode/config.json	MiMoCode config
/home/node/.local/share/mimocode/mimocode.db	MiMoCode SQLite state

To regenerate OpenAB config, delete /home/node/.config/openab/config.toml and restart.

Links

• OpenAB GitHub
• OpenAB MiMoCode docs
• GitHub Packages