Open Agent Broker — a lightweight Rust harness that bridges Discord to any ACP-compatible coding CLI over stdio JSON-RPC. This template uses OpenCode as the agent backend, supporting 75+ LLM providers (Ollama Cloud, OpenAI, Anthropic, Google, and more). Source: https://github.com/openabdev/openab

OpenAB is a lightweight, open-source Rust harness that bridges Discord to any Agent Client Protocol-compatible coding CLI over stdio JSON-RPC.
This template uses OpenCode as the agent backend, supporting 75+ LLM providers (Ollama Cloud, OpenAI, Anthropic, Google, and more).
0.8.1-beta.5). To upgrade, change the image tag in Zeabur Dashboard -> Service -> Settings. Available tags: GitHub Packages./home/node is mounted as a persistent volume. Settings, config, credentials, and opencode.json survive restarts.node user before running openab. If you encounter permission issues, restart the service -- ownership is fixed automatically on boot.bot -> check permissions: Send Messages, Send Messages in Threads, Create Public Threads, Read Message History, Add Reactions, Manage MessagesOpenCode needs access to an LLM provider. The simplest approach is to set an environment variable in Zeabur Dashboard -> Service -> Variables:
| Variable | Provider |
|---|---|
OPENCODE_API_KEY | OpenCode (native, get key at opencode.ai) |
ANTHROPIC_API_KEY | Anthropic Claude |
OPENAI_API_KEY | OpenAI GPT |
GOOGLE_GENERATIVE_AI_API_KEY | Google Gemini |
GROQ_API_KEY | Groq |
MISTRAL_API_KEY | Mistral |
DEEPSEEK_API_KEY | DeepSeek |
OPENROUTER_API_KEY | OpenRouter (proxies 100+ models) |
Set at least one variable and restart the service. OpenCode picks it up automatically.
Alternative: Interactive login
For providers that use browser OAuth (e.g. AWS Bedrock, Azure OpenAI), open the service terminal in Zeabur Dashboard and run:
runuser -u node -- opencode auth login
Warning: Must run as
node. Running asrootwrites credentials to/root/which is not persisted; they will be lost on restart.
To configure a specific model, create or edit /home/node/opencode.json:
{
"provider": "anthropic",
"model": "claude-sonnet-4-20250514"
}
See OpenCode documentation for all available providers and models.
123456789012345678,234567890123456789Fill in the Discord Bot Token and click deploy. The service connects to Discord automatically. Then authenticate OpenCode using the method above.
| File | Description |
|---|---|
/home/node/.config/openab/config.toml | OpenAB config (sessions, reactions, STT, etc.) |
/home/node/opencode.json | OpenCode model/provider config |
/home/node/.opencode/ | OpenCode credentials and state |
config.toml is created from a built-in template on first boot. After that, edit the file directly -- environment variables are only used for initial setup. To reset to defaults, delete the file and restart: rm /home/node/.config/openab/config.toml
For config options, see the OpenAB documentation.
By default, openab ignores messages from other bots and webhooks. To allow webhook-triggered messages (e.g. automated testing or CI pipelines), add the following to your config.toml:
[discord]
allow_bot_messages = "mentions"
With this setting, openab responds to any bot or webhook message that @mentions it. To restrict to a specific webhook, also add:
trusted_bot_ids = ["YOUR_WEBHOOK_USER_ID"]
The webhook user ID is the numeric ID in the webhook URL: https://discord.com/api/webhooks/<ID>/...
Leave Discord Bot Token empty. The service sleeps instead of crashing.