Operations and API
Gateway HTTP Surface
According to the current pkg/api/server.go, Gateway now exposes three main things by default:
- health checks
- a Gateway-hosted WebUI entrypoint
- WebUI control APIs
Base Endpoint
Health
GET /healthReturns ok.
Auth
WebUI and API requests are protected by gateway.token.
The current default entrypoint remains the README pattern:
http://<host>:<port>/?token=<gateway.token>The code currently accepts:
?token=<gateway.token>Authorization: Bearer <gateway.token>clawgo_webui_tokencookie
Gateway also enables permissive CORS by default, which makes /api/* easier to consume from external frontends or control panels.
WebUI API Groups
Config and Version
/api/config/api/version
GET /api/config?mode=normalized returns:
configraw_config
Important normalized keys include:
core.default_providercore.default_modelcore.main_agent_idcore.subagentsruntime.routerruntime.providers
Chat and Upload
/api/chat/api/chat/history/api/chat/live/api/upload
Provider and OAuth
/api/provider/oauth/start/api/provider/oauth/complete/api/provider/oauth/import/api/provider/oauth/accounts/api/provider/models/api/provider/runtime
These are mainly used for:
- browser-driven OAuth login
- importing existing auth JSON
- querying provider model lists
- inspecting provider runtime health, cooldown state, and candidate ordering
Runtime Resources
/api/sessions/api/memory/api/workspace_file/api/tool_allowlist_groups/api/tools/api/mcp/install/api/cron/api/skills
Logs and Channel Helpers
/api/logs/recent/api/logs/live/api/whatsapp/status/api/whatsapp/logout/api/whatsapp/qr.svg
status As An Operational Check
clawgo status reads runtime-facing artifacts rather than only echoing config.
The most useful lines now include:
- active provider
Provider API BaseProvider API Key- heartbeat / cron state
- skill execution stats
- session stats
That makes it much closer to the real runtime state than looking at one static provider slot in config.
Sentinel
Sentinel is initialized at Gateway startup and uses:
enabledinterval_secauto_healnotify_channelnotify_chat_id
Logs
Default log path:
~/.clawgo/logs/clawgo.logThe default log endpoints are:
/api/logs/recent/api/logs/live
not the older /api/logs/stream name from previous docs.
Hot Reload and Rollback
clawgo config set currently:
- updates config
- writes atomically
- keeps a backup
- attempts Gateway reload
- rolls back if reload fails while Gateway is running
Service Deployment
clawgo gateway supports:
startstoprestartstatus
Running:
clawgo gatewayattempts to register the gateway service for the current platform. For foreground debugging, prefer:
clawgo gateway run