OpenClaw 4.14: agents add Writes Wrong baseUrls — New Agents Silent-Fail Instantly

If you created a new agent on OpenClaw 2026.4.14 and it immediately returns "Agent couldn't generate a response" with no actual model activity — the bug is in models.json. The openclaw agents add command writes incorrect baseUrl values for several providers, causing every outbound LLM call to 404 silently. GitHub issue #67295.

What's Broken

When openclaw agents add creates a new agent on 4.14, it writes a per-agent models.json with wrong baseUrl values. The result: every outbound LLM call returns stopReason=stop, payloads=0 instantly — no HTTP request is actually reaching the provider. The agent runtime treats the 404 as an empty turn.

Affected providers and the specific URL errors:

The pattern: 4.14 is appending /v1 to providers that don't want it on their base URL, or missing /api where it's required. DeepSeek is unaffected because its correct URL already includes /v1.

How to Confirm This Is Your Problem

Check your new agent's models.json:

cat ~/.openclaw/agents/<your-agent-name>/agent/models.json

If you see https://openrouter.ai/v1 instead of https://openrouter.ai/api/v1 (or the other wrong URLs from the table above), this is your issue.

You can also test directly — curl the correct URL with your API key to confirm it works, then curl the broken URL to confirm it 404s:

# Should work (correct URL)
curl -sS https://openrouter.ai/api/v1/chat/completions \
  -H "Authorization: Bearer $OPENROUTER_API_KEY" \
  -d '{"model":"anthropic/claude-sonnet-4.6","messages":[{"role":"user","content":"hi"}]}'

# Will 404 (broken URL that 4.14 writes)
curl -sS https://openrouter.ai/v1/chat/completions \
  -H "Authorization: Bearer $OPENROUTER_API_KEY" \
  -d '{"model":"anthropic/claude-sonnet-4.6","messages":[{"role":"user","content":"hi"}]}'

The Fix: Edit models.json Manually

Open your agent's models.json and correct the baseUrl values:

~/.openclaw/agents/<agent-name>/agent/models.json

Find and replace the wrong URLs:

• https://openrouter.ai/v1 → https://openrouter.ai/api/v1
• https://chatgpt.com/backend-api/v1 → https://chatgpt.com/backend-api
• https://api.individual.githubcopilot.com/v1 → https://api.individual.githubcopilot.com

Restart the gateway after editing:

openclaw gateway restart

Workaround: Copy models.json from a Working Agent

If you have an older working agent (created before 4.14), you can copy its models.json to your new agent and adjust as needed:

cp ~/.openclaw/agents/<old-working-agent>/agent/models.json \
   ~/.openclaw/agents/<new-broken-agent>/agent/models.json

The issue report confirms older agents created with the same command still work correctly — the bug is only in newly-created agents on 4.14.

Does This Affect Existing Agents?

No. Only agents created with openclaw agents add on 4.14 are affected. Existing agents that were working before the 4.14 update will continue to work — their models.json has the correct values.

Status

GitHub issue #67295 filed April 15, currently open. Given that this completely breaks new agent creation for several major providers simultaneously, expect a quick patch. Watch for 2026.4.15.