Skip to content

v0.1.0 — Developer Preview

Latest
Latest

Choose a tag to compare

View all tags
@lezama lezama released this 16 May 21:45
· 55 commits to main since this release
v0.1.0
7d24c97

First tagged release of openclaWP.

An agent that lives inside your WordPress site. Chat block, REST chat surface, deterministic workflows, per-turn cost dashboard, per-agent MCP server endpoint, WhatsApp Cloud API channel — all built on Automattic/agents-api and the WordPress 7.0 AI Client / Connectors API.

🎬 Try it in 60 seconds (no install, no API key)

Open in WordPress Playground →

The bundled demo runs entirely in your browser — the agent calls real WordPress abilities (openclawp/get-recent-posts, count-comments, get-active-plugins, get-current-user) under a canned-response runner. Swap in any WordPress AI Provider connector afterward and you're talking to a real model.

What's in v0.1.0

  • Chat block (wp:openclawp/chat) — Drop the agent UI into any post, page, template, or wp-admin screen.
  • openclawp/chat + canonical agents/chat abilities — Callable from MCP servers, Studio Code skills, WP-CLI, other plugins. No HTTP needed.
  • REST endpoints — POST /openclawp/v1/chat for browser UIs, GET /openclawp/v1/chat/{session} for transcripts.
  • Multi-turn sessions — Each conversation is a CPT (openclawp_session); history follows the user across requests.
  • Tool use — Agents can call read-only abilities via the WordPress Abilities API. Bundled example agent ships four: recent posts, comment counts, active plugins, current user.
  • Workflows — Compose agents and abilities into deterministic recipes with ${inputs.x} / ${steps.y.output.z} bindings. CPT-backed Store + Run Recorder; wp-admin → openclaWP → Workflows lists registered workflows, has a Run now form per workflow, and a recent-runs list with per-step trace.
  • Per-turn cost dashboard — wp-admin → openclaWP → Usage. CPT-backed (openclawp_usage) with daily, per-model, and recent-turn breakdowns. Filterable pricing table.
  • Per-agent MCP server — wp-admin → openclaWP → MCP Servers. Each registered agent gets its own JSON-RPC endpoint at /openclawp/v1/mcp/{slug} scoped to that agent's tool surface. Bearer-token auth (hashed with wp_hash_password). v1 supports initialize, tools/list, tools/call.
  • Channels admin — wp-admin → openclaWP → Channels.
  • Connector: WhatsApp Cloud API — Meta's official Graph API. Off by default.
  • wp openclawp doctor — Install-health diagnostics from the shell.

Requirements

Install

# In any WordPress 7.0+ site's plugins directory:
git clone https://github.com/Automattic/agents-api.git
git clone https://github.com/lezama/openclawp.git
( cd openclawp && composer install --no-dev )
wp plugin activate agents-api openclawp

Studio + Ollama runbook in the README.

Status

Developer preview. Use on local, staging, or sandbox sites. wp.org plugin directory submission is gated on WordPress 7.0 final shipping (May 20, 2026).

How it compares vs other WP AI agent plugins

Honest comparison matrix in the README — covers sd-ai-agent, ClawWP, AI Engine, AI Services, and WordPress/ai across substrate, provider model, MCP server, MCP client, workflows, cost dashboard, Playground demo, chat block, and concrete channels.

License

GPL-2.0-or-later.

Assets 2
Loading