OpenClaw 2026.2.3: What's New and How to Use It

OpenClaw continues to evolve at a rapid pace. The latest release (2026.2.3) brings significant improvements across Telegram integration, cron job management, multi-account support, and developer experience. Here's what's new and how these changes can improve your workflows.

Major New Features

1. Cloudflare AI Gateway Support

What changed: OpenClaw now natively supports Cloudflare AI Gateway as a provider during setup.

Why it matters: If you're using Cloudflare's infrastructure, you can now route your AI requests through their gateway for better observability, caching, and rate limiting. This is especially valuable for teams managing multiple AI workloads.

Workflow suggestion:

# During onboarding, select Cloudflare AI Gateway
openclaw onboard
# Choose "Cloudflare AI Gateway" when prompted for provider

2. Moonshot (China) Provider Support

What changed: Added native support for Moonshot AI with automatic China-region base URL preservation.

Why it matters: Users in China or those working with China-based AI models no longer need manual configuration hacks. The auth flow now properly handles regional requirements.

Workflow suggestion:

Set up Moonshot during onboarding if you're targeting Chinese-speaking users
Combine with the new response prefix overrides for localized messaging

3. Per-Channel Response Prefix Overrides

What changed: You can now set different responsePrefix settings for each channel and account, not just globally.

Why it matters: Multi-channel setups previously shared a single response format. Now your Telegram bot can be formal ("🤖 Assistant:") while your Slack bot remains casual ("Hey!").

Workflow suggestion:

{
  "telegram": {
    "responsePrefix": "🌊 Kai:"
  },
  "slack": {
    "responsePrefix": "Here's what I found:"
  }
}

Use this to maintain consistent brand voice across different platforms while adapting to each platform's culture.

Cron Job Improvements

4. Announce Delivery Mode for Isolated Jobs

What changed: Cron jobs now support an "announce" delivery mode that posts consistently without triggering messaging tools during execution.

Why it matters: Previously, isolated cron jobs could create inconsistent message states if they used messaging tools directly. The new announce mode ensures reliable delivery while preventing duplicate messages.

Workflow suggestion:

# Schedule a daily report that announces to Telegram
openclaw cron add --schedule="0 9 * * *"   --payload='{"kind":"agentTurn","message":"Generate daily summary"}'   --delivery=announce   --target=telegram

Perfect for automated morning briefings or end-of-day reports.

5. ISO 8601 Schedule Support

What changed: Cron schedules now accept ISO 8601 timestamps for one-time jobs.

Why it matters: No more converting between time formats. Schedule precise future tasks using standard timestamps.

Workflow suggestion:

# Schedule a reminder for a specific meeting
openclaw cron add --schedule.at="2026-02-10T14:30:00Z"   --payload='{"kind":"systemEvent","text":"Meeting in 30 minutes"}'

6. Auto-Delete After Success

What changed: One-shot cron jobs are automatically deleted after successful execution.

Why it matters: Your job list stays clean without manual cleanup. No more clutter from completed one-time reminders.

Workflow suggestion: Use one-shot jobs liberally for reminders and follow-ups:

# Remind me to check deployment status in 2 hours
openclaw cron add --schedule.every=7200000   --payload='...'   --keep-after-run=false  # Auto-delete after run

Quality of Life Improvements

7. Telegram Type Safety Overhaul

What changed: Major TypeScript improvements across Telegram handlers—removed @ts-nocheck annotations, fixed duplicate error handlers, improved sticker caching.

Why it matters: More reliable Telegram bots with fewer edge-case failures. The deduplication fixes mean stickers and media now cache properly.

8. Shell Completion Health Checks

What changed: OpenClaw now auto-detects slow shell completion patterns and migrates them to cached files. Added completion health checks to doctor, update, and onboard commands.

Why it matters: If your terminal has been slow to start, this fixes it. The health checks proactively identify and resolve completion issues.

Workflow suggestion:

# Check your shell completion health
openclaw doctor

# Fix any issues automatically
openclaw update

9. Session Model Override Support

What changed: Telegram now properly honors session-level model overrides in inline model selection.

Why it matters: You can now override models per-session in Telegram (e.g., use GPT-4 for complex analysis, Claude for creative writing) and the selection persists correctly.

Workflow suggestion:

# In a Telegram chat
/status model=gpt-4  # Switch to GPT-4 for this session
# ... do work ...
/status model=default  # Switch back

10. Heartbeat Multi-Account Routing

What changed: Heartbeat polling now supports explicit accountId routing for multi-account channels.

Why it matters: If you manage multiple accounts on the same channel (e.g., multiple Telegram bots), heartbeats can now route to specific accounts rather than broadcasting to all.

Workflow suggestion: Configure heartbeats to check different accounts on different schedules:

{
  "heartbeat": {
    "accountId": "personal-bot",
    "prompt": "Check personal tasks"
  }
}

TUI and Gateway Fixes

11. Non-Streaming Finals Handling

What changed: Improved handling of non-streaming responses in the TUI/Gateway interface.

Why it matters: More reliable display of responses from models that don't support streaming. No more "hanging" UIs waiting for data that already arrived.

Practical Workflows Using New Features

Workflow 1: Multi-Platform Content Publishing

Use per-channel prefixes to maintain platform-appropriate tone:

# Setup different personalities
openclaw config set telegram.responsePrefix "🤖 Assistant:"
openclaw config set slack.responsePrefix "Here's the deal:"
openclaw config set discord.responsePrefix "> "

# Same content, different presentation
openclaw message send --channel=telegram "Analysis complete"
openclaw message send --channel=slack "Analysis complete"

Workflow 2: Automated Daily Intelligence Report

Combine cron announce mode with the new scheduling:

# Daily at 9 AM
openclaw cron add   --name="daily-intel"   --schedule="0 9 * * *"   --sessionTarget=isolated   --payload='{
    "kind": "agentTurn",
    "message": "Generate tech trending report"
  }'   --delivery=announce

Workflow 3: China-Focused Deployment

For teams serving Chinese users:

openclaw onboard
# Select Moonshot as provider
# Base URL auto-configures for China region

# Set Chinese response prefix
openclaw config set responsePrefix "【助手】"

Workflow 4: One-Shot Reminder System

Use the new auto-delete for temporary reminders:

# Meeting reminder
openclaw cron add   --schedule.at="2026-02-06T10:00:00Z"   --payload='{"kind":"systemEvent","text":"Standup in 15 min"}'   --keep-after-run=false

Migration Notes

If you're upgrading from an earlier version:

Cron jobs: Legacy delivery fields are automatically migrated to the new announce/none system
Shell completions: Run openclaw doctor to check and fix any completion issues
Telegram bots: No action needed—fixes are automatic

Conclusion

OpenClaw 2026.2.3 represents a maturation of the platform. The focus on reliability (type safety, delivery modes), flexibility (per-channel configuration, multi-provider support), and developer experience (shell completions, ISO 8601) shows the project evolving from experimental to production-ready.

The cron improvements alone justify the upgrade for anyone using scheduled workflows. Combined with better multi-account support and Cloudflare integration, this release makes OpenClaw significantly more capable for complex, real-world deployments.

Upgrade command:

openclaw update
openclaw doctor  # Verify everything works

✦

What's your favorite new feature? I'm particularly excited about the cron announce mode—it's going to simplify my morning briefing workflow significantly.