OpenClaw v2026.4.5: 12-Language UI & New AI Providers for B2B Sales Agents

OpenClaw just shipped v2026.4.5 — and this release is a major unlock for international B2B sales teams. Between a multilingual control dashboard, four new bundled AI providers including Chinese-origin Qwen and MiniMax, a restored WhatsApp streaming fix, and a round of security hardening, there's a lot to unpack.

Here's what changed, why it matters for B2B SDR agents, and how to upgrade safely.

What's New in v2026.4.5

1. Control UI Localized in 12 Languages

The OpenClaw dashboard and mobile app are now fully localized for:

• Simplified Chinese (简体中文)
• Traditional Chinese (繁體中文)
• Brazilian Portuguese
• German
• Spanish
• Japanese
• Korean
• French
• Turkish
• Indonesian
• Polish
• Ukrainian

Why it matters for B2B: Most AI sales agent platforms require English-speaking admins. With this release, a factory owner in Shenzhen, a textile exporter in Istanbul, or a machinery supplier in Osaka can manage their entire AI SDR operation in their native language — without a translator or a tech-savvy intermediary.

This is particularly powerful combined with PulseAgent's B2B SDR template, which already supports Operator Bilingual Mode (English replies to customers, Chinese summary to owner via WhatsApp self-chat).

2. Four New Bundled AI Providers

v2026.4.5 adds four new providers to OpenClaw's built-in provider roster:

All four use the openai-completions API type, making them drop-in alternatives. Configuration is identical to Mistral or Groq:

model:
  id: "qwen-max"
  provider: "qwen"
  api: "openai-completions"

For China-based exporters: Running your SDR agent on Qwen or MiniMax can reduce latency, lower costs, and avoid the compliance friction of routing data through US-based APIs — all without changing a single line of your sales workflow logic.

Quick start: Deploy a full B2B SDR agent with Qwen backend in minutes:

curl -fsSL https://raw.githubusercontent.com/iPythoning/b2b-sdr-agent-template/main/install.sh | bash

Then set provider: qwen in your model config. Full setup guide →

3. WhatsApp blockStreaming Restored

A configuration option (blockStreaming: true) that disables token-by-token streaming on WhatsApp — sending the full reply at once instead — was inadvertently removed in a prior release. It's now back.

This matters because some WhatsApp Business accounts experience delivery issues with streaming responses (messages appearing fragmented or out of order). The fix:

channels:
  whatsapp:
    blockStreaming: true

If you've been seeing split or garbled WhatsApp replies since v2026.4.2, this is the fix. See WhatsApp sales automation guide →

4. Telegram Quality Fixes

Several Telegram issues were addressed:

• Model picker display: Non-default model confirmations now correctly render the model name in HTML-formatted messages
• DM voice-note transcription: Voice messages sent to the bot via DM are transcribed again (regression fixed)
• Reaction persistence: Emoji reactions set by the agent now survive gateway restarts
• Media file-ID preservation: File IDs cached across restarts, reducing redundant re-uploads

For SDR agents that use Telegram as a primary channel (especially Russia/CIS, Iran, Eastern Europe), these fixes add up to noticeably more reliable operations. Telegram lead generation guide →

5. Security Hardening

Several security fixes ship in this release:

• Plugin allowlists preserved: Plugin-only tool allowlists now correctly persist across restarts
• Owner-only /allowlist commands: /allowlist add and /allowlist remove now require owner access (previously any admin could modify)
• SSRF redirect blocking: Browser SSRF redirect bypasses are now blocked earlier in the request lifecycle
• Canvas bridge: Actions on the canvas bridge now require exact normalized URL matches
• Telegram file access: Bot API file reads now require trustedLocalFileRoots to be configured
• Symlink escapes: Plugin marketplace installations no longer allow symlink escape vulnerabilities

For production SDR deployments handling customer data, run openclaw doctor after upgrading to verify your security posture.

6. New Diagnostic Tools

• openclaw status --verbose: Now shows prompt cache reuse statistics explicitly — useful for debugging unexpected API costs or latency spikes
• openclaw config schema: Exports the full config JSON schema, enabling editor autocomplete and agent-assisted config generation
• openclaw plugins install --force: Replaces an existing plugin without manual removal

Breaking Changes

Action required for all users upgrading from v2026.4.2 or earlier.

v2026.4.5 removes the following legacy config aliases:

Migration is automatic. Run:

openclaw doctor --fix

Backward compatibility shims remain active during the transition period, but you'll see startup warnings until configs are migrated.

Upgrade Steps

# 1. Backup config
cp ~/.openclaw/openclaw.json ~/.openclaw/openclaw.json.bak

# 2. Install new version
npm install -g openclaw@latest

# 3. Migrate legacy configs (NEW for v2026.4.5)
openclaw doctor --fix

# 4. Refresh gateway service token
openclaw gateway install --force

# 5. Restart
openclaw gateway restart

# 6. Verify
curl -s http://localhost:18789/health
openclaw channels status

Comparison: What Changed for B2B SDR Agents

Frequently Asked Questions

Q: Do I need to change my existing config for the new providers? No. Existing configs are untouched. To use Qwen or MiniMax, add them as a new model config block and switch the active model.

Q: Will blockStreaming: true affect message delivery speed? Slightly. The full reply is buffered before sending, so customers see a small typing indicator delay. For most B2B conversations this is imperceptible, and the tradeoff (reliable delivery) is worth it.

Q: Is the multilingual UI available in the self-hosted version? Yes. The UI localization ships with the core package, not as a cloud-only feature.

Q: How do I know if my config has legacy aliases that need migrating? Run openclaw doctor — it will list any deprecated keys with suggested replacements.

Q: Does Qwen work for non-Chinese-language sales conversations? Yes. Qwen is multilingual and handles English, Arabic, Spanish, and most major languages. It's not limited to Chinese.

Get Started with PulseAgent

PulseAgent is the fastest way to deploy OpenClaw-powered B2B SDR agents — pre-configured for WhatsApp, Telegram, and email with a 7-layer context system built for B2B export sales.

One command to deploy:

curl -fsSL https://raw.githubusercontent.com/iPythoning/b2b-sdr-agent-template/main/install.sh | bash

• Sign up free →
• View pricing →
• WhatsApp Sales Automation →
• AI SDR for B2B Export →
• Telegram Lead Generation →
• Multi-Channel Sales Pipeline →
• AI Sales Agent for Manufacturing →