Title: LolaCore – AI Admin Agent
Author: Fran Barbero
Published: May 22, 2026
Last modified: August 20, 2026
---
Search plugins
# LolaCore – AI Admin Agent
By [Fran Barbero](https://profiles.wordpress.org/vanguardhive/)
[Download](https://downloads.wordpress.org/plugin/lolacore.2.7.2.zip)
[Live Preview](https://vec.wordpress.org/plugins/lolacore/?preview=1)
* [Details](https://vec.wordpress.org/plugins/lolacore/#description)
* [Reviews](https://vec.wordpress.org/plugins/lolacore/#reviews)
* [Installation](https://vec.wordpress.org/plugins/lolacore/#installation)
* [Development](https://vec.wordpress.org/plugins/lolacore/#developers)
[Support](https://wordpress.org/support/plugin/lolacore/)
## Description
> **You:** Run the weekly cleanup.
> **Lola:** Last week you decided to keep post revisions for 30 days and leave the
> ones on your landing pages alone. Going by that, 1,240 revisions and 1.2K expired
> transients are safe to clear, about 34 MB. I’ll show you the exact list before
> anything runs. Proceed?
You didn’t repeat your rules. You didn’t re-explain last week. Lola already knew,
because she remembers your site across sessions while every other AI tool forgets
the moment you close the tab. That is the difference between a chatbot and an agent
that runs your site.
Running WordPress once is easy; running it every day wears you down—separate screens,
repeated clicks, context gone when you close the session. That grind has a name:
[admin fatigue](https://lolacore.com/admin-fatigue/), the real cost of running a
site. It hits hardest in WooCommerce, where every order and stock update adds another
screen. I ran a store for ten years; what burned me out was never the selling—it
was the admin.
LolaCore is where that stops. Lola is an AI agent inside your wp-admin. You tell
her what you need; she does the admin work and shows you exactly what she will change
before anything happens. No new dashboard. No external tool. She works where you
already work.
She is **built natively on the WordPress 7.0 AI Client and the Abilities API**.
She reads your database, reasons about it, and executes real actions only with your
explicit approval. Full picture: [documentation](https://lolacore.com/documentation/).
#### Persistent memory
Memory is the foundation everything else stands on.
Lola remembers facts across sessions: plugin conflicts, security findings, your
preferences, decisions you have made—all stored locally in your WordPress database.
Ask what you worked on last week and she searches that memory plus the action log
before answering. Correct or archive individual facts from chat without a full wipe.
Important findings stay sharp; old trivia fades; pinned facts stay longer. When
you start a new conversation, you don’t re-explain your stack. You pick up the thread.
How decay, boosting, and export/import work: [persistent memory guide](https://lolacore.com/documentation/#persistent-memory).
#### 77 abilities. 10 domains. One chat.
* **Site diagnostics** (4 abilities). WordPress and PHP status, HTTPS, database
size, security headers, SEO audit. Lola tells you what’s broken before your client
does.
* **Plugins** (8). Search WordPress.org, install, activate, deactivate, update,
roll back to an earlier release, or update all. “Update all plugins” is one sentence,
not 14 update screens.
* **Plugin Builder** (9). Describe a custom plugin in chat. Lola reads your site,
co-designs a short plan, generates files with safety checks and AI code review,
then you test in Playground before it touches your live site.
* **Block Builder** (9). Same flow for custom Gutenberg blocks: Lola scaffolds `
block.json`, editor scripts, and the PHP render callback; you preview in Playground,
then install on approval.
* **Content & metadata** (7). Create pages, edit posts, change status, update slugs,
read and write post meta. Works with Yoast, RankMath, and other post-meta plugins.
* **Users** (4). Create accounts, change roles, remove users with automatic content
reassignment.
* **Database & cache** (3). Clean post revisions, expired transients, orphaned
postmeta, and spam comments. The cleanup WordPress never does for you.
* **Taxonomies & media** (7). Categories, tags, comments, and media files.
* **Themes & settings** (13). Install, update, and delete themes with safety warnings,
read and write site options, manage navigation menus, review cron jobs.
* **WooCommerce** (13). Detected automatically. Products, orders, customers, coupons,
categories, sales reports. “How much revenue this week?”—from your store data,
not a dashboard.
Every ability in detail: [ability reference](https://lolacore.com/documentation/#what-lola-can-do).
Store tools with examples: [WooCommerce abilities](https://lolacore.com/documentation/#woocommerce-core).
#### How Lola stays safe
**Your data never touches our servers.** No telemetry, no analytics. Your conversations
go from your hosting to your AI provider. That’s it.
**Nothing happens without your approval.** Every write action shows a preview card
with exactly what Lola is about to do. You confirm or cancel. Every action is logged
with before/after snapshots. Admin-only.
#### She has an opinion
Lola has judgment. When a change would hurt your site, she tells you before you
commit and offers a safer way to get what you want. If you still want to proceed,
she does it your way and records the decision, so the next time it comes up the
context is already there.
#### Any model, your choice
Lola works with whatever AI provider you configure in WordPress 7.0 (Settings AI).
Agentic models perform best: GPT-5.5, DeepSeek V4, Claude 4.6 Sonnet or Opus 4.7.
Gemini, Grok, Ollama, and OpenRouter work through the native connector.
You pay your provider directly—no token markup from LolaCore. Each message sends
only the abilities your request needs, not the full catalog. Setup: [connecting your AI provider](https://lolacore.com/documentation/#api-provider-setup).
#### Work with your site from Claude
If you already pay for Claude, that subscription can run your site. Open **Lola
MCP Settings**, find **Connect from the web**, and click **Add to Claude**. The
dialog opens on claude.ai with everything filled in — sign in, approve the connection
on your site, done. From that moment, “update the plugins on my site” or “how did
the store do this week?” works from any Claude conversation, on desktop or mobile.
No API key to generate, no provider account to configure.
You approve the connection once, as an administrator, on your own site. Every connected
app appears in a list on the same screen, with a Disconnect button that cuts its
access on the spot.
Three things the connection needs: HTTPS, a site reachable from the internet (not
a local install), and pretty permalinks. If any of them is missing, the screen tells
you exactly what to fix. If your host runs an aggressive firewall, allow Anthropic’s
published address range `160.79.104.0/21` — the screen has a built-in connection
check that tells you whether the site is answering correctly.
#### Native to WordPress 7.0
LolaCore runs entirely on the native WordPress AI Client and Abilities API. No external
HTTP libraries, no custom credential vaults. When WordPress updates its AI infrastructure,
LolaCore updates with it.
#### Spanish and Brazilian Portuguese
Lola speaks your language. Set WordPress to `es_ES` or `pt_BR` and the full admin
experience runs in native Spanish or Brazilian Portuguese: settings panel, chat
widget, ability labels, onboarding, preview cards, errors, and status messages.
More than 1,050 user-facing strings per locale — not a thin language pack.
The intent router is localized for both languages. Ask in Spanish or Portuguese
which pages are in draft, what needs attention today, or to list your skills — Lola
routes to the right tools without English keywords. Other locales fall back to English.
#### Lola’s lane
A tool that does everything does nothing well. Lola is built narrow on purpose.
* She doesn’t edit theme files, core, or server config. Plugin Builder and Block
Builder are the exceptions: she generates custom plugins and blocks that you
own and iterate in chat.
* She doesn’t see your frontend. Lola lives inside wp-admin.
* In wp-admin, she works on one site at a time. Over MCP, your editor can hold
the whole fleet.
Why these boundaries exist: [what Lola cannot do](https://lolacore.com/documentation/#what-lola-cannot-do).
#### Skills and playbooks: teach Lola how you work
Skills are short behavioral guides in plain Markdown that shape how Lola approaches
a task. LolaCore ships with 14 built in, and you can write your own or ask Lola
to create one for you in chat. [Skills guide](https://lolacore.com/documentation/#skills).
A playbook is a curated manual for one area of work: your brand guidelines, your
FSE build conventions, an internal process. Upload a document (TXT, Markdown, DOCX,
or HTML), Lola distills it into a draft, you review and activate it. From then on
she consults it whenever that domain comes up. [Playbooks guide](https://lolacore.com/documentation/#playbooks).
#### Free addons teach Lola your stack
When you work with a specific tool every day, a free addon teaches Lola that domain—
all sharing the same site memory:
* [LolaCore for Elementor](https://lolacore.com/lolacore-for-elementor/): manage
your Elementor pages and templates from chat
* [LolaCore for ACF](https://lolacore.com/lolacore-for-acf/): read and write Advanced
Custom Fields in plain language
* [LolaCore for SEO](https://lolacore.com/lolacore-for-seo/): audit and edit your
SEO without opening another panel
* [LolaCore for Forms](https://lolacore.com/lolacore-for-forms/): work with your
forms and their entries from the chat
* [LolaCore for Statistics](https://lolacore.com/lolacore-for-statistics/): ask
about your traffic and get the number, not a dashboard
* [LolaCore for FSE](https://lolacore.com/lolacore-for-fse/): a block and template
builder for block themes
Browse them all: [lolacore.com/add-ons](https://lolacore.com/add-ons/).
#### For agencies and consultants
Run WordPress for clients and the admin work multiplies with every site. Free addons
go deep on the stack you build with: 91 for Elementor, 26 for ACF, 22 for SEO, 18
for Statistics, 15 for Forms, 17 for FSE—189 abilities on top of Lola’s core.
Each client site is a separate install with its own memory; contexts never bleed
across clients. Preview cards and logs mean you always know what changed on a live
site.
LolaCore bundles a zero-config MCP server—each client site becomes a tool in Cursor,
Claude Code, or any MCP client. Connect the fleet and one agent runs it: “update
plugins on site A”, “how did site B sell this week”, “SEO audit on every site”.
Your agent, your rules, Lola’s full toolset—abilities, memory, builders, skills,
playbooks.
#### Don’t know what to say? Start here.
No commands, no syntax. Three prompts you can paste right now:
> “Give me a quick briefing on the site. Anything that needs attention today.”
> “Update all plugins except Elementor and [plugin name]. Show me the list first.”
> “How much have we sold this week? Compare it to last week.”
There are 45 more in the [prompt library](https://lolacore.com/documentation/#prompt-library):
daily check-ins, maintenance routines, session combos.
### External Services
LolaCore connects to the following external services. Each connection is documented
with what triggers it, what data is sent, and links to the relevant terms and privacy
policies.
#### AI Providers (Chat Feature)
When you use the chat widget, your messages are sent to whichever AI provider you
have configured in WordPress’s built-in AI settings (Settings AI). LolaCore does
not operate its own servers and does not route data through any intermediary.
**Data sent to your provider:**
– Your chat messages – A summary of your site scan(
WordPress version, active plugin list, PHP version) – Relevant memory facts (site
observations stored in your local database)
**Data never sent:**
– Passwords, API keys, wp-config values, or database credentials–
Personal user data (emails, addresses, payment info)
**When this happens:** Only when you actively send a message in the chat widget.
No background calls.
**Supported providers:**
– OpenAI – [https://openai.com](https://openai.com) |
[Terms of Use](https://openai.com/policies/terms-of-use) | [Privacy Policy](https://openai.com/privacy)–
Anthropic – [https://anthropic.com](https://anthropic.com) | [Terms of Service](https://www.anthropic.com/legal/consumer-terms)
| [Privacy Policy](https://www.anthropic.com/privacy) – DeepSeek – [https://deepseek.com](https://deepseek.com)
| [Terms of Use](https://chat.deepseek.com/downloads/DeepSeek%20Terms%20of%20Use.html)
| [Privacy Policy](https://chat.deepseek.com/downloads/DeepSeek%20Privacy%20Policy.html)
#### Claude Web Connection (Optional)
When you connect your site to Claude from **Lola MCP Settings**, the traffic direction
is inbound: Anthropic’s servers call your site’s REST API on behalf of your signed-
in Claude account. LolaCore does not send any data to Anthropic on its own — data
leaves the site only when you actively ask Claude to work with it, and every connection
first requires an administrator’s approval on the site’s consent screen.
* Anthropic (Claude) – [https://anthropic.com](https://anthropic.com) | [Terms of Service](https://www.anthropic.com/legal/consumer-terms)
| [Privacy Policy](https://www.anthropic.com/privacy)
#### Wordfence Vulnerability API
LolaCore can check your installed plugins against the public Wordfence vulnerability
database to identify known security issues.
**Endpoint:** `https://www.wordfence.com/api/intelligence/v2/vulnerabilities/scanner`
**Data sent:** An HTTP GET request with no request body. LolaCore sends only a User-
Agent header identifying itself (`LolaCore WordPress Plugin`). No plugin lists,
site URLs, or user data are transmitted to Wordfence.
**Data received:** A public JSON feed of known WordPress plugin vulnerabilities.
LolaCore compares this list locally against your installed plugin slugs and versions
to surface relevant findings.
**When this happens:** Only when you explicitly request a vulnerability check through
the chat (e.g., “check my plugins for vulnerabilities”). This call is never made
automatically during plugin activation, scheduled scans, or background operations.
**Service links:**
– Wordfence – [https://www.wordfence.com](https://www.wordfence.com)
| [Terms of Service](https://www.wordfence.com/terms-of-use-and-privacy-policy/)
| [Privacy Policy](https://www.wordfence.com/privacy-policy/)
#### WordPress.org Plugin API
When you ask Lola to search for or install plugins, LolaCore queries the official
WordPress.org Plugin API.
**Data sent:** Plugin search keywords or slug identifiers.
**Data received:** Plugin
metadata, descriptions, and download URLs from the WordPress.org repository.
**When this happens:** Only when you use plugin search or install features through
the chat.
* Service: [https://wordpress.org](https://wordpress.org) | [API Documentation](https://codex.wordpress.org/WordPress.org_API)
#### Google Fonts
The admin settings page loads two font families (Plus Jakarta Sans and JetBrains
Mono) from Google Fonts for the plugin’s admin interface.
**Data sent:** Standard HTTP font file requests. Google receives the requesting
IP address and browser User-Agent.
**When this happens:** Each time an administrator
opens the LolaCore settings page.
* Service: [https://fonts.google.com](https://fonts.google.com) | [Terms of Service](https://developers.google.com/terms)
| [Privacy Policy](https://policies.google.com/privacy)
## Screenshots
[⌊Lola's first scan: a specific, actionable report about your site, not a generic
greeting.⌉⌊Lola's first scan: a specific, actionable report about your site, not
a generic greeting.⌉[
Lola’s first scan: a specific, actionable report about your site, not a generic
greeting.
[⌊Security audit results with severity flags and fix suggestions.⌉⌊Security audit
results with severity flags and fix suggestions.⌉[
Security audit results with severity flags and fix suggestions.
[⌊Plugin installation through chat. Lola finds, downloads, and asks before installing.⌉⌊
Plugin installation through chat. Lola finds, downloads, and asks before installing
.⌉[
Plugin installation through chat. Lola finds, downloads, and asks before installing.
[⌊Action confirmation flow: every write operation shows a preview and requires approval
before executing.⌉⌊Action confirmation flow: every write operation shows a preview
and requires approval before executing.⌉[
Action confirmation flow: every write operation shows a preview and requires approval
before executing.
[⌊The ability panel: 77 abilities across 10 domains, each toggleable from the settings
page.⌉⌊The ability panel: 77 abilities across 10 domains, each toggleable from the
settings page.⌉[
The ability panel: 77 abilities across 10 domains, each toggleable from the settings
page.
## Installation
1. Upload the `lolacore` folder to `/wp-content/plugins/` or install via the WordPress
plugin screen.
2. Activate the plugin through the “Plugins” screen in WordPress.
3. Configure your AI provider through WordPress’s built-in AI settings (Settings
AI).
4. Open the floating chat widget in your admin dashboard.
5. Start managing your site through conversation.
#### Requirements
* WordPress 7.0 or higher
* PHP 8.0 or higher
* MySQL 5.7+ or MariaDB 10.3+ (JSON column support required)
* An AI provider configured through WordPress’s AI Client settings
* WooCommerce 8.0+ (optional, for store management abilities)
Detailed setup instructions and first-conversation tips: [getting started guide](https://lolacore.com/documentation/#installation).
## FAQ
### What is admin fatigue?
Admin fatigue is the cumulative cost of running a WordPress site through a panel
that puts dozens of clicks between the simple thing you want to do and actually
getting it done. It is worst in WooCommerce stores, but every WordPress admin feels
it. LolaCore exists to remove it: you describe the task, Lola does the admin work
from chat. Full explanation: [what is admin fatigue](https://lolacore.com/admin-fatigue/).
### Do I need to know how to code?
No. You tell Lola what you need in plain language, the same way you would explain
it to an employee. No commands, no syntax, nothing to memorize. If you can describe
the task, Lola can run it.
### Can Lola break my site?
Every write action requires explicit confirmation. Lola shows you exactly what she
is about to do, and you approve or cancel. Safety guards prevent deactivating LolaCore
itself, deleting the last administrator, and permanent content deletion without
warning. All executed actions are logged with before/after snapshots.
### What’s the difference between memory, skills, and playbooks?
Memory is what Lola knows about your site: facts, decisions, and preferences she
has picked up over time. Skills shape how she works a task; one might load a safety
protocol before a bulk deletion. Playbooks are curated manuals for a whole domain,
like the rules of your FSE build or your brand guidelines, and she reads the matching
one before she works in that area. All three sit on top of her abilities, which
are the actions she actually takes in WordPress.
### Does LolaCore charge per use?
No. LolaCore is free. The only cost is your own AI provider: you connect your account
in WordPress settings and pay that provider directly for what you use. LolaCore
takes no cut, adds no markup, and never charges per message.
### Does LolaCore work with WooCommerce?
Yes. If WooCommerce is active, Lola automatically detects it and enables 13 dedicated
abilities for product management, order tracking, customer data, coupons, categories,
and sales reporting.
### Is LolaCore only for WooCommerce stores?
No. The store owner feels admin fatigue most acutely, so a lot of the examples are
about WooCommerce, but 64 of Lola’s 77 abilities are general WordPress work: diagnostics,
plugins, content, users, database, themes, and settings. If you run any WordPress
site, Lola earns her keep with or without WooCommerce.
### What data is sent to AI providers?
When you chat with Lola: your messages, a summary of your site scan (WordPress version,
plugin list, PHP version), and relevant memory facts. Passwords, API keys, and personal
user data are never included in the AI context.
### Where is my data stored?
All data (memory facts, chat history, configuration) is stored in your WordPress
database. Six dedicated tables are created on activation (`lolacore_memory`, `lolacore_log`,`
lolacore_config`, `lolacore_sessions`, `lolacore_messages`, `lolacore_skills`).
Nothing is sent to external servers except your chat messages to your configured
AI provider when you actively use the chat.
### What happens when I deactivate the plugin?
Deactivation clears scheduled cron events but preserves all your data. Uninstalling
the plugin permanently deletes all database tables and stored options. Your choice.
### Does LolaCore work with other plugins?
Lola reads and writes standard WordPress data: options, post meta, users. She works
alongside Yoast SEO, RankMath, ACF, Contact Form 7, and any plugin that stores data
in the WordPress database.
### Can I use LolaCore for client sites?
Yes. Install LolaCore on each client site independently. Each installation keeps
its own memory and its own logs, so one client’s context never bleeds into another’s.
The free addons cover the tools you build with (Elementor, ACF, SEO, forms, analytics,
block themes), and consultants use Lola to cut down monthly maintenance and produce
client reports from a conversation.
### Can I use Lola from an IDE?
Yes. Every ability is exposed through the WordPress Abilities API, and LolaCore
bundles a zero-config MCP server. Over MCP, your own agent (Claude Code, Cursor,
Claude Desktop) drives Lola’s toolset directly under the rules you set for it: all
abilities, the persistent memory, skills, playbooks, Plugin Builder and Block Builder.
Agencies use this to run a fleet: add each client site’s MCP server to one editor
and a single agent updates, audits, and reports across all of them. Plugins and
blocks built over MCP still have to pass WordPress Playground before they can be
installed. Lola herself, with her judgment and confirm-before-write flow, lives
in the wp-admin chat.
### How does the Claude connection stay secure?
The connection follows the open standard Claude uses for custom connectors. The
sign-up address on your site is public because the standard requires it — that is
what lets the button work without you typing identifiers by hand. Signing up grants
nothing: until a site administrator signs in and approves the connection on the
site’s own consent screen, a registered app cannot read or write anything. Approved
connections use the same curated set of abilities as the MCP server, every action
is logged, and the Connected apps list on **Lola MCP Settings** shows each one
with a Disconnect button that revokes its access immediately. A daily cleanup removes
registrations nobody used within 24 hours, connections idle for more than 30 days,
and expired sign-in data.
### Why does LolaCore require WordPress 7.0?
LolaCore is built entirely on the native AI Client introduced in WordPress 7.0.
This eliminates external HTTP dependencies, uses WordPress’s own credential management,
and ensures long-term compatibility as the platform evolves. No shims, no polyfills,
no fallback layers.
### Where is the full documentation?
This readme covers the essentials. The full documentation goes deeper: memory mechanics,
the complete ability catalog with examples, a prompt library with 48 ready-to-use
conversation starters, a detailed settings walkthrough, and 45+ answers across 12
FAQ categories. **[LolaCore Documentation](https://lolacore.com/documentation/)**
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“LolaCore – AI Admin Agent” is open source software. The following people have contributed
to this plugin.
Contributors
* [ Fran Barbero ](https://profiles.wordpress.org/vanguardhive/)
[Translate “LolaCore – AI Admin Agent” into your language.](https://translate.wordpress.org/projects/wp-plugins/lolacore)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/lolacore/), check out
the [SVN repository](https://plugins.svn.wordpress.org/lolacore/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/lolacore/) by [RSS](https://plugins.trac.wordpress.org/log/lolacore/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 2.7.2
* Compatibility: Tested up to WordPress 7.1.
* Feature: **Connect Claude from the first chat.** After the site scan, Lola offers
Connect with Claude next to Configure AI Connectors. One click opens Claude with
your site already filled in; you sign in, approve, and talk to her from the account
you already have. To chat inside wp-admin, connect a provider in Settings Connectors.
* Feature: **Ask for ACF fields, SEO titles, a translation, or a block-theme edit—
if the free addon isn’t on the site, Lola offers to install it from WordPress.
org in the same conversation.** She installs the host plugin first when it’s
missing (Advanced Custom Fields, Yoast, Polylang, and the rest). She doesn’t
mention addons you didn’t ask for, and she doesn’t send you to the Plugins screen.
Works from the wp-admin chat and from Claude.
#### 2.7.1
* Fix: **get-comments response uses total like get-content** — comment listings
and direct lookups now include total (count remains as a backward-compatible
alias).
* Fix: **Paginated get-content and get-comments chunks are labeled honestly** —
when content_limit is set on a direct lookup, content_preview is true so agents
know they are reading a chunk, not the full body.
* Fix: **get-content returns the full post body again** — when you pass a post_id,
Lola returns the complete HTML with content_length. For very long posts, use
content_offset and content_limit to read in chunks. Post listings still return
a short preview marked with content_preview: true, plus truncated, total, and
limit so agents know to fetch again by id.
* Fix: **Surgical post edits from MCP** — edit-content accepts search and replace(
and replace_all) so connected assistants can patch long articles without rewriting
the entire body. Full body replacement via content still works when you mean
to replace everything.
* Fix: **get-comments returns the full comment text again** — pass comment_id for
the complete text; comment listings stay as truncated previews with content_preview:
true and explicit bounds.
* Improvement: **Confirmation previews are honest** — dry-run diffs for posts,
pages, and post meta use preview_* fields and mode: preview so truncated confirmation
cards are never mistaken for the value that will be saved.
* Improvement: **MCP discovery summaries label truncation** — the lightweight ability
index flags when a summary was shortened (summary_truncated, summary_total, summary_limit).
* Improvement: **MCP instructions** — connecting agents are told to use get-content
for post bodies and not to use Polylang translation tools as a workaround to
read content.
* Improvement: **Plugin and block code audits** — when inline code returned for
review exceeds the audit budget, the response includes truncated, total, and
limit plus a clear audit_warning.
* Feature: **Test a built plugin and install it without leaving the conversation**—
when Lola builds a plugin or a block, you can open it in Playground, try it,
and simply tell her it works. She records your test and installs it on your site
from there. Until now that confirmation lived on the WordPress admin screen,
so anyone working from Claude reached Playground and had no way to finish.
* Improvement: when Lola holds something back on purpose — such as installing a
plugin before you have tested it — the reply now reads as a decision with a clear
next step, and connected assistants get the message in plain text.
* Fix: Premium addon tools no longer appear in the Claude or MCP catalog when the
addon license is not active. They were showing up under a generic name, which
made it look like the tools were available when they were not.
#### 2.7.0
* Feature: **Full operability from Claude** — the web connection now offers the
same abilities as the wp-admin chat and IDE connections. Whatever Lola can do
on your site, she can do from Claude too, including addon abilities like WooCommerce
Pro.
* Feature: **Lightweight tool catalog for web clients** — Claude reads a compact
index of every ability (name, category, and a one-line summary) instead of the
full technical catalog, so sites with many addons connect without hitting platform
limits.
* Feature: **Drafts before publishing** — when a web client asks to publish new
content, Lola creates a draft first and explains how to publish it, so nothing
goes live without a second look.
* Feature: **Site context for web clients** — connected assistants can ask who
manages the site and what Lola remembers, and present Lola’s memory with proper
attribution.
* Improvement: after a web client changes something on the site, a gentle reminder
nudges it to save important decisions to Lola’s memory.
* Improvement: clearer messages when an ability isn’t available through a web connection,
without confusing technical causes.
* Fix: cache plugins can no longer serve stale responses to the connection endpoints—
the root cause of intermittent connection errors on sites running LiteSpeed Cache.
* Fix: the cache purge ability now detects and purges LiteSpeed Cache and reports
which cache plugin was purged.
* Fix: addon abilities that use the site’s own REST services internally (such as
the WooCommerce tools) now work through the Claude connection.
* Fix: bridged abilities without arguments no longer fail input validation when
a client sends parameters anyway.
#### 2.6.0
* Feature: **Work with your site from Claude** — connect your Claude subscription
to your site with one button. Open Lola MCP Settings, click “Add to Claude”,
sign in, approve, and any Claude conversation can run your site: update plugins,
check store sales, edit content. No API key needed.
* Feature: **Connect from the web screen** — connection cards with a built-in check
that verifies your site answers correctly, a Connected apps list showing every
approved connection with when it was last used, and one-click disconnect.
* Feature: **Admin consent screen** — every web connection waits for an administrator
to sign in and approve it on the site itself. Nothing is granted by connecting
alone.
* Improvement: The connection screen detects local installs, plain HTTP, and plain
permalinks, and explains what to fix instead of showing a button that cannot
work.
* Improvement: A daily cleanup prunes web-connection data: registrations nobody
used within 24 hours, connections idle for more than 30 days, and expired sign-
in codes and tokens.
#### 2.5.1
* Fix: Improved MCP Adapter coexistence when other plugins ship the same bundled
library. LolaCore defers loading when WP\MCP classes are already registered,
preventing class and trait redeclaration fatals during plugin bootstrap.
#### 2.5.0
* Feature: **Memory recall in web chat** — Ask what you worked on last week and
Lola searches facts, session summaries, and the action log before answering.
Recall intent prefetches results into the prompt and exposes `getMemoryContext`
and `getActionHistory` tools.
* Feature: **Memory lifecycle tools** — Correct, archive, delete, compact, and
export memory facts from chat and MCP (`update-memory-fact`, `archive-memory-
fact`, `delete-memory-fact`, `compact-memory`, `export-memory`) without a full
wipe or manual JSON import.
* Improvement: **Temporal memory search** — `get-memory-context` and `get-action-
history` accept `since` and `until` datetime filters for week/month/day recall
queries.
* Fix: Plugin activation no longer fatals when another plugin already loaded MCP`
McpAdapter` from a different vendor path.
* Fix: Temporal recall questions no longer inject stale `last_session_summary` —
RECALL RESULTS and memory facts drive the answer instead.
#### 2.4.4
* Fix: Activation no longer fatals on sites without WP-CLI. The MCP vendor preload
skipped CLI-only adapter files that extend `WP_CLI_Command`.
#### 2.4.3
* Fix: More reliable MCP connections on sites where several plugins expose MCP-
related features. LolaCore initializes its MCP integration earlier and handles
startup order more predictably, reducing timing issues that could interrupt IDE
or external tool connections.
#### 2.4.2
* Feature: **Shared domain playbooks** — Plugin, content, and WooCommerce workflows
now draw from one registry of domain guidance, so chat and the LolaHub ability
catalogue stay aligned whether Lola runs on one site or across your fleet.
* Feature: **Clearer fleet execution feedback** — Remote actions from LolaHub report
complete, follow-up, or partial outcomes with the right status, so install-and-
activate and other multi-step jobs show exactly where they stand after you approve.
* Improvement: **Smarter fleet install previews** — Plugin install plans are checked
against WordPress.org before a job is queued, so you see missing or mistyped
slugs in the preview instead of discovering them later.
#### 2.4.1
* Feature: **Richer fleet ability catalogue** — When a client site pairs with LolaHub,
LolaCore now shares what Lola can do on that site in a structured, category-based
summary (plugins, content, WooCommerce, and more). Agency operators get enough
context to route work across a fleet without loading hundreds of individual abilities
into every conversation.
* Feature: **Clearer multi-step fleet results** — Remote actions from LolaHub now
report whether work finished completely, needs a follow-up step, or failed. Install-
and-activate flows and similar multi-step jobs no longer get marked done when
only part of the work ran.
* Fix: **Parameter handling in chat and fleet** — Plugin install now respects the
activate option; WooCommerce product lookups honor the product type filter; order
status updates accept a customer note; SEO diagnosis respects the result limit
you asked for.
* Improvement: **Minimum version check on agency pairing** — Sites running an older
LolaCore release see a clear message during LolaHub connection if an update is
required, instead of failing silently later.
#### 2.4.0
* Feature: **Maintenance & security posture in fleet health** — `lolacore/get-site-
health` now returns a `maintenance` block for agency reporting: SSL status, debug
mode, file editing lock, core up-to-date, PHP version and whether it is still
supported, a pending-updates count, and backup detection (which backup solution
is active, plus a best-effort last-backup time from UpdraftPlus). Everything
is read from the site’s own local scan — no uptime pinging or external monitoring,
and backups are reported as detected or not, never assumed.
#### 2.3.0
* Feature: **Action domains in history** — `lolacore/get-action-history` now returns
a `domain` for each action (for example `woocommerce`, `content_metadata`, `site_diagnostics`,`
plugin_builder`). A fleet manager can group a site’s work into clean sections
straight from the log instead of inferring it. The domain is resolved when the
history is read; no new data is stored.
#### 2.2.2
* Fix: **Fleet remote writes never applied after approval** — Dry-run previews
for `POST /lolacore/v1/hub/execute` were stored in the hub request-id cache using
the same `request_id` as the later apply call. Approving a LolaHub fleet plan
returned the cached preview (status ok) without running the write on the child
site. Dry-run responses are no longer cached; idempotency cache applies only
to completed executions.
* Fix: **`update_plugin` param alias** — Remote and chat paths may pass `plugin`
instead of `slug`; the handler now accepts both keys so fleet `lolacore/update-
plugin` plans do not fail at execution time.
* Fix: **Non-verifiable fleet writes execute after approval** — Abilities such
as `create-content` and `add-language` no longer return `not_verifiable` on apply;
params frozen at plan time are executed once the fleet master approves (UI-4 §
3.3).
#### 2.2.1
* Fix: **Agency Connection fatal error** — The transparency page template expected
a scope object that was not passed from the controller, causing a fatal error
on PHP 8.2+ after pairing with LolaHub.
* Fix: **Agency Connection menu placement** — The page now lives under the Lola
menu (LolaCore submenu) instead of a separate top-level admin menu.
* Improvement: **Authorize Application layout** — Long LolaHub callback URLs wrap
inside the WordPress consent card instead of overflowing the box.
#### 2.2.0
* Feature: **Agency fleet connection (child site)** — LolaCore on a client site
can now pair with an agency fleet manager via WordPress native Application Passwords.
Pairing uses the standard `authorize-application` flow; no custom tokens or shared
admin passwords are stored.
* Feature: **Agency Connection admin page** — Site owners see who is connected,
what domains the agency may operate on, recent fleet actions, and can narrow
scope or disconnect at any time. Operator memory can be forgotten without touching
the owner’s local memory.
* Feature: **Remote execution channel** — An authenticated fleet master can run
a curated set of Lola abilities on the child site through `POST /wp-json/lolacore/
v1/hub/execute`, with scope checks, idempotency, and state fingerprints on sensitive
writes so stale approvals are not applied blindly.
* Feature: **Fleet site health & provisioning** — New abilities expose a cached
health snapshot, accept agency playbooks/skills/preferences without overwriting
local owner content, and optionally set the site’s AI provider when Connectors
is available.
* Feature: **Batch memory reconcile** — Fleet-authored memory facts can be pushed
to the child in one round-trip, merged by content hash (`fact_hash`) without
clobbering the site owner’s existing memory. The owner can export seed memory
for adoption on connect.
* Improvement: **Shared remote allow list** — MCP and fleet execution use the same
curated ability list, so the two surfaces cannot drift apart.
#### 2.1.4
* Fix: **Reasoning models no longer leak their thinking into the session summary**—
with a reasoning-capable model (DeepSeek and similar), the “last session summary”
showed the model’s internal deliberation pasted in front of the actual summary.
The thought channel is now filtered out, as it already was in chat replies.
* Fix: **Memory extraction with reasoning models** — the same leak silently broke
fact extraction: the model’s thinking was concatenated ahead of the JSON payload,`
json_decode()` failed, and every fact from that turn was discarded. Lola now
records facts correctly on reasoning models.
* Improvement: **Desktop Mode compatibility** — Lola’s floating widget stays available
and keeps its position when switching into the Desktop Mode shell, and no longer
duplicates itself inside every open window.
#### 2.1.3
* Fix: **MCP native abilities** — `lolacore/get-site-info`, `lolacore/get-memory-
context`, `lolacore/get-action-history`, and `lolacore/get-scan-data` are now
exposed through the LolaCore MCP server. Previously the guard only whitelisted
chat-bridge tool names (e.g. `get-site-status`), so MCP agents received a misleading“
requires a valid license” error when calling the documented boot abilities. Uses
WordPress core `wp_get_abilities()` (`WP_Ability` instances), not the non-existent`
wp_get_registered_abilities()` helper.
#### 2.1.2
* Feature: **Deep internationalization** — complete native support for **Spanish(
Spain)** (`es_ES`) and **Brazilian Portuguese** (`pt_BR`). More than 1,050 user-
facing strings per locale: settings UI, chat widget, ability labels, onboarding,
preview cards, errors, and status messages. Shipped as compiled `.mo` language
packs; other locales fall back to English.
* Feature: **Brazilian Portuguese (pt_BR)** — full translation catalog at parity
with Spanish, transcreated for Brazilian product voice (`você`, not European
Portuguese).
* Improvement: **Localized intent router** for Spanish and Brazilian Portuguese—
natural-language keywords, meta-tool queries (“what can you do?”), holistic monitoring(“
what needs my attention?”), and deferral/confirmation patterns so chat routes
tools correctly in both languages.
#### 2.1.1
* Fix: **TOOL DISCIPLINE** now applies even when write confirmation is disabled
in Safety settings — it was previously omitted on sites with direct-write mode.
* Fix: **Deferred-intent auto-continue** — when Lola says she will look something
up (e.g. “Let me fetch that…”) but emits no tool calls, the server automatically
continues the turn once and forces the read tools to run instead of waiting for
the user to say “ok”.
* Fix: **Plugin Builder iteration install** — updating a built plugin from the
chat delivery card (v2 over an installed v1) now reliably prompts to overwrite
the on-disk copy, completes the install, and activates afterward. Fixes a locale
bug where translated admin languages never triggered the overwrite retry, and
replaces the browser confirm dialog with an inline modal plus clearer activation
errors on the card.
#### 2.1.0
* Feature: **Progressive tool expansion in chat** — new `requestAdditionalCategories`
meta-tool adds 1–2 domain categories to the session without loading every ability(
MCP-style discover expand execute).
* Feature: **`getDiscoveredAbilities` search** — filter by `query`, `category`,`
limit`, or `names_only` so Lola finds the right tool without dumping the full
registry into context.
* Improvement: Session toolset persists across tool continuations — expanded categories
are not lost mid-workflow.
* Improvement: Gemini tool cap prioritizes expanded categories and keeps expansion
meta-tools available under the 32-tool limit.
* Improvement: System prompt **ROUTED TOOLSET DOCTRINE** — cross-domain tasks (
e.g. resolve a page by title, then translate) are expected; Lola escalates before
claiming a task is impossible.
* Improvement: **TOOL DISCIPLINE** — read lookups (search, inspect, resolve a page)
must run in the same turn; no intent-only pauses waiting for the user to say “
ok”.
#### 2.0.3
* Fix: Database migrator now recreates any missing LolaCore tables on load, so
sites that upgraded to Playbooks without getting `wp_lolacore_playbooks` self-
heal on the next admin request — no deactivate/reactivate required.
* Fix: Chat no longer shows a false firewall error when WordPress prints a database
notice before the JSON response (for example a missing Playbooks table with WP_DEBUG
on).
* Fix: Chat error messages now match the real failure (database issue, timeout,
garbled response, or hosting WAF) instead of always blaming the hosting firewall.
#### 2.0.2
* Feature: **Plugin rollback** for WordPress.org plugins — roll back to an earlier
release from chat (`rollback_plugin`). Lola can list older versions first (`get_plugin_versions`).
Premium and custom plugins are blocked with a clear message.
* Improvement: Rollback confirmation card shows a calm human preview (plugin name
and version change) instead of technical fields and long version lists.
#### 2.0.1
* Improvement: **LolaCore for FSE** now appears in the Addons catalog and Expansions
panel before you install it, with a WordPress.org install link (21 abilities).
#### 2.0.0
* Feature: **Block Builder** — describe a custom Gutenberg block in chat; Lola
scaffolds block files, saves to the **Built Blocks** library, tests in WordPress
Playground, and installs to `wp-content/lolacore-blocks/` after your approval.
Nine Block Builder abilities (`createBlock`, `updateBlockCode`, `listBuiltBlocks`,`
getBuiltBlock`, `getInstalledBlock`, `testBlock`, `installBlock`, `uninstallBlock`,`
deleteBuiltBlock`).
* Feature: System playbook **`block-development`** for Block Builder scaffolding
and iteration.
* Improvement: Broader **Spanish (Spain)** coverage for builders, chat, and action
handlers.
* Improvement: **Playbook distiller** — clearer format contract, YAML frontmatter
repair, and persistent error UX when distillation fails.
#### 1.9.0
* Feature: **Playbooks** — curated domain manuals Lola consults when working in
a specific area. Built-in `playbook-format` contract, system playbook `plugin-
development` for Plugin Builder, database and filesystem sources, model-adaptive
delivery (inline hints for lightweight models, full attachment on ability use),
and seven playbook abilities for chat and MCP.
* Feature: Playbooks admin under **Lola Playbooks** — list, create, edit, activate,
upload (TXT/MD/DOCX/HTML), AI distillation with review before save, and reload.
Skills moved to its own submenu (**Lola Skills**).
* Improvement: Upload guardrail with a clear notice when extracted document text
exceeds 40,000 characters.
#### 1.8.9
* Fix: Plugin Builder Playground works again on production hosting. Opening Playground
no longer depends on a loopback scrape on your live server (which often fails
and was blocking every library plugin with a false “fatal error”). Runtime load
checks still run when saving code for review and before installing on your site.
* Improvement: Playground links are short and shareable. The blueprint is served
from your site via a signed REST URL (`blueprint-url`), so MCP and chat agents
can give you a clickable link that opens Playground in the browser without copying
a megabyte-long URL from wp-admin.
#### 1.8.8
* Improvement: The Plugin Builder now works over MCP. A connected code editor can
create and iterate plugins straight into your Plugin Builder library by sending
the exact code — the site no longer asks its own AI to rebuild code the external
tool already wrote. The wp-admin chat is unchanged: there you describe what you
want and Lola writes it. Plugins added over MCP go through the same static safety
checks and must still be tested in Playground before they can be installed.
* Fix: LolaCore for Forms now appears on the Addons screen before you install it,
with a one-click install from WordPress.org — the same pattern as the other free
bridge addons (ACF, SEO, Statistics).
#### 1.8.7
* Fix: On the Addons screen, installed free bridge addons now show **Learn more**
and link to their lolacore.com landing pages instead of **Download free ** (which
only applies before install). Install-from-WordPress.org links are unchanged
for addons you have not installed yet.
* Fix: Addons catalog and cross-domain footer links no longer 404 — marketing URLs
now use UTM-safe landing pages, and **How cross-domain intelligence works **
points to the live add-ons catalog at lolacore.com/add-ons/.
* Fix: The **View all abilities** list on Settings now lists tools for free bridge
addons (ACF, SEO, Statistics, Elementor, and others), not just premium addons
and core domains.
#### 1.8.6
* Fix: Resolved a race condition on sites where another active plugin bundles its
own copy of the WordPress MCP adapter (recent versions of WooCommerce do this).
The Abilities API init event fires only once per request; when WooCommerce or
an addon triggered it before the adapter could register its meta-tools, the debug
log filled with repeated “ability does not exist” notices on every wp-admin page
load and Lola’s IDE/MCP connection could stop working. LolaCore now registers
the MCP protocol meta-abilities at the earliest hook priority and skips tools
that are not yet available.
#### 1.8.5
* Feature: The Addons screen now shows the free LolaCore bridge addons (for ACF,
SEO, and Statistics) even before you install them, each with a one-click install
from WordPress.org. Until now only installed addons appeared, so there was no
way to discover the free ones from inside Lola.
* Docs: New conversation-led opening for the plugin description that shows how
Lola uses persistent memory, plus a clearer short description and search tags.
No functional changes to the agent.
#### 1.8.4
* Docs: Rewrote the readme to explain more clearly what LolaCore does and the problem
it solves (admin fatigue). No functional changes to the plugin.
#### 1.8.3
* Fix: Improved compatibility with hosting security plugins and firewalls. Chat
messages are now sent as plain text, which prevents some security suites from
blocking WordPress REST API requests on affected hosts — an issue that could
interfere with Application Password management and MCP connections.
* Improvement: When a hosting firewall blocks a chat message, Lola now explains
what happened and what to do, instead of showing a generic connection error.
#### 1.8.2
* Fix: Free bridge addons (e.g. LolaCore for ACF, LolaCore for Elementor) now show
a green **FREE ADDON** badge in the What Lola Can Do ability panel, matching
the premium addon label treatment.
#### 1.8.1
* Fix: Chat now accepts HTML and JavaScript code snippets (e.g. WPCode tracking
scripts with `