LolaCore – AI Admin Agent
Lola is an AI agent in your wp-admin that runs WordPress and WooCommerce from chat. She remembers your site and asks before every change.
Will this break my store?
What the WordPress.org registry says about keeping LolaCore – AI Admin Agent running.
Tested to 7.0.2
Tested against the WordPress branch in use today.9 days ago
8.0
Your host must be running at least this version.7.0
1
A single maintainer. Worth knowing if the plugin is load-bearing for your store.Maintenance & trust
Scored on how LolaCore – AI Admin Agent is looked after — not on how many stores run it.
Maintenance
35 / 35WordPress compatibility
20 / 20Support responsiveness
Not enough dataMerchant satisfaction
Not enough dataListing transparency
10 / 10Ratings
No one has rated this plugin on WordPress.org yet. That is a statement about the ratings page, not about the plugin — plenty of well-kept plugins never collect them.
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, 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.
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. 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.
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. Store tools with examples: WooCommerce abilities.
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.
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.
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.
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.
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: manage your Elementor pages and templates from chat
- LolaCore for ACF: read and write Advanced Custom Fields in plain language
- LolaCore for SEO: audit and edit your SEO without opening another panel
- LolaCore for Forms: work with your forms and their entries from the chat
- LolaCore for Statistics: ask about your traffic and get the number, not a dashboard
- LolaCore for FSE: a block and template builder for block themes
Browse them all: 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: 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 | Terms of Use | Privacy Policy
– Anthropic – https://anthropic.com | Terms of Service | Privacy Policy
– DeepSeek – https://deepseek.com | Terms of Use | Privacy Policy
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 | Terms of Service | 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 | API Documentation
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 | Terms of Service | Privacy Policy
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.
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.
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.
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.
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.
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.
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.
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.
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.
Deactivation clears scheduled cron events but preserves all your data. Uninstalling the plugin permanently deletes all database tables and stored options. Your choice.
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.
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.
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.
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.
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
Plugin details
Tags on WordPress.org