Fix OpenClaw Chat Completions Issues in BenAgent
Troubleshoot OpenClaw gateway setup for BenAgent, including missing Chat Completions endpoints, unexpected auth requirements, silent replies, and local-history continuity.
OpenClaw integration problems usually look like normal HTTP errors, but the fix is often in the gateway configuration. BenAgent expects OpenClaw to expose an OpenAI-compatible Chat Completions endpoint on the configured base URL.
The expected route
- Base URL: http://127.0.0.1:18789
- Endpoint path: /v1/chat/completions
- Model sent by BenAgent: openclaw/default
- Authorization: none for trusted loopback, or an optional OpenClaw Bearer token matching gateway.auth.token
- Continuity: bounded local history inside exactly one user message
404 on /v1/chat/completions
A 404 on the default path usually means the OpenAI-compatible Chat Completions endpoint is disabled, not that BenAgent chose the wrong URL. Enable the gateway Chat Completions option, restart OpenClaw, then test again.
401 or unauthorized
A 401 means OpenClaw and BenAgent disagree on endpoint authentication. Re-check gateway.auth.token and the optional OpenClaw Bearer token saved in BenAgent, or keep both unset for loopback-only no-auth access.
Silent replies
BenAgent expects a visible answer. If OpenClaw returns a silent placeholder or empty content, BenAgent treats that as a runtime problem. Fix the OpenClaw prompt/model/tool path so the latest user message produces a concise visible reply.
Context weirdness
BenAgent keeps OpenClaw continuity by embedding completed local history in the one user message. If you change provider settings while OpenClaw is still replying, you can confuse the test path. Wait for the request to finish, then reset the local conversation intentionally.
Debug in this order
Check the gateway
Confirm OpenClaw is running and the configured port matches BenAgent.
openclaw gateway statusCheck the endpoint
Confirm Chat Completions is enabled before changing BenAgent settings.
Check endpoint authentication
Send the equivalent request with the same no-auth or Bearer-token mode and confirm the exact configured route accepts it.
Check the reply
Use a one-sentence test prompt before debugging tools, cron jobs, or long workflows.
References
Ready to bring agent-first work to your Mac?
Install BenAgent, connect Hermes or OpenClaw, verify the endpoint and its access boundary, then delegate one safe result you can review before relying on longer work.