OpenClaw expands model support
OpenClaw (now OpenAI‑owned) added model‑agnostic support for Claude Code and Cursor MCP, plus Exa search and Chrome integration — widening options for developers to plug different agent engines into the same stack. That makes OpenClaw a stronger neutral layer for mixed‑model agent setups. (x.com)
A community-maintained skill called "openclaw-claude-code-skill" exposes Claude Code to OpenClaw via the Model Context Protocol (MCP) and advertises persistent sessions, effort control, context management, model switching, and agent-team features for OpenClaw agents (github.com). Exa’s MCP server listing shows developers can route OpenClaw and other MCP clients — Claude Desktop, Cursor, and VS Code — to Exa’s web search, code search and research APIs to give agents live search and retrieval capabilities (exa.ai). OpenClaw’s official docs describe “bundles” that map external ecosystems (Codex, Claude, Cursor) into native OpenClaw skills and hooks, normalizing those providers so a single OpenClaw stack can treat different model ecosystems uniformly (docs.openclaw.ai). A GitHub issue (openclaw/openclaw #4494) captured a proposed bidirectional Cursor MCP integration — letting Cursor models appear as OpenClaw providers and vice versa — and that proposal was tracked and ultimately closed as “not planned.” (github.com). Third-party walkthroughs note Claude Code can auto-generate OpenClaw configuration files in minutes but does not handle agent deployment or runtime orchestration, so the integration primarily speeds config authoring rather than replacing OpenClaw’s runtime stack (betterclaw.io). OpenAI’s move to bring OpenClaw creator Peter Steinberger into the company was announced in mid‑February 2026, with Steinberger joining OpenAI and OpenClaw slated to transition to an independent foundation under OpenAI sponsorship ( ).
