Guide

OpenClaw v2026.3.24: OpenAI compatibility, upgrade notes

March 25, 20264 min readUpdated September 11, 2026By OpenClawBlog Team

v2026.3.24 arrived on 2026-03-25 with a change that matters during maintenance: openai compatibility. The page is a researched reading note from the official release record, with a test path for a real Gateway.

The tag is stable, but the direct notes still define its migrations, corrections, and package-specific limits. Support still depends on the provider, channel, platform, and account behind the installation, so check those boundaries before extrapolating from the tag.

Channel
Stable

Primary signals
Gateway/OpenAI compatibility; Agents/tools; Microsoft Teams

Publication date
2026-03-25

Before the package changes

Gateway/OpenAI compatibility

Evidence from the release. add /v1/models and /v1/embeddings, and forward explicit model overrides through /v1/chat/completions and /v1/responses for broader client and RAG compatibility.

Operator reading. Check Gateway/OpenAI compatibility with a known prompt and a disposable account. Save the selected route, reasoning setting, latency, and refusal or fallback result so another operator can reproduce it.

Agents/tools

Evidence from the release. make /tools show the tools the current agent can actually use right now, add a compact default view with an optional detailed mode, and add a live "Available Right Now" section in the Control UI so it is easier to see what will work before you ask.

Operator reading. For Agents/tools, inspect state rather than only the new control. Repeat the flow after reload and reconnect, and note the session, pending action, URL, and visible error.

Microsoft Teams

Evidence from the release. migrate to the official Teams SDK and add AI-agent UX best practices including streaming 1:1 replies, welcome cards with prompt starters, feedback/reflection, informative status updates, typing indicators, and native AI labeling.

Operator reading. The operator question around Microsoft Teams is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

Outbound media/local files

Evidence from the release. align outbound media access with the configured fs policy so host-local files and inbound-media paths keep sending when workspaceOnly is off, while strict workspace-only agents remain sandboxed.

Operator reading. The useful evidence for Outbound media/local files is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.

Details behind the headline

Security/sandbox media dispatch

close the mediaUrl/fileUrl alias bypass so outbound tool and message actions cannot escape media-root restrictions.

Read Security/sandbox media dispatch as an authorization checkpoint: prove who may act, what the action can reach, and how the rejected attempt is surfaced to the operator.

Test this release without widening the boundary

Note the current version, host, provider, and workspace before exercising Gateway/OpenAI compatibility.
Keep a tested backup beside the release record if the update can touch configuration, sessions, or a database.
Send one harmless message through the named account and save the account, thread, and sender identifiers.
Compare the transcript before and after reconnect, including delivery state and any visible error.
Stop if the observed behavior falls outside the official note, and link the log or screenshot to the version record.

openclaw --version
openclaw gateway status
openclaw security audit

Record what the release actually changed

Keep the version, source URL, test identity, and rollback decision together. If this tag is pre-release, leave it isolated; if it is stable, record the migration and rollback result before reconnecting every channel.

Corrections worth replaying

Outbound media/local files. align outbound media access with the configured fs policy so host-local files and inbound-media paths keep sending when workspaceOnly is off, while strict workspace-only agents remain sandboxed. Keep the reproduction and the post-fix result together in the acceptance record.

Security/sandbox media dispatch. close the mediaUrl/fileUrl alias bypass so outbound tool and message actions cannot escape media-root restrictions. Record the failure that this correction addresses before declaring the upgrade complete.

Use the complete OpenClaw v2026.3.24 release notes for the exact change list, then cross-check the official release index and the model provider reference before acting.