Bug: /v1/chat/completions endpoint disabled by default — tool calls silently fail

[juliosuas]

Bug Report: OpenClaw HTTP Endpoint Disabled

Description

VisionClaw's OpenClawBridge sends all Gemini tool calls to:

POST http://{openClawHost}:{openClawPort}/v1/chat/completions

However, the OpenClaw gateway has this endpoint disabled by default. First-time users who follow the README setup get silent failures — every tool call returns 404 or Connection refused — with no obvious error message in the app.

Steps to Reproduce

1. Install OpenClaw with default settings
2. Configure VisionClaw with gateway host + token
3. Ask Gemini to perform any action ("Search for coffee shops", etc.)
4. Nothing happens — gateway returns 404 on /v1/chat/completions

Root Cause

OpenClaw requires explicit opt-in in ~/.openclaw/openclaw.json:

{
  "gateway": {
    "http": {
      "endpoints": {
        "chatCompletions": { "enabled": true }
      }
    }
  }
}

This critical step is not prominently documented in the VisionClaw README.

Fix

1. Add a prominent warning in the README's OpenClaw setup section:

   ⚠️ You must enable chatCompletions in openclaw.json or tool calls will fail silently.

2. Add a startup health check in OpenClawBridge that hits /health and warns the user if the endpoint returns 404.

3. Display a visible UI indicator (red dot / banner) if the gateway is unreachable.

Severity

High — blocks the core agentic functionality for all new users.

See BUGS.md in this repo for full documentation.