openclaw - 💡(How to fix) Fix opencode-go/deepseek-v4-flash tool schema failure and Telegram planning text leak after fallback [2 comments, 3 participants]

Summary

Using opencode-go/deepseek-v4-flash in Telegram fails on tool-enabled requests with a provider schema error, and the fallback path can expose internal planning text in the visible reply.

OpenClaw Version

• 2026.4.21

Environment

• Channel: Telegram direct chat
• Provider/model: opencode-go/deepseek-v4-flash
• Fallback model observed: Fireworks / Kimi

Problem 1: DeepSeek Go tool payload is rejected

When the model is selected for normal chat with tools enabled, the provider rejects the request with:

400 invalid_request_error
Error from provider (DeepSeek): Failed to deserialize the JSON body into the target type: tools[0].function: missing field `name`

OpenClaw logs this as a provider schema / format failure and falls back.

Problem 2: Fallback can leak internal planning text into Telegram replies

After the DeepSeek failure, OpenClaw falls back to another model. In some fallback replies, internal planning/reasoning text becomes part of the visible assistant message sent to Telegram, for example:

The user keeps sending test. They might be checking if I'm still responsive or testing something. I should just acknowledge briefly.i'm here.

That text should never be shown to the end user.

Expected

• DeepSeek Go requests should be serialized in a provider-compatible tool schema.
• If fallback occurs, internal planning / reasoning text should remain hidden from the user.
• Telegram should only receive the final assistant text.

Actual

• opencode-go/deepseek-v4-flash fails with a 400 schema error on tool-enabled requests.
• OpenClaw falls back successfully.
• In some runs, fallback output includes internal planning text in the user-visible Telegram message.

Repro

1. Set primary model to opencode-go/deepseek-v4-flash
2. Use Telegram direct chat
3. Send a simple message like test
4. Observe:
   • DeepSeek request fails with tools[0].function: missing field 'name'
   • OpenClaw falls back
   • Visible Telegram reply may include planning text

Evidence

Relevant log excerpts observed locally:

• provider failure:
  • LLM request failed: provider rejected the request schema or tool payload.
  • Error from provider (DeepSeek): Failed to deserialize the JSON body into the target type: tools[0].function: missing field 'name'
• fallback decision:
  • candidate failed for opencode-go/deepseek-v4-flash
  • next candidate succeeded on Fireworks / Kimi
• leaked visible reply contained internal planning text instead of only final user-facing output

I can provide sanitized session/log snippets if needed, but the core failure is reproducible from the setup above.