QUICK ANSWER
OpenClaw 2026.6.1 (currently in beta) adds MiniMax M3 as a supported provider (1M context, multimodal, strong coding/agent skills), a Skill Workshop for governed agent skill creation with review and approval workflows, SQLite-backed state for reliable restarts, and native Windows Execution Container support. To configure MiniMax M3: run openclaw models set minimax/MiniMax-M3 after setting your MINIMAX_API_KEY.
What OpenClaw Is - For Readers Who Are New to It
OpenClaw is a self-hosted agent runtime and message router - "your own personal AI assistant, any OS, any platform, the lobster way." You run it on your own machine (macOS, Windows, or Linux) and it connects AI models to tools, workflows, and chat applications like WhatsApp, Telegram, iMessage, and Slack. Rather than paying a SaaS platform to own your conversation history and workflow logic, OpenClaw puts the orchestration layer on your own hardware using whatever AI model you choose.
The positioning is direct: OpenClaw Cloud starts at $59/month, a self-hosted VPS setup runs around $13/month, and traditional human assistants cost $3,000+/month for comparable coverage. The platform has scaled to hundreds of thousands of users, and recent releases have shifted from feature velocity toward reliability, audit trails, and governance - the hallmarks of a platform graduating from enthusiast use to production deployment.
MiniMax M3 Integration - What It Adds and How to Configure It
The headline feature of 2026.6.1 is MiniMax M3 provider support (PR #88860). MiniMax M3 was released on OpenRouter on May 31, 2026 and became generally available via MiniMax's own API on June 1. Its core strengths align with what OpenClaw agents need most: a 1M-token context window via MiniMax Sparse Attention, native multimodal input (text, image, and video in a single context), strong coding performance, and reliable agentic tool calling.
How to configure MiniMax M3 in OpenClaw
Option 1: API key (direct)
export MINIMAX_API_KEY=your_key_here
openclaw models set minimax/MiniMax-M3
Option 2: OAuth portal
openclaw configure
# Select MiniMax auth option
openclaw models set minimax-portal/MiniMax-M3
Verify setup
openclaw models list
# Should show minimax/MiniMax-M3 as available
Two provider IDs are available depending on your auth method. API-key setups use minimax/MiniMax-M3. OAuth portal setups (MiniMax's web-based auth) use minimax-portal/MiniMax-M3. If you see an error about MiniMax provider not configured, the fix is in 2026.1.12+ - upgrade first, then run openclaw configure and select a MiniMax auth option. The 2026.6.1 release also adds MiniMax M3 pricing metadata and PDF defaults to the provider catalog, so the model should surface automatically in model selection UIs after the upgrade.
Skill Workshop - Governed Agent Skill Creation
Skill Workshop is the most architecturally significant change in the 2026.6.1 release. Before this release, agent skills in OpenClaw were created and deployed without a formal review layer - an agent could propose a new skill and it would go into production without a human approving it. For personal use that is fine; for teams or any deployment touching real external channels (customer messages, file systems, credentials), it is a meaningful risk.
Skill Workshop adds a full approval pipeline for agent-created skills:
Proposal queue
Agent-created skills enter a pending proposal state rather than going live immediately. A list of pending proposals is visible in the Gateway and CLI.
Review and approval
Proposals can be reviewed, approved, rejected, or sent back for revision. The review shows the full skill definition, the agent's stated rationale, and any support files. Approval policy can be configured - auto-approve for low-risk skill categories, manual review for anything touching credentials or external APIs.
Scanner checks and quarantine
Support files attached to skills are hashed and scanned before approval. Skills that fail scanner checks go to quarantine with a clear reason logged. Rollback metadata is stored so any approved skill can be reverted to a prior version.
Control UI screens
Skill Workshop adds dedicated Control UI screens for the full proposal lifecycle - visible in the ClawHub interface. The skills runtime loading, status, filtering, and prompt formatting are all centralized in a new core skills index.
The OpenClaw 2026.5.31 update tracker described this direction well: "The next useful agent platform feature is not another prompt trick; it is change control." Skill Workshop is the materialization of that insight - governed skill edits, inspectable workboards, durable state, and explicit recovery paths are what separate a toy automation from a system you can deploy in a business context.
Windows Execution Containers - What Changed and What It Means
OpenClaw has technically supported Windows for some time, but execution of agent tasks on Windows required workarounds - typically running through WSL (Windows Subsystem for Linux) rather than native Windows processes. The 2026.6.1 work on Windows Execution Containers moves toward running agent workloads natively inside Windows containerized environments, eliminating the WSL dependency for most use cases.
The timing alongside Microsoft Build 2026 is deliberate. Build 2026 shipped Windows Agent Framework 1.0 - the OS-level API layer that allows AI agents to integrate with the Windows shell, task scheduler, and security model as registered system services. OpenClaw's Windows Execution Container work positions it to leverage Windows Agent Framework as a deployment target - meaning OpenClaw agents could eventually be registered as Windows Agent Framework services, appearing in the Windows task bar with managed permissions and Intune governance. That deeper integration is forward roadmap; the 2026.6.1 release delivers the foundational container work that makes it possible.
SQLite State Migration - Why It Matters for Reliability
Multiple subsystems have moved from filesystem-based state to SQLite-backed storage in 2026.6.1: plugin install ledgers, inbound channel queues (PRs #88794, #88797), iMessage monitor state, ACP metadata, session metadata, memory writes, and cron migrations. This might read as internal plumbing, but the practical impact is significant: SQLite-backed state survives restarts without duplicate filesystem scanning, recovers from crashes without losing queue positions, and provides transactional guarantees that raw filesystem operations cannot.
For users running OpenClaw as an always-on agent server - monitoring channels, executing scheduled tasks, handling inbound messages - the filesystem state model meant restarts could lose queue position or re-process already-handled messages. SQLite-backed queues and monitor state eliminate that class of reliability issue. If you run OpenClaw on a VPS or homelab server that restarts occasionally, this upgrade is worth applying for the reliability improvement alone.
Full Changelog Summary - 2026.6.1 Beta
| Area |
Change |
PR |
| Providers |
Add MiniMax M3 model support, pricing, PDF defaults |
#88860 |
| Providers |
MiniMax M3/account OAuth endpoints; Google/Vertex catalog fixes; OpenRouter SQLite model caching; Copilot Claude 1M capabilities; Foundry reasoning alignment; OpenAI response replay guards |
#88480, #88512, #88851 |
| Skills |
Add core skills index; centralize runtime loading, status, filtering, prompt formatting; Skill Workshop guide added to docs |
Multiple |
| State / Channels |
Store inbound queues in SQLite; migrate iMessage monitor state to SQLite-backed tracking |
#88794, #88797 |
| Doctor / Diagnostics |
Add disk space health checks; stabilize post-upgrade JSON probes |
Multiple |
| CI / Release |
Cap logs, response bodies, readiness probes, artifact checks, status polling, rollback snapshots for bounded failure reporting |
#88966 |
| Agents / TUI |
Keep local custom provider runs from loading plugin runtime and auth alias metadata when plugins are disabled |
Multiple |
How to Upgrade
Upgrade OpenClaw to 2026.6.1 beta
npm (beta channel)
npm install -g openclaw@beta
From source
git pull origin main
npm install
npm run build
Docker
docker pull openclaw/openclaw:beta
docker compose pull && docker compose up -d
Note: 2026.6.1 is currently in beta (beta.1 and beta.2 released, stable not yet tagged on npm). The npm stable channel remains on 2026.5.28. If you are running a production setup and cannot tolerate beta instability, wait for the stable tag. If you are comfortable with beta software, the MiniMax M3 and Skill Workshop additions are worth upgrading for now.
Frequently Asked Questions
What is MiniMax M3 and why does it matter for OpenClaw?
MiniMax M3 is a frontier model from Chinese AI lab MiniMax, released May 31-June 1, 2026. Its key capabilities for OpenClaw use: 1M-token context window via MiniMax Sparse Attention (useful for long-running agent sessions), native multimodal input (text, image, video in one context), strong coding performance, and reliable tool calling for agentic workflows. It is available via API key or OAuth portal, and as of 2026.6.1 it is fully integrated into OpenClaw's provider catalog.
Is 2026.6.1 stable enough for production use?
Currently no - 2026.6.1 is in beta (beta.1 and beta.2 are tagged, stable has not shipped). The npm stable channel is still on 2026.5.28. If you are running OpenClaw for personal use and are comfortable with beta software, upgrading is reasonable. For production deployments handling customer-facing workflows or sensitive data, wait for the stable release.
How does OpenClaw compare to n8n or Zapier for agent automation?
OpenClaw is closer to a self-hosted AI agent runtime than a workflow automation tool. n8n and Zapier are designed for connecting services with defined triggers and actions; OpenClaw is designed for conversational and autonomous agent workflows that connect to chat channels (WhatsApp, Telegram, iMessage) and use AI models for reasoning and planning. OpenClaw gives you more flexibility and model choice; n8n and Zapier give you more pre-built connectors and a lower setup barrier for non-developers.
What is Workboard in OpenClaw?
Workboard is OpenClaw's Kanban-style coordination view for managing tasks across multiple agents. It provides a visual overview of agent task states - queued, in progress, blocked, completed - across all running agents in a session. It is separate from Skill Workshop (which governs skill creation) and provides operational visibility into what agents are doing at any given moment.