Deploy OpenAB with Google Antigravity CLI (agy) as a Discord bot. Uses the agy-acp Rust adapter for reliable ACP stdio communication. Supports multi-turn conversations via --continue session continuity.

One-click deployment of OpenAB with Google Antigravity CLI as the AI agent backend. This template uses the agy-acp Rust adapter for stable stdin/stdout pipe communication.
beta tag. To pin a specific version, change the image tag in Zeabur Dashboard → Service → Settings./home/agent is mounted as a persistent volume. Config, auth tokens, and session data survive restarts.config.toml is generated at /home/agent/.config/openab/config.toml on first boot. Edit it directly after that — env vars are only used for initial setup.agy-acp) bridges OpenAB to Google Antigravity CLI--continue session continuityDISCORD_BOT_TOKENbot → check permissions: Send Messages, Send Messages in Threads, Create Public Threads, Read Message History, Add Reactions, Manage MessagesAfter deployment, open the Exec tab in Zeabur Dashboard and run:
agy auth
Complete the device flow in your browser. Auth tokens persist in the volume at ~/.gemini/.
Set OPENAB_ALLOWED_CHANNELS to restrict which channels the bot responds in. Leave empty to allow all channels.
connections:writeapp_mention, message.channels, message.groupsapp_mentions:read, chat:write, channels:history, groups:history, channels:read, groups:read, reactions:write, files:read, users:readxoxb-... token and xapp-... token| File | Description |
|---|---|
/home/agent/.config/openab/config.toml | OpenAB config (sessions, reactions, etc.) |
To reset config to defaults: rm /home/agent/.config/openab/config.toml and restart.
agy -p returns the full response at onceagy -p runs to completion--continue (resumes most recent conversation per container)