Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.augustin.ai/llms.txt

Use this file to discover all available pages before exploring further.

Self-hosted AI assistant gateway. Connects to messaging channels and routes conversations to AI backends. Runs on i3.

​
Access

  • Control UI: openclaw.augustin.ai — new devices require pairing approval via devices list / devices approve
  • Matrix bot: DM the bot user configured in openclaw.json
  • Telegram bot: @tyson_am_openclaw_bot

​
Services

All run via openclaw/compose.yaml:
ContainerPurpose
openclaw-gatewayGateway process, Control UI, channel connections, agent runtime
openclaw-cliInteractive CLI, shares gateway’s network stack
Built from source with the Matrix and Telegram extensions. The source tree (openclaw-src/) is gitignored.

​
Configuration

Gateway config lives in data/openclaw/openclaw.json, mounted into the container. Edit on the host and restart, or use the Control UI’s config editor.

​
Model Provider

LLM inference routes through AIClient-2-API (aiclient2api container), which proxies requests via Kiro billing. OpenClaw sees it as a custom OpenAI-compatible provider (kiro/claude-sonnet-4-5). Falls back to direct Anthropic API if the proxy is down. The Kiro auth token is synced automatically from the local Kiro CLI’s SQLite DB via a cron job (sync-kiro-token.py every 15 min). The Kiro CLI manages its own token refresh via IAM Identity Center.

​
Networking

The gateway joins the traefik network for reverse proxy access. It binds to LAN inside the container so Traefik can reach it. Host port mapping remains localhost-only. The Control UI uses WebSocket connections — allowedOrigins in the gateway config must include the public URL.

​
Matrix

OpenClaw connects outbound to the local Synapse homeserver as a Matrix user. The Matrix plugin is baked into the image at build time. DM access is controlled via allowlist in openclaw.json.

​
Telegram

OpenClaw connects to Telegram via the Bot API. The bot token is stored in openclaw/.env and referenced in openclaw.json via ${TELEGRAM_BOT_TOKEN}. DM access is locked to an allowlist of Telegram user IDs.