OpenClaw 3.24: Sub-Agents, OpenWebUI, Slack Buttons, and Teams Integration | OpenClaw DC

OpenClaw v2026.3.24 is here, released on March 25. The headline feature is sub-agent orchestration through the OpenAI-compatible API and OpenWebUI, letting you spin up specialized agents that coordinate on multi-step tasks without manual prompting. Beyond sub-agents, this release adds a skills and tool management control UI, Slack interactive reply buttons, native Microsoft Teams integration, and smart Discord auto-thread naming. If you skipped v3.23, you also pick up every fix from that cycle, including the patches for the Dashboard and WhatsApp packaging bugs that hit v3.22.

How to Upgrade

One command:

npm install -g openclaw@latest

Verify: openclaw --version should show 2026.3.24.

If you hit problems, check the troubleshooting guide. Coming from 3.13 or earlier? Read the 3.13 release notes first so you do not miss breaking changes.

Sub-Agents via OpenWebUI

This is the biggest feature in 3.24. The OpenAI-compatible API now supports a sub-agent protocol that lets a primary agent delegate tasks to specialized child agents. OpenWebUI acts as the orchestration layer, routing requests, passing context between agents, and aggregating results before returning the final output.

In practice, this means you can define a research agent, a writing agent, and a review agent in your config:

openclaw config set agents.research.model deepseek-v3
openclaw config set agents.writer.model claude-sonnet
openclaw config set agents.reviewer.model gpt-4o

When a user sends a prompt through OpenWebUI, the primary agent breaks the task into steps, dispatches each step to the right sub-agent, and assembles the final response. Each sub-agent runs with its own model, system prompt, and tool permissions. You control which agents have access to which skills, and the orchestration respects rate limits and spending caps you already have in place.

The sub-agent protocol follows the OpenAI chat completions format, so any client that speaks that API can participate. OpenWebUI provides the most complete experience with a visual pipeline editor, but you can also trigger sub-agent workflows from the REST API directly. If you already use OpenWebUI with OpenClaw, upgrading surfaces the new agent routing options automatically in the pipeline settings panel.

Skills and Tool Management Control UI

Previous versions required editing JSON config files to enable, disable, or restrict tools for each agent. Version 3.24 adds a control UI accessible from the OpenClaw dashboard at http://localhost:3000/admin/skills.

From the UI you can:

• Browse all installed skills and tools
• Toggle individual tools on or off per agent
• Set execution limits (maximum calls per conversation, cooldown periods)
• View recent tool invocation logs with input/output previews

The UI writes back to the same config file, so you can switch between the UI and CLI without conflicts. Changes take effect immediately with no restart needed.

Slack Interactive Reply Buttons

Slack responses from OpenClaw now include interactive buttons directly beneath the reply. Instead of typing follow-up commands, users can click buttons to approve an action, request a revision, escalate to a human, or dismiss the message.

Button layouts are configurable per skill. A code review skill might show “Approve,” “Request Changes,” and “Merge” buttons, while a scheduling skill might show “Confirm,” “Reschedule,” and “Cancel.” You define button sets in the skill config:

openclaw config set skills.codeReview.slackButtons '["Approve","Request Changes","Merge"]'

Clicking a button sends the label back to the agent as a new user message within the same thread. The agent processes it like any other input, so existing skill logic works without modification. Button interactions are logged in the dashboard under the Slack activity tab.

Native Microsoft Teams Integration

OpenClaw 3.24 adds first-class Microsoft Teams support. Previous versions required a third-party bridge or webhook relay. The native integration connects directly through the Microsoft Bot Framework, handling authentication, adaptive cards, and threaded conversations out of the box.

To set it up:

openclaw config set teams.appId YOUR_APP_ID
openclaw config set teams.appPassword YOUR_APP_PASSWORD
openclaw teams start

The bot appears in your Teams workspace and responds in channels or direct messages. It supports the same skills, tools, and agent configurations as every other platform integration. Adaptive card formatting is applied automatically, so code blocks, tables, and lists render correctly in the Teams client.

If you run OpenClaw behind a firewall, you need to allow outbound connections to the Microsoft Bot Framework endpoint. The troubleshooting guide has the full list of required URLs and ports.

Smart Discord Auto-Thread Naming

Discord threads created by OpenClaw used to receive generic names like “OpenClaw Response” or the first few words of the user message. Version 3.24 generates descriptive thread names by summarizing the conversation topic. A question about Docker networking becomes “Docker bridge network routing issue” instead of “hey can you help me with.”

The naming runs through a lightweight summarization call that adds negligible latency. You can disable it if you prefer the old behavior:

openclaw config set discord.autoThreadName false

v3.22 Bug Recap

Version 3.22 shipped over 30 security patches, but two packaging bugs slipped through. The first broke the Dashboard: a missing dependency caused the admin panel to crash on startup. The second broke the WhatsApp integration: an incorrect import path prevented the WhatsApp connector from loading.

Both bugs were fixed in the 3.23-2 stable release. If you are still on 3.22 or 3.23-0, skip directly to 3.24. It includes every fix from 3.23-2 plus the new features above. For the full 3.23 changelog, see the 3.23 release notes.

Should You Upgrade?

If you want multi-agent workflows: Yes. Sub-agent orchestration through OpenWebUI is a major capability that opens up complex automation pipelines.

If you use Slack: Yes. Interactive reply buttons reduce friction and make agent responses actionable without extra typing.

If your team uses Microsoft Teams: Yes. Native integration replaces fragile webhook bridges with a direct Bot Framework connection.

If you manage many skills and tools: Yes. The new control UI saves time compared to editing JSON config files by hand.

If you are on 3.22 or early 3.23: Yes. You need the packaging bug fixes from 3.23-2, and 3.24 bundles them all.

If you are on a stable 3.23-2 and do not need any of these features: You can wait, but sub-agent support alone is worth evaluating for future workflows.

Questions or Need Help Setting Up?

Book a Call. We walk through upgrades, sub-agent configuration, and Teams setup regularly with OpenClaw users.