Remote OpenClaw

Remote OpenClaw Blog

OpenClaw 3.24 Update: Native Teams, Slack Buttons, Sub-Agents, and More

Published: ·Last Updated:
What changed

This post was reviewed and updated to reflect current deployment, security hardening, and operations guidance.

What should operators know about OpenClaw 3.24 Update: Native Teams, Slack Buttons, Sub-Agents, and More?

Answer: OpenClaw v2026.3.24, released on March 25, 2026, is a significant update focused on enterprise messaging channels and developer experience. The release migrates Microsoft Teams to the official SDK, adds interactive Slack reply buttons, introduces Discord auto-thread naming, and improves OpenAI API compatibility for sub-agent communication. This guide covers practical deployment decisions, security controls, and operations steps to run.

Updated: · Author: Zac Frulloni

OpenClaw v2026.3.24 brings native Microsoft Teams integration, Slack interactive reply buttons, Discord auto-thread naming, improved OpenAI API for sub-agents, and a redesigned skills management UI. Full changelog and upgrade guide.

Marketplace

Free skills and AI personas for OpenClaw — deploy a pre-built agent in 15 minutes.

Browse the Marketplace →

Join the Community

Join 500+ OpenClaw operators sharing deployment guides, security configs, and workflow automations.

What Are the Headline Features in 3.24?

OpenClaw v2026.3.24, released on March 25, 2026, is a significant update focused on enterprise messaging channels and developer experience. The release migrates Microsoft Teams to the official SDK, adds interactive Slack reply buttons, introduces Discord auto-thread naming, and improves OpenAI API compatibility for sub-agent communication.

For operators running OpenClaw in production, the Teams migration is the most impactful change — it replaces the previous community integration with the official Teams SDK, bringing streaming replies, welcome cards, typing indicators, and native AI labeling.


How Does Native Microsoft Teams Work?

OpenClaw 3.24 migrates the Microsoft Teams channel from the community plugin to the official Teams SDK, bringing enterprise-grade features that make OpenClaw feel like a native Teams application.

What's new in Teams:

  • Streaming 1:1 replies — responses appear in real-time as the model generates them, not as a single block after completion.
  • Welcome cards with prompt starters — when a user first interacts with the bot, they see a card with suggested prompts.
  • Feedback and reflection — users can provide feedback on responses directly in Teams.
  • Status updates and typing indicators — the bot shows "typing..." while processing, like a human colleague.
  • Native AI labeling — Teams displays the message as coming from an AI, maintaining transparency.
  • Message edit and delete — the bot can edit or delete its own sent messages, including in-thread fallbacks.

If you're currently using Teams with OpenClaw, you'll need to reconfigure after updating. The setup flow has changed with the SDK migration. See our Teams setup guide for the updated process.


What Are Slack Interactive Reply Buttons?

OpenClaw 3.24 adds automatic interactive buttons to Slack replies. When the agent's response ends with an Options: line, Slack renders those options as clickable buttons instead of plain text.

For example, if the agent responds with:

Here are your options for the meeting:
Options: Reschedule | Cancel | Confirm | Ask for agenda

Slack will display four clickable buttons. The user clicks one, and OpenClaw receives it as a new message — no typing required.

This works automatically with no configuration. The system also restores rich reply parity for direct deliveries and isolates reply controls from plugin handlers.


How Does Discord Auto-Thread Naming Work?

Discord servers using OpenClaw can now enable LLM-generated thread names. When a user starts a conversation, instead of the default message-based thread title, the agent generates a descriptive title asynchronously.

Enable it with:

{
  "autoThreadName": "generated"
}

The default behavior (message-based naming) is preserved. Thread titles are generated in the background, so there's no delay in the user's first response.

Marketplace

4 AI personas and 7 free skills — browse the marketplace.

Browse Marketplace →

What Changed in the OpenAI API?

OpenClaw 3.24 adds /v1/models and /v1/embeddings endpoints to the OpenAI-compatible API layer, and forwards explicit model overrides through /v1/chat/completions and /v1/responses.

The practical benefit: you can now use OpenClaw as a backend for OpenWebUI and other OpenAI-compatible clients to communicate with sub-agents. This opens up multi-agent architectures where a primary agent delegates tasks to specialised sub-agents running on the same gateway.


What's New in Skills Management?

The skills management interface in the Control UI has been completely redesigned:

  • Status filter tabs — quickly filter by All, Ready, Needs Setup, or Disabled.
  • Click-to-detail dialogs — instead of inline cards, each skill opens a detail panel showing requirements, toggles, install actions, API key entry, source metadata, and homepage links.
  • "Available Right Now" section — the /tools endpoint now shows tools available to the current agent in a live dashboard.
  • One-click install recipes — bundled skills (coding-agent, gh-issues, openai-whisper-api, session-logs, tmux, trello, weather) now include CLI and Control UI install buttons.
  • Softened labeling — "missing" changed to "needs setup" with specific API key guidance.

What Bugs Were Fixed?

OpenClaw 3.24 addresses over 15 bugs, many of which affected production deployments:

WhatsApp Fixes

  • Group echo suppression — outbound messages in groups no longer echo back as inbound. The system now tracks recent gateway-sent message IDs and filters them.
  • Reply-to-bot detection — restored implicit group reply detection by unwrapping botInvokeMessage payloads.

Telegram Fixes

  • Forum topic routing — recovered #General topic routing when Telegram omits forum metadata.
  • Photo dimension checking — preflights photo dimensions and falls back to document sends when invalid.
  • 403 error handling — preserves actionable membership/block/kick details.

Discord Fixes

  • Gateway crash prevention — centralized error handling behind lifetime-owned supervisor.
  • Timeout replies — sends visible timeout message when the worker times out before a response.

Infrastructure Fixes

  • Docker fresh install — fixed setup-time write loop that broke fresh Docker installations.
  • Gateway restart recovery — wakes interrupted agent sessions via heartbeat after restart instead of best-effort notes.
  • Channel boot isolation — one broken channel no longer blocks other channels from starting.
  • Security sandbox fix — closed mediaUrl/fileUrl alias bypass that could escape media-root restrictions.

How Do You Update to 3.24?

Docker (most common):

cd ~/openclaw
docker compose pull
docker compose up -d

npm:

npm update -g openclaw

New in 3.24: The openclaw update command now preflights the target npm package's engines.node requirement before installation. If your Node.js is outdated, it tells you to upgrade instead of attempting a broken install. Minimum supported: Node 22.14+.

Docker container CLI: New --container flag lets you run CLI commands inside your Docker or Podman container:

openclaw --container skills list

Remote OpenClaw managed clients: We handle updates for you. Your agent will be updated during the next maintenance window with zero downtime.


Recent Version History

VersionDateHighlights
3.24Mar 25Native Teams, Slack buttons, Discord auto-threads, OpenAI API sub-agents
3.23Mar 23Qwen API, DashScope, CSP fixes, plugin runtime restoration
3.22Mar 23ClawHub integration, Matrix plugin, Vertex AI, breaking env var changes
3.13Mar 14Recovery release — compaction, Telegram threading, Discord gateway

For the complete changelog of all versions, see our OpenClaw Changelog.