Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,13 @@ All notable changes to this project will be documented in this file, per [the Ke
### Added
- New Experiment: AI Workspace; a dedicated `Tools → AI Workspace` screen where you hold a multi-step, site-aware conversation with an assistant. The assistant can search your content under your own capabilities, renders post results as a table, and writes nothing until you approve a proposal, which shows the exact values -- including the post status -- that will be written ([#282](https://github.com/WordPress/ai/issues/282)).
- New `ai/search-content` Ability that runs a bounded, capability-filtered full-text search across the post types exposed to abilities, returning titles and excerpts rather than post bodies. Registered by the AI Workspace experiment, so it is also available to the REST `abilities` endpoints, the Abilities Explorer and MCP clients ([#282](https://github.com/WordPress/ai/issues/282)).
- New `ai/get-site-info` Ability that returns the site's name, tagline, home URL, language, timezone, date and time formats, active theme and whether it is a block theme, plus the WordPress and PHP versions for users who can view Site Health (`view_site_health_checks`). It never returns the admin email, the WordPress address, database details or the plugin list, which is why the AI Workspace offers it while withholding the broad `core/get-environment-info` and `core/settings-get` ([#1287](https://github.com/WordPress/ai/issues/1287)).
- New `ai/find-admin-screens` Ability that answers "where do I…" with links: given a short description such as "hide my site from google", it returns up to five matching admin screens from a curated map of core screens, only those the current user can open, each linked with `admin_url()`. Matching runs on the server with no model call, and the map is filterable through `wpai_admin_screens` ([#1287](https://github.com/WordPress/ai/issues/1287)).
- The AI Workspace can propose changes to things that already exist: a post's title, excerpt or content (`ai/propose-post-changes`), and the site title or tagline (`ai/propose-site-identity`). Nothing changes until the person approves. The card shows each current value beside the new one, says when a change goes live as soon as it is approved, and lets the person edit a value first. Approving is strictly one-time, and a value that changed since it was proposed is left alone and reported. This brings in the Site Agent's write actions from [#1214](https://github.com/WordPress/ai/pull/1214) as part of the AI Workspace ([#1287](https://github.com/WordPress/ai/issues/1287)).
- The command palette (Cmd/Ctrl+K) suggests admin screens with AI when a search finds nothing of its own, and offers "Ask AI: <search>" to carry the question into the AI Workspace, unsent. It is part of the AI Workspace experiment rather than an experiment of its own, bringing in [#1250](https://github.com/WordPress/ai/pull/1250) ([#1287](https://github.com/WordPress/ai/issues/1287)).
- Every AI Workspace tool call, including a withheld one, and every proposal event (created, edited, declined, expired, failed, or refused because its chat was deleted) is recorded in the AI Request Log under a new `agent` type, and the log screen gains a `denied` status. No row records post content or option values ([#1287](https://github.com/WordPress/ai/issues/1287)).
- Saved AI Workspace chats are included in `Tools → Export Personal Data` and removed by `Tools → Erase Personal Data`, archived chats included, whether or not the experiment is on ([#1287](https://github.com/WordPress/ai/issues/1287)).
- A Wapuu shows while an AI Workspace turn runs, finishes or fails, from the set Jeffrey Paul (@jeffpaul) posted, derived from Kazuko Kaneuchi's original Wapuu. With reduced motion it is a still frame ([#1287](https://github.com/WordPress/ai/issues/1287)).
- The AI Workspace's tool surface is no longer a fixed list. An ability exposed to the surface -- through `meta.public`, or by naming the `ai-workspace` channel -- and annotated `readonly: true`, `destructive: false`, `open_world: false` -- can be offered to the assistant alongside the three that ship with it. Admission defaults to refusing: an ability that is not public, and has not opted in, is never offered. Declaration-based admission is itself switched **off** until [#354](https://github.com/WordPress/ai/issues/354) settles the channel name, so the shipped surface is still the three curated abilities; `add_filter( 'wpai_workspace_tool_admission_enabled', '__return_true' )`, or the `WPAI_WORKSPACE_TOOL_ADMISSION` constant, turns it on to try it. A short list of core abilities that read personal data, settings or environment detail is never admitted whatever they declare, filterable through `wpai_workspace_withheld_abilities`. Exposure and the annotations are both the ability author's self-attestation, and the effect class is a declared intent rather than an enforced property: the site owner's Explorer controls and the execute-time `permission_callback` remain the boundaries ([#1003](https://github.com/WordPress/ai/issues/1003)).
- The Abilities Explorer shows which abilities the AI Workspace assistant can call, the exact description text the model receives, and why any other ability is excluded. A site owner can remove an ability from the surface or switch the policy off entirely and return to the three that ship ([#1003](https://github.com/WordPress/ai/issues/1003)).

Expand All @@ -14,6 +21,11 @@ All notable changes to this project will be documented in this file, per [the Ke
- New temporary filter `wpai_workspace_tool_admission_enabled` (and the matching `WPAI_WORKSPACE_TOOL_ADMISSION` constant) switches declaration-based admission on ahead of [#354](https://github.com/WordPress/ai/issues/354); both are removed when it lands. Separate from the site owner's admission-policy off switch on the Abilities Explorer, which stays ([#1003](https://github.com/WordPress/ai/issues/1003)).
- The site owner's tool removals are applied wherever the workspace builds its candidate list, rather than through a filter registered by the workspace experiment's bootstrap, so a removal holds on a site that runs the Abilities Explorer without the workspace ([#1003](https://github.com/WordPress/ai/issues/1003)).
- New filters for the AI Workspace: `wpai_workspace_tool_candidates` (the ability allowlist offered to the model), `wpai_workspace_max_rounds`, `wpai_workspace_system_instruction`, `wpai_workspace_stream_emitter` and `wpai_has_function_calling_support` ([#282](https://github.com/WordPress/ai/issues/282)).
- New `wpai_agent_event` action, fired for every AI Workspace agent event with its operation, status, context and error message, whether or not AI Request Logging is on. It covers agent turns and approvals, not direct MCP calls to an ability ([#1287](https://github.com/WordPress/ai/issues/1287)).
- New filters `wpai_workspace_write_proposals_enabled` (default `true`), which turns off the proposals that change existing content, and `wpai_workspace_proposal_kinds`, the list of proposal types the tools, turn rules and system instruction are built from ([#1287](https://github.com/WordPress/ai/issues/1287)).
- The AI Workspace's own abilities (`ai/propose-*` and `ai/ask-user`) declare `meta.mcp.public` as false, so MCP clients are no longer offered tools that only work inside a workspace turn. An override on the MCP Access screen still wins ([#1287](https://github.com/WordPress/ai/issues/1287)).
- `ai/read-content-bodies` accepts `raw: true` to return a post's stored block markup, only for posts the user can edit ([#1287](https://github.com/WordPress/ai/issues/1287)).
- AI Workspace tool-call and write rows in the AI Request Log now use the `agent` type; rows logged before keep the `ability` type ([#1287](https://github.com/WordPress/ai/issues/1287)).
- Documented how to run the PHP and e2e suites in one session: `npm run test:php` reinstalls WordPress in the shared test environment and deactivates the plugins, so they must be re-activated before `npm run test:e2e` ([#282](https://github.com/WordPress/ai/issues/282)).

## [1.5.0] - 2026-10-29
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,7 @@ Everything is opt-in and off by default. Features are stable and supported; Expe

* **[Abilities Explorer](docs/experiments/abilities-explorer.md)** – Discover, inspect, test, and document all abilities registered via the WordPress Abilities API.
* **[AI Request Logging](docs/experiments/ai-request-logging.md)** – Logs AI requests for observability and debugging.
* **[AI Workspace](docs/experiments/ai-workspace.md)** - Hold a multi-step conversation about your own site under Tools. The assistant searches and reads your content, answers questions about the site, links the admin screen for a task, and proposes new drafts and templates or changes to posts and the site title and tagline, which happen only once you approve them. It also adds an AI fallback and an "Ask AI" row to the command palette.
* **[Alt Text Generation](docs/experiments/alt-text-generation.md)** - Generates descriptive alt text for images using AI vision models.
* **[Block Container Label Generation](docs/experiments/block-container-label-generation.md)** - Generates short List View labels for Group, Columns, and other container blocks.
* **[Comment Moderation](docs/experiments/comment-moderation.md)** (runs automatically) - Automatically moderate comments based on toxicity detection and sentiment analysis, and give each comment a value score. Includes guest comments by default.
Expand Down Expand Up @@ -108,7 +109,6 @@ Overview of planned features:

* **AI Playground** – Experiment with different AI models and providers.
* **Content Assistant** – AI-powered writing and editing in Gutenberg.
* **Site Agent** – Natural language WordPress administration.
* **Workflow Automation** – AI-driven task automation.

## Developer Experience
Expand Down
Loading
Loading