LolaCore Documentation
Everything you need to install, configure, and use LolaCore and its addons. 66 free abilities · 9 domains · 143 with Elementor (159 with Pro) · 334 with every addon (350 with Pro).
Foundation
Before you install anything, these documents explain what LolaCore actually is and why it works the way it does.
What is LolaCore?
LolaCore is an AI agent that lives inside your WordPress admin and executes tasks on your site. It doesn't just talk about them.
You open the chat inside wp-admin. You type what you need. Lola reads your site, shows you exactly what she's going to do, waits for your confirmation, and executes. No switching between twelve admin screens. No copying plugin names into ChatGPT and hoping for relevant advice. No instructions to follow yourself.
Lola didn't suggest you update your plugins. She did it.
Agent vs. chatbot
Most "AI for WordPress" tools are chatbots with WordPress knowledge. They read documentation, generate advice, and hand the work back to you.
LolaCore is an agent. It has tools connected to your actual site. When you ask about your WooCommerce orders, it queries your real database, not a generic explanation of how WooCommerce works. When you ask it to create a coupon, it creates it. When you ask it to deactivate a vulnerable plugin, it deactivates it.
A chatbot tells you what to do. An agent does it with you.
What Lola can do (free core)
The free LolaCore plugin gives Lola 66 abilities across 9 domains:
| Domain | What it covers |
|---|---|
| Site Diagnostics & Security | Security audits, plugin vulnerability checks, SEO diagnosis |
| Plugin Management | List, update, activate, deactivate, install, bulk update |
| Content & Metadata | Create and edit posts and pages, manage metadata, export content |
| WooCommerce Operations | Products, orders, customers, coupons, categories, reports |
| User Management | Roles, capabilities, create and edit users |
| Database & Cache | Optimize tables, clean expired data, purge cache |
| Taxonomies & Media | Categories, tags, comments, upload and delete media |
| Themes & Settings | Switch themes, update site options, manage menus |
That's the free plugin. No premium tier, no trial, no limited version. Install it and all 66 abilities are yours.
Persistent memory
Every other AI tool you've used forgets your site the moment you close the browser tab. Lola doesn't.
She remembers which plugins you have, what you updated last month, why you disabled that caching plugin, what your client prefers for their homepage layout. Not as a log you have to scroll through, but as active context that shapes every response.
Open a new session two weeks later and Lola picks up where you left off: "Last time we talked, you were migrating the blog categories. Three were pending. Want to continue?"
This memory compounds. Session 1 she's useful. Session 10 she knows your patterns. Session 50 she knows your site better than you do.
Anti-sycophancy
Most AI tools are trained to agree with you. Lola is trained to protect your site.
She won't tell you your plugin choice is great if it has three known vulnerabilities. She won't tell you a database cleanup made your site noticeably faster if it didn't. If you push back and override her recommendation, she executes your decision and logs her objection for the record.
The confirmation rule
Every action that modifies your site goes through a confirmation step. Lola shows you what will change, how many records are affected, and what the current values are. You review. You confirm. Then she executes.
Read-only actions, queries, audits, reports, run immediately. They don't change anything, so they don't need confirmation.
Destructive actions without a backup in place? Lola refuses until you have one.
What LolaCore is NOT
Not a front-end editor. Lola works inside wp-admin. She can create and edit content, but she can't visually rearrange your Elementor layouts or drag blocks around in the block editor.
Not a server administrator. Lola is confined to WordPress. She cannot access your hosting control panel, SSH into your server, or edit files over FTP. This is by design, and it's also what keeps her safe.
Not a general-purpose AI assistant. Ask Lola to write a blog post and she'll write and save a draft. Ask her to explain quantum physics and she'll tell you that's outside her scope. She only does things connected to your WordPress site.
Not a service that stores your data. All of Lola's memory, logs, and configuration live in your WordPress database. Nothing is sent externally except to your chosen AI provider (Anthropic, OpenAI, or DeepSeek), and only when you send a message.
Not a replacement for developers on complex projects. Lola handles the administrative and operational work that takes up time every week. For custom plugin development or complex migrations, you still need a developer.
Who LolaCore is for
WooCommerce store owners who want to manage orders, check sales, and update their store without navigating WooCommerce's interface every time.
Site administrators who do plugin updates, security audits, and content management as part of their regular workflow.
Freelancers and agencies managing multiple client sites, who want to delegate the repetitive administrative work to something that remembers each site's history.
Next: How Lola's Memory Works
How Lola's Memory Works
You open ChatGPT. You paste your plugin list. You explain your site setup. You describe what happened last week. You get a useful answer. You close the tab.
Next week, you start over. Same paste, same explanation, same context-building from scratch. The tool has no idea it's talked to you before.
LolaCore is built differently.
What Lola remembers
Lola stores facts about your site, your decisions, and your preferences in a dedicated table in your WordPress database. Not a chat log. Structured memory with types, importance scores, and timestamps.
The kinds of things she remembers:
- Your active plugins, WooCommerce configuration, PHP version, what broke after which update
- Why you disabled that caching plugin, which products you excluded from the last sale, that you always want Elementor excluded from bulk updates
- Your store's seasonal patterns, who your top customers are, what campaigns you've run
- Plugin pairs that caused problems last quarter, snippets that had to be rolled back
- How technical you like the responses, what level of detail you want in reports
None of this requires you to explicitly tell Lola to remember something. She infers what's worth saving from the work you do together. You can also tell her directly: "Remember that we're moving to a new theme in June" and she will.
How the memory stays useful over time
A log that grows forever becomes noise. Lola's memory doesn't work like a log.
Each fact has a relevance score that evolves over time. Facts you reference often stay sharp. Facts that haven't come up in months fade naturally. The system doesn't delete them, it deprioritizes them so they don't clutter your active context.
Think of it like a colleague who's worked with you for a year. They don't recite everything that ever happened before answering your question. They recall what's relevant to what you're asking right now, weighted by what you've revisited together.
Two things override the decay:
Importance. Some facts are marked high-importance when they're saved. A plugin conflict that took three hours to diagnose. A client preference that affects every session. These stay accessible longer.
Pinning. You can explicitly pin any fact to make it permanently available. Pinned facts are always part of Lola's context, regardless of how long ago they were created.
What "context" means in practice
When you start a new session, Lola doesn't load your entire memory history. That would be slow and wasteful. Instead, she loads the facts most relevant to what you're doing.
She scores each memory fact against your current message and selects the ones that match. A question about WooCommerce orders surfaces your WooCommerce history. A question about plugin updates surfaces your update preferences and conflict history. A generic "what should I work on today?" surfaces your most recent and highest-priority context.
The result: Lola arrives at each conversation already knowing the parts of your site's history that matter right now. You don't have to re-explain anything she's already learned.
The compounding effect
This is the part that takes a few sessions to feel but changes how you work once you do.
Session 1: Lola runs the initial scan and knows your site's current state. She's useful immediately.
Session 5: She knows which plugins you prefer to handle manually, that you run a WooCommerce store with a seasonal spike in November, and that you prefer concise answers over long explanations.
Session 15: She remembers the plugin conflict from last month, the content structure decisions you made in March, and that you've been migrating from one theme to another. When you ask about the theme, she starts from where you left off.
Session 30: She knows your site's history better than most of the people who've worked on it. You stop asking "do you remember when..." because she does.
A real example across sessions
Session 1 — November
Session 2 — January
Lola connected the Black Friday decision from November, the December sales data, and the Gift Pack creation in one response, because all of it is in memory.
Memory and addons
When you install addons, the memory spans all of them. Lola doesn't maintain separate memories for WooCommerce Pro and Fluent Support. She maintains one memory of your business.
A customer who opened a support ticket in Fluent Support last month and just placed a large order in WooCommerce: Lola can see both when you ask about that customer. This cross-addon memory is what makes a question like "which of my at-risk customers have open support tickets?" answerable, because the answer requires connecting data from two different systems.
Managing your memory
You have full control over what Lola remembers.
- View memory: Ask "what do you remember about my WooCommerce setup?" and she'll show you the relevant facts.
- Add a fact: Tell Lola something directly. "Remember that this site belongs to a client." She'll store it.
- Correct a fact: "That's outdated, we moved to a new host in April." She'll update it.
- Export memory: The settings panel lets you export your full memory database for backups or migration.
- Wipe memory: Clear everything from the maintenance section of Settings. Use this if you're repurposing the plugin for a different site.
Your data stays in your database
Everything Lola remembers lives in a table in your WordPress database (wp_lolacore_memory). It never leaves your server. It's not synced to any LolaCore service, not used to train any model, not accessible to anyone other than you.
If you uninstall LolaCore, the uninstall routine removes all plugin data including the memory tables. Nothing is left behind.
Why Lola Disagrees With You
Every AI assistant you've used before Lola was trained, at some level, to make you feel good about your choices.
You suggest a plugin, it finds the positives. You ask if your plan is good, it lists reasons it could work. You push back on a warning, it backs down. The path of least resistance is agreement, and agreement is what keeps users happy in the short term.
The problem is that your WordPress site doesn't care about your feelings. A plugin with three unpatched vulnerabilities is dangerous whether or not the AI validated your decision to install it. A bulk price update with a typo costs you real money whether or not the AI told you it looked great.
Lola is trained differently. Her loyalty is to your site's integrity, not to your comfort.
What anti-sycophancy looks like
Lola has formed opinions. She shares them, even when you didn't ask.
She didn't say "sure, here's how to install it" and let you figure out the vulnerabilities later. She told you what she found, explained why it's a problem, and offered the better path.
It applies across every domain. Ask about your coupons and she won't tell you they're working because you created them. She'll tell you which one works and which one is eating your margin.
What Lola will refuse outright
Some actions require a verified backup before Lola will execute them. This isn't a preference. It's a hard stop.
Bulk deletion of content, database operations that can't be undone, removing plugins with active transactional data: for these, Lola checks whether a recent backup exists. If it doesn't, she won't proceed.
This isn't caution for caution's sake. It's the behavior you'd want from any competent person with access to your database.
The override pattern: you're always in control
Lola is not a gatekeeper. She can't lock you out of your own site.
When she disagrees, she says so clearly. If you hear her out and still want to proceed, she will execute your decision. She won't ask three times. She won't add passive-aggressive disclaimers to the output.
But she will log her objection.
Every time you override a Lola warning, she saves a record: the date, the risk she identified, what she recommended instead, and what you chose. Three months later, if something goes wrong that connects to that decision, the record is there. Not to hold it over you, but as your audit trail of what was decided and why.
Honest about results
Anti-sycophancy isn't just about disagreeing with your plans. It also means not inflating what she's done.
She didn't tell you your site is noticeably faster because you wanted the cleanup to work. She told you the actual impact and pointed at the real problem.
When she says something helped significantly, you can trust that it did. When she says an action had minimal impact, you know not to waste time on it.
What Lola is NOT doing
She's not blocking your autonomy. You can override any warning. The site is yours. Her job is to inform, not to control.
She's not being negative for the sake of it. When something looks good, she says so. When a plugin is clean, she'll tell you. When your sales numbers are strong, she'll tell you that too, with the actual numbers.
She's not applying one-size-fits-all rules. A warning that makes sense for a 50,000-visitor e-commerce site might not apply to a personal portfolio. Lola calibrates her concerns to your actual context.
How to get the most from it
Work with the pushback, not against it. When Lola flags something, ask her to explain it. The context she provides is often more useful than the original action you were asking about.
If you think she's wrong, tell her. She can be wrong. She doesn't have access to information outside your WordPress database and the AI's training data. If you override her and she was wrong, no harm done and she learns from the correction.
If she's right and you override her anyway, the decision and its context are recorded. Future-you will thank present-you for having that record.
Working With Lola Efficiently
Lola is built around a persistent memory that carries context between sessions. That's the feature that makes her fundamentally different from other tools. And it has a practical consequence that changes how you work: the session is not the unit of work. The task is.
You don't need to stay in one long conversation to get something done. You can close a session mid-task, come back tomorrow, and Lola will have the context she needs to continue. The memory is the thread, not the conversation window.
Focused sessions work better than marathon sessions
The best sessions with Lola have a clear scope: one task, one domain, one outcome.
- "Update my plugins and run a security audit."
- "Update the product prices for the winter sale."
- "Check the open support tickets and draft responses for the ones from this week."
These complete cleanly. The context stays tight, Lola stays precise, and at the end you know exactly what was done.
Long, wide-ranging sessions where you're jumping between plugin management, content edits, WooCommerce questions, and memory management work, but they're less efficient. As the conversation grows, there's more context to carry and responses slow down. When a session starts feeling unwieldy, that's the signal to wrap it up, start a fresh one, and let Lola's memory carry the thread.
How to start a session well
You don't have to re-explain your site every time. Lola already has that context from memory.
Good session openers:
- "Let's do the weekly plugin check."
- "I need to update prices for the Electronics category before the weekend."
- "What's in the open ticket queue?"
That's it. She knows your site. She knows your history. She loads the relevant context and starts from there.
If there's something specific she should know before you start, a new constraint, a time-sensitive situation, something that changed since your last session, tell her at the top:
That's now in memory. It applies to this session and every session after.
Let memory do the briefing
The first time you do a recurring task with Lola, she might ask clarifying questions. That's normal, she's building context. The second and third time, those questions disappear. She already knows your preferences.
After the first bulk update session, she knows you always exclude Elementor. After the first WooCommerce report session, she knows you track revenue by category, not by product. After the first security audit, she knows you already reviewed the flagged items and decided to keep that one plugin despite the warning.
You build this context naturally, just by using the tool. Each session is faster than the last because Lola already knows more.
When to start a new session vs. continue the current one
Start a new session when:
- You've completed the task you came to do
- You're switching to a completely different domain (finished plugin updates, now want to work on content)
- The current session has gotten very long and responses feel slower
- You're coming back the next day
Stay in the current session when:
- You're in the middle of a multi-step task that Lola is orchestrating
- Lola is waiting for a confirmation and you need to give it
- You're iterating on something: adjusting a batch operation, refining a draft
There's no penalty for starting a new session. Continuity is built into the memory, not the conversation.
Prompts that work well
For audits and diagnostics:
- "Run a security audit and tell me what actually needs my attention."
- "Which plugins haven't been updated in over 90 days?"
- "Show me orders that need action."
For batch operations:
- "Update all plugins except Elementor. Show me the list first."
- "Raise prices 15% across the Winter Gear category. Show me examples before you apply it."
For reports:
- "How much did we sell this month vs. last month?"
- "Which products are generating the most revenue this quarter?"
For getting unstuck:
- "What was the last thing we worked on with the navigation menu?"
- "What do you remember about the plugin conflict we had last month?"
- "What were the pending items from our last session?"
What to do when Lola gets something wrong
She will occasionally get something wrong. The right response is to correct her directly:
She'll update her understanding for the current session and, where appropriate, correct the memory for future sessions. Direct correction is more efficient and produces better memory than working around errors or starting over.
Knowing when you've hit a boundary
Lola will tell you when something is outside what she can do. She won't fake it or try to work around it in ways that could cause problems.
"I can't access your server configuration directly, that's outside WordPress's scope. But I can check your PHP settings from within WordPress."
"I don't have access to your email inbox, so I can't read the order notification. Share the order number and I'll pull it from WooCommerce."
When she says she can't do something, take it at face value.
The Ecosystem Effect: When Addons Work Together
Each LolaCore addon gives Lola a new set of tools for a specific domain. WooCommerce Pro for your store. WPCode Snippets for custom code. Fluent Support for your helpdesk.
Used individually, each addon is already significant. But something different happens when Lola has access to two or three addons at once: she starts making connections between them that no individual tool could make, and that no human switching between tabs would easily notice.
This isn't a designed feature that had to be built. It's an emergent property of how the system works, one AI with persistent memory and access to multiple domains simultaneously. The connections happen because Lola sees the whole picture.
A real example: the ticket that needed order data
A customer opened a support ticket: "I requested a refund three days ago and my card hasn't been credited yet."
Without cross-addon access, the support workflow looks like this: read the ticket in Fluent Support, switch to WooCommerce, search for the order, find the refund record, check the status, switch back to Fluent Support, draft the response manually.
With both addons active, Lola handles the whole chain:
Lola didn't read the ticket and wait for you to look up the order. She read the ticket and looked up the order herself, because she has both systems available in the same conversation. The response she drafts includes the exact refund date, the amount, and the correct timeline, all pulled from real data.
Lateral reasoning across domains
Lola doesn't treat each addon as an isolated toolset. She sees the whole ecosystem and reasons across it, including cases where the goal is achievable through a different route than the one you asked for.
A practical example: you want checkout to auto-complete orders that contain only virtual or downloadable products. WooCommerce doesn't have a native setting for this. Lola doesn't stop at "there's no option for that." She recognizes the goal can be achieved with a targeted WooCommerce hook and shifts to WPCode Snippets:
No explicit instruction told her to use WPCode. She knew it was available, she knew the WooCommerce hook that solves the problem, and she connected them. The goal is achievable. Lola finds the way.
The stack audit: one question, two domains
WordPress sites naturally accumulate plugins over time. Some handle critical integrations. Others do one small thing that seemed worth a separate installation at the time, a header injection, a login page tweak, a minor display behavior. After a few years, a functional site might have thirty active plugins doing very different things.
WPCode Snippets alone can tell you which single-purpose utilities could be a short snippet instead. WooCommerce Pro alone can tell you which reporting functions it covers natively. With both active, Lola can run the combined audit:
Neither addon alone could run that audit. Lola needs both to see the complete picture.
Memory as the connective tissue
The cross-addon connections aren't just real-time. They compound through memory.
WooCommerce Pro remembers your store's campaigns, your pricing decisions, your seasonal patterns. WPCode Snippets remembers the code it's written, why each snippet was created, and what behavior it changes. As these memories accumulate, Lola starts making connections that span months:
She connected the November decision to create the Gift Pack, the December sales numbers, the coupon from the Black Friday campaign, and the banner snippet used in both promotions. WooCommerce Pro's store data, WPCode Snippets' code history, and the persistent memory that tied it all together.
The pattern to internalize
The more addons Lola has active, the more she can do, not just by addition but by multiplication.
One addon gives her a domain. Two addons give her the ability to connect two domains. Three addons give her something closer to a complete picture of your business operations. The ceiling isn't the tools available in any single addon. It's the breadth of context Lola can draw from when solving a problem.
If you're running a WooCommerce store and also managing customer support and custom code: the full stack isn't just a convenience. It's the difference between an AI that handles tasks and an AI that understands your business.
Getting started with multiple addons
There's no special setup for cross-addon features. Install the addons, activate them, and Lola immediately has access to all the domains they provide.
The cross-addon capabilities appear naturally as you work. You don't need to tell Lola to cross-reference two systems. She does it when it's relevant. The first time she brings in WooCommerce order data while responding to a Fluent Support ticket, without being asked, you'll understand what this section was about.
Getting Started
Everything needed to go from zero to first conversation.
Requirements & Compatibility
| Requirement | Minimum |
|---|---|
| WordPress | 7.0 or higher |
| PHP | 8.1 or higher |
| AI provider account | Anthropic, OpenAI, or DeepSeek (one is enough) |
That's the complete list. LolaCore has no other mandatory dependencies.
WordPress 7.0
LolaCore is built on the native AI Client introduced in WordPress 7.0. This is what eliminates the dependency on third-party packages for AI communication. Everything goes through WordPress's own standardized interface.
If your site is on WordPress 6.x, LolaCore will not activate. This is a hard requirement and cannot be bypassed.
To check your version: go to wp-admin → Dashboard → Updates. The current WordPress version is shown at the top.
PHP 8.1
LolaCore uses several PHP 8.x language features that don't exist in earlier versions. PHP 8.1 is the minimum; PHP 8.2 and above work without issues.
To check your PHP version: wp-admin → Tools → Site Health → Info → Server.
Most modern hosting providers run PHP 8.1 or higher by default. If yours doesn't, the PHP version can usually be changed in your hosting control panel, the process varies by host.
An AI provider account
LolaCore doesn't include an AI model. You connect your own account from one of three supported providers:
- Anthropic: Makes Claude (Sonnet, Opus, Haiku). Strong reasoning, excellent at following complex instructions.
- OpenAI: Makes GPT-4o and related models. Widely used, extensive documentation, broad capability.
- DeepSeek: Makes DeepSeek V4 models. Capable reasoning models with competitive pricing.
You only need one. All three work with the full LolaCore feature set. You can switch providers at any time without losing your memory or configuration.
What LolaCore does NOT require
- No Composer or npm. No build tools, no terminal access, no developer setup. Install and activate like any WordPress plugin.
- No special hosting. LolaCore runs on shared hosting, VPS, managed WordPress hosting (WP Engine, Kinsta, Flywheel), or any environment that meets the WordPress and PHP requirements.
- No external database. All memory, logs, and configuration live in your existing WordPress database, in five dedicated tables.
- No account with LolaCore. The free core plugin requires no registration, no account, and no API key from us. You bring your own key from your AI provider.
- No constant internet connection. Lola only makes external requests when you send a message in the chat. Site scanning, memory reads, and settings changes happen locally.
Optional: WooCommerce
The WooCommerce domain (13 abilities) activates automatically when WooCommerce is installed and active on your site. If WooCommerce isn't present, the domain is simply not available, no error, no warning, no impact on the rest of LolaCore.
Addon requirements
| Addon | Requires |
|---|---|
| WooCommerce Pro | LolaCore core + WooCommerce active + valid license |
| WPCode Snippets | LolaCore core + WPCode active + valid license |
| Fluent Support | LolaCore core + Fluent Support active + valid license |
Addons validate their dependencies at activation. If a required plugin is missing, the addon shows an admin notice and waits, it doesn't cause errors.
Multisite
LolaCore is designed for single-site installations. Multisite compatibility is not supported in the current version.
Next: Installing LolaCore
Installing LolaCore
Before you start, confirm your site meets the requirements: WordPress 7.0+ and PHP 8.1+. Check wp-admin → Tools → Site Health if you're not sure.
Step 1: Install from WordPress.org
- In your wp-admin, go to Plugins → Add New Plugin
- Search for LolaCore
- Click Install Now
- Click Activate
No configuration wizard. No setup form. That's the full installation.
Alternative: manual install. Download the plugin zip from wordpress.org/plugins/lolacore, then go to wp-admin → Plugins → Add New Plugin → Upload Plugin. Upload the zip and activate.
Step 2: Lola appears
The moment LolaCore activates, a floating chat widget appears at the bottom center of your wp-admin. You don't have to go looking for her. She shows up.
At the same time, she starts scanning your site in the background. Within 60 seconds, the scan collects:
- WordPress version, active theme, and pending updates
- All installed plugins with their versions and update status
- PHP version and server configuration
- Database size and health
- SSL status and basic security configuration
- WooCommerce setup (if WooCommerce is active)
- Content counts and user roles
This is what gives Lola her initial context. Before you've typed anything, she already knows your site.
Step 3: Connect your AI provider
If you haven't configured an AI provider yet, the chat window will show a prompt asking you to set one up. Click the button: it takes you directly to the WordPress 7.0 AI settings screen, where the supported providers are already listed and ready to configure.
Paste your API key for your chosen provider (Anthropic, OpenAI, or DeepSeek) and save. That's all.
Once your key is saved, come back to the chat window and start talking.
Step 4: Choose your model (optional)
In wp-admin → Lola → Settings → General, you'll find a dropdown listing all models available for your configured provider. Select the one you want to use.
If you don't select a model, LolaCore uses the first available model in the list. You can change this at any time, the switch takes effect on your next message.
Step 5: Your first conversation
You don't need a specific prompt. Lola already has context from the scan. A simple starting point:
She'll give you a current snapshot: WordPress version, active plugins, any pending updates, WooCommerce status if applicable, and anything that caught her attention. From there, ask her to do anything. The 66 core abilities are available immediately.
Working with the chat widget
Drag it anywhere. The floating widget starts at the bottom center of your screen, but you can drag it anywhere that's convenient. It remembers its position.
Minimize vs. close. Minimizing the chat collapses the window to just the avatar, the session stays active in the background. Closing the chat (X) ends the session. When you click the avatar to reopen, a new session starts. Either way, Lola's memory carries everything over.
Resize the window. The chat window is resizable. Drag the edges to make it wider or taller to fit your working style.
What's created in your database
LolaCore creates five tables in your WordPress database on activation:
- wp_lolacore_memory — Lola's persistent memory facts
- wp_lolacore_log — History of all executed actions
- wp_lolacore_sessions — Chat session metadata
- wp_lolacore_messages — Conversation history
- wp_lolacore_config — Settings and scan data
These tables use your WordPress table prefix. On sites with a custom prefix, the prefix adjusts accordingly.
Uninstalling
If you ever uninstall LolaCore, the uninstall routine removes all five database tables and all plugin data. Nothing is left behind.
Deactivating without uninstalling leaves everything intact, which is useful if you plan to reactivate later.
Next: Activating Your License
Activating Your License
The LolaCore core plugin is free and doesn't require a license of any kind. Premium addons, WooCommerce Pro, WPCode Snippets, and Fluent Support, each require an active license. The license is per site, per addon, and renews annually.
Finding your license key
When you purchase an addon from lolacore.com, Lemon Squeezy (our payment and license platform) sends your license key immediately by email. Check your inbox and spam folder for a confirmation email from Lemon Squeezy. Your key is in that email.
Each addon has its own key. If you purchased the bundle, you received two keys: one for WooCommerce Pro and one for WPCode Snippets.
Activating an addon license
Before activating, make sure:
- The LolaCore core plugin is installed and active
- The addon plugin is installed and active
- Any required third-party plugin is installed and active (WooCommerce for WooCommerce Pro, WPCode for WPCode Snippets, Fluent Support for Fluent Support)
Then:
- Go to wp-admin → Lola → Settings
- Scroll to the What Lola Can Do section, you'll see your installed addons listed with a "Manage license" link beneath each one
- Click Manage license for the addon you want to activate
- Paste your license key and click Activate
Activation is instant and requires an internet connection (the key is verified with lolacore.com). Once activated, the addon's full capabilities are immediately available.
Activating the bundle
If you purchased the bundle, activate each addon separately. Both use different keys and each activation is independent. The order doesn't matter.
What an active license gives you
- Plugin updates delivered via the standard WordPress update mechanism (wp-admin → Dashboard → Updates)
- Support through the LolaCore support system
What happens when a license expires
If you don't renew before the expiration date:
- The addon stops working when the license expires
- The addon's abilities disappear from Lola's available tools
- Your data stays intact. WooCommerce orders, WPCode snippets, Fluent Support tickets are unaffected
- Lola's memory, including everything she learned while the addon was active, stays in your database
If you renew later, reactivating the license restores full functionality immediately, including the memory context Lola built while the addon was previously active.
Managing your subscription
Renewals, cancellations, payment method changes, and invoice downloads are all handled through the Lemon Squeezy customer portal. The link to your portal is in your original purchase confirmation email.
If you can't find the email, access the portal directly at app.lemonsqueezy.com using the email address you purchased with.
Transferring a license to a different site
Licenses are single-site. If you move your site to a new domain, deactivate the license from the current site first (wp-admin → Lola → Settings → Manage license → Deactivate), then activate it on the new site.
Troubleshooting
"License key not found." Check for typos. License keys are case-sensitive. Copy and paste directly from your email rather than typing manually.
"This key is already in use." The key is active on another site. Deactivate it there first, or contact support if you don't recognize the site it's registered to.
"Could not connect to license server." Your server may have outbound HTTP requests blocked. Check with your hosting provider that wp-admin can make external HTTPS requests.
The addon is installed but the "Manage license" link doesn't appear. The addon's required dependency may not be active. Check that the third-party plugin it requires is installed and activated.
Connecting Your AI Provider
LolaCore doesn't include an AI model. It connects to whichever providers you've configured in the WordPress AI Connectors panel, the native provider management screen that WordPress 7.0 introduced.
This setup is independent of LolaCore. If you've already configured a provider before installing LolaCore, Lola detects it automatically. If you deactivate and reactivate LolaCore, or uninstall and reinstall it, your provider configuration is unaffected. It lives in WordPress, not in the plugin.
When you send a message in the chat, LolaCore routes it to your selected provider and returns the response. The conversation goes directly from your WordPress site to your provider's servers. You pay your provider directly, at their standard rates, with no markup from us.
Where to configure your API keys
Go to wp-admin → Settings → AI (or search for "AI" in the wp-admin menu). This is the WordPress 7.0 AI Connectors panel, where you add and manage provider connections.
LolaCore can see any provider you connect here. You can configure one provider or several, all of them become available for model selection in LolaCore's settings.
The three supported providers
Anthropic makes the Claude family of models (Sonnet, Opus, Haiku). Claude has strong reasoning capabilities and follows complex, multi-step instructions reliably, both qualities that matter for an agent executing real actions on your site.
Get a key: console.anthropic.com → Create an account → API Keys → Create Key. Copy the key immediately (you won't see it again after closing the window).
OpenAI makes GPT-4o and related models. Widely used, extensive documentation, broad general capability.
Get a key: platform.openai.com → Create an account → API Keys → Create new secret key. Copy it immediately.
DeepSeek makes the DeepSeek V4 family. Capable reasoning models, particularly strong at structured tasks.
Get a key: platform.deepseek.com → Create an account → API Keys → Create API Key. Copy it.
Selecting your model in LolaCore
Once your provider is connected in the WordPress AI panel, open wp-admin → Lola → Settings → General.
The AI Model dropdown lists every model available across all your connected providers. If you have Anthropic and DeepSeek both configured, you'll see all their models together. Select the one you want Lola to use.
If you don't make a selection, Lola uses the first available model in the list.
Adding providers and switching models
You can connect multiple providers and switch between models at any time. Your memory, conversation history, and all LolaCore settings are stored in your WordPress database and are independent of the provider. Switching from Anthropic to DeepSeek doesn't affect anything except which API receives your next message.
Which provider should you use?
Any of them works well for the full range of LolaCore tasks. Plugin management, WooCommerce operations, content management, security audits, all run reliably across all three providers.
Where differences emerge: tasks involving complex reasoning chains (diagnosing a performance issue, running a multi-step campaign) tend to benefit from the more capable models within each provider's lineup. Simpler, high-frequency tasks (checking stock, running a quick query, creating a draft) run well on faster, lighter models.
Start with whichever provider you already have an account with. If you're new to all three, any of them is a valid starting point.
Your keys are not stored by LolaCore
API keys are managed entirely by WordPress in the AI Connectors panel. LolaCore reads the provider connection from there. It never stores your keys directly, never logs them, and never includes them in memory or any exported data.
If you ever need to rotate a key, do it in the WordPress AI panel. LolaCore picks up the change automatically.
Next: Settings Panel Reference
Settings Panel Reference
All LolaCore configuration lives in wp-admin → Lola → Settings. The panel is divided into five sections:
- General: Provider, model, and Lola's persona
- Memory: How Lola's memory behaves over time
- What Lola Can Do: Enable or disable capability domains
- Safety: Confirmation and backup requirements for write actions
- Maintenance: Scanning, exporting, and data management
General
AI Model. The model Lola uses for all conversations. The dropdown shows every model available across all AI providers you've configured in WordPress. If you have Anthropic, OpenAI, and DeepSeek all connected, you'll see all their models in a single list. The change takes effect on your next message.
If you leave this unset, Lola uses the first available model in the list.
API provider keys are not configured here. Keys are managed in the WordPress AI Connectors panel (wp-admin → Settings → AI), which is independent of LolaCore. If you reinstall or deactivate and reactivate LolaCore, it picks up the existing provider configuration automatically.
Communication Style. Controls how Lola calibrates her explanations and the level of detail she includes.
- Technical: Development terminology, shows code, doesn't explain basics. For developers who want the direct answer without context.
- Professional: Clear language, explains technical decisions without jargon. The default. Best for site owners and administrators who want to understand what's happening without needing to be developers.
- Direct: Minimal explanations, maximum action. For experienced users who know what they're doing and want Lola to act without elaborating.
This doesn't change what Lola can do, only how she communicates it.
Lola's Avatar. Upload a custom image to replace the default avatar in the chat interface. Optional.
Memory
| Setting | Default | What it does |
|---|---|---|
| Memory Decay Rate | 0.02 | How quickly older facts lose relevance. Higher = faster fade. |
| Archive Threshold | 0.1 | Facts below this score move to archive (not deleted, just inactive). |
| Max Context Entries | 20 | Max memory facts injected per conversation turn. |
| Log Retention | 90 days | How long the action log is kept. |
Leave these at their defaults unless you have a specific reason to change them.
What Lola Can Do
This section shows all available capability domains and their ability counts. Each domain can be toggled on or off. Disabling a domain removes those abilities from Lola's active toolset, she won't use them even if asked. The abilities aren't deleted; re-enabling the domain restores them instantly.
| Domain | Abilities |
|---|---|
| Site Diagnostics & Security | 4 |
| Plugin Management | 6 |
| Content & Metadata | 7 |
| User Management | 4 |
| Database & Cache | 3 |
| Taxonomies & Media | 7 |
| WooCommerce Operations | 13 |
| Themes & Settings | 8 |
Active addon licenses appear in this section as well, with their ability counts and a "Manage license" link. You can temporarily disable an addon's domain without deactivating the addon itself.
Safety
Confirm Write Actions. When enabled (default), every action that modifies your site goes through a preview-and-confirm step. When disabled, Lola executes write actions immediately without waiting for confirmation. Not recommended for most users.
Block Destructive Actions Without Verified Backup. When enabled, Lola checks for a recent backup before deleting content or running irreversible operations. Default: disabled. Enabling this adds a hard stop before destructive operations, recommended if your site has content that would be difficult to recover.
Learning Mode. When enabled, Lola explains what she's about to do before showing the action preview. Default: enabled. Useful while you're getting familiar with LolaCore. Once you're comfortable, turn it off for a more streamlined flow.
Maintenance
Re-Scan Site. Runs a fresh full scan and updates Lola's context with the current state. The initial scan happens automatically on activation; use this after a major plugin update, a site migration, or a theme switch. The scan takes under 60 seconds and runs in the background.
Export Memory. Downloads your complete memory database as a JSON file. Use this to back up Lola's accumulated context before a site migration, or to inspect what she has stored.
Import Memory. Uploads a previously exported memory JSON file. Existing memory is merged with the imported data, nothing is overwritten. Use this after a site migration to restore the memory context Lola had on the original installation.
Compact Memory. Runs the memory maintenance process manually: archives facts below the threshold score, removes duplicates, and optimizes the memory table. This runs automatically on a daily schedule, but you can trigger it manually if you want to clean things up after a long period of heavy use.
Wipe Memory. Deletes all memory facts. Irreversible. Use this only if you're repurposing the plugin for a completely different site. Lola will have no prior context after a wipe, the next session starts from scratch, with only the initial scan as a baseline.
Next: Skills
Skills
Skills change how Lola thinks about specific situations. When a conversation matches certain keywords or patterns, Lola loads short behavioral guides that shape her judgment for that specific turn.
You see the difference immediately. Ask Lola to delete 200 draft posts, and the destructive-bulk-protocol skill activates: she calculates the exact scope, offers exclusions, and shows a preview before touching anything. Ask her to write a blog post, and content-writing-craft kicks in to keep her prose away from generic AI patterns.
Skills shape judgment, not capabilities. They don't give Lola access to new data or new actions. Think of them as specialized training that activates on demand.
Built-in skills
LolaCore ships with 10 built-in skills, tested against the engine. They cover the most common gaps between what a general-purpose AI model does and what a WordPress admin agent needs to do well.
| Skill | What it does |
|---|---|
skill-author | Teaches Lola how to create valid skill files when you ask her to build one |
destructive-bulk-protocol | Forces a 4-step safety protocol before any mass deletion or purge |
wp-conventions-expert | Prevents mistakes with slugs, meta keys, post statuses, and autoload options |
block-editor-shaper | Ensures Lola uses proper Gutenberg block markup when editing post content |
action-log-narrator | Structures Lola's responses when you ask about her action history or request an undo |
code-explainer | When Lola delivers code, she explains what it does, where it goes, and how to test it |
memory-hygiene | Teaches Lola to update and archive memory facts instead of accumulating contradictions |
lolacore-self-knowledge | Gives Lola a structured way to explain what LolaCore is and how it works |
content-writing-craft | Anti-AI prose discipline for any content Lola writes for your site |
conversion-copy-strategist | Adds CRO frameworks when Lola writes commercial copy (headlines, value props, sales pages) |
You don't toggle individual skills. They're managed as a group through the master toggle. When the master is ON, all 10 are available. When it's OFF, none of them fire.
Premium addons can register their own skills through the same engine. When an addon is active and the master toggle is ON, its skills appear in the built-in list with a badge showing which addon they come from. Deactivating the addon removes its skills automatically.
How skills activate
Skills don't run on every conversation. Each skill defines triggers: keywords, regex patterns, or intent labels that match against your message. When you type something that matches, that skill's instructions get added to Lola's reasoning for that turn.
For example, destructive-bulk-protocol triggers on words like "delete", "remove", "wipe", "purge", "borra", "eliminar". If your message contains any of those words, the skill activates. If you're asking about revenue or updating a plugin, it stays dormant.
Multiple skills can activate on the same message. The engine sorts by priority and applies two safety caps:
- Maximum 5 skills per message. If more than 5 match, the lowest-priority ones are dropped.
- 6,000-character budget. Skill bodies enter whole or not at all. If the combined text exceeds the budget, the lowest-priority skill gets dropped until it fits.
Settings panel (Section 8)
Skills are configured in wp-admin → Lola → Settings, Section 8.
Master toggle: Enable LolaCore Skills. When ON, Lola loads and matches all built-in skills on every request. When OFF, the skill engine is bypassed entirely. Lola operates on her baseline instructions only.
Default for new installations: ON. Default after upgrading: OFF. LolaCore never changes behavior without your explicit consent. After upgrading, a one-time notice in wp-admin invites you to enable skills.
Performance impact: Skills add roughly 100-500ms of processing time and 5-15% to API costs per request. Most conversations trigger 0-2 skills. Simple questions like "how many orders today?" typically trigger none.
Beta toggle: Enable custom skills. A second toggle controls custom skills. Custom skills let you teach Lola new behaviors: import from external sources, create them with Lola's help (via skill-author), or drop .md files into wp-content/lolacore-skills/. Requires the master toggle to be ON. The first time you enable it, a modal asks you to acknowledge the experimental nature of custom skills.
How a skill file looks
Every skill is a Markdown file with YAML frontmatter at the top and a body below:
--- name: my-custom-skill description: Reminds Lola to check stock levels before recommending promotions. --- # Stock check before promotions Before recommending any discount, sale, or promotional campaign, check the current stock levels for the affected products. If any product has fewer than 10 units in stock, flag it explicitly and suggest adjusting the scope.
The name and description are the only required fields. Optional fields include triggers (keywords, regex, intents), conditions (required plugins, user capability, locale), always (fires on every message), priority (0-100, built-ins range 60-80), and writes_data.
The body is plain text injected verbatim into Lola's system prompt when the skill activates. Keep bodies under 1,500 characters. The engine has a shared budget, and oversized skills crowd out others.
Skill precedence
When two skills share the same name, the engine applies a fixed precedence order:
- Filesystem (
wp-content/lolacore-skills/) wins over everything - Database (imported or Lola-created) overrides addons and built-ins
- Addon-registered overrides built-ins
- Built-in (shipped with LolaCore core) is the baseline
Lifecycle of a custom skill
Custom skills follow a simple lifecycle: Inactive → Active → Archived. New skills always start inactive. You activate them after reviewing the content. Deactivating keeps the skill in the database but stops it from firing. Archiving hides it from the admin panel without deleting the data.
Lola has abilities for managing the lifecycle directly through chat:
| Ability | What it does |
|---|---|
addSkill | Creates a new skill draft (starts inactive) |
activateSkill | Turns on an inactive skill |
deactivateSkill | Turns off an active skill |
updateSkill | Modifies the content of an existing skill |
listSkills | Shows all skills with their current status |
deleteSkill | Permanently removes a skill |
Things to know
Skills don't stack unpredictably. The engine sorts by priority, caps at 5 per message, and enforces a character budget. Even with 30 custom skills loaded, Lola never gets more than 5 on a single turn.
LolaCore uses its own lightweight YAML parser. It supports plain values, inline arrays, block arrays, and nested maps up to 2 levels deep. Multiline scalars (| or >), anchors (&), aliases (*), and tags (!!) are not supported. If you paste a skill that uses advanced YAML features, the parser rejects it with a specific error pointing to the exact line.
The validator catches common mistakes before a skill enters the system. Names are auto-sanitized to kebab-case. Descriptions over 200 characters get truncated. Priorities outside 0-100 are clamped. Regex patterns are test-compiled before the skill is accepted.
The skill registry uses a two-layer cache (transient + config snapshot) that self-invalidates when filesystem changes are detected. If you add a file to wp-content/lolacore-skills/ and don't see it immediately, wait a minute for the cache to refresh, or trigger a re-scan from the Settings panel.
Next: MCP Integration
MCP Integration
MCP (Model Context Protocol) lets AI agents in code editors connect directly to your WordPress site. LolaCore ships with a native MCP server — when you connect Cursor, Claude Code, or Antigravity, the AI gets access to the same abilities Lola has in the web chat: plugin management, content editing, WooCommerce, diagnostics, persistent memory, everything.
The intelligence comes from your IDE’s own AI model. WordPress just provides the tools. No AI provider needs to be configured in WordPress, and no extra plugins are required — the MCP server is built into LolaCore and activates automatically.
What you need
- LolaCore v1.6.0 or higher installed and active on your site.
- A WordPress Application Password. Your IDE connects over HTTPS using Basic Auth — your main login is never sent.
Setup
Step 1 — Create an Application Password. Go to wp-admin → Users → Profile, scroll to Application Passwords, give it a name (e.g. “Claude Code”), and copy the value it generates. You won’t see it again.
Step 2 — Get your config. Open Lola → MCP Settings, enter your username and the Application Password, and click Generate Configs. LolaCore builds a ready-to-paste config file for each supported IDE.
Step 3 — Install the config in your IDE.
- Claude Code — save as
.mcp.jsonin your project root - Cursor — save as
.cursor/mcp.jsonin your project root - Antigravity — save as
mcp_config.jsonin your workspace
Step 4 — Verify. Ask the agent: “What WordPress version is this site running?” If it responds with your actual version, you are connected.
How it works
The server exposes three tools. Your agent uses them in sequence, automatically:
- discover-abilities — lists every ability available on your site.
- get-ability-info — returns the full parameter schema for a specific ability.
- execute-ability — runs the ability and returns the result.
You type natural language. The agent decides which abilities to call, in what order, and handles everything else.
What you can do
Everything Lola can do in the web chat is available through MCP. Both interfaces read from the same ability registry. Domain toggles in LolaCore Settings apply to both: if a domain is off, its abilities won’t appear in MCP either.
| Domain | Examples |
|---|---|
| Site Diagnostics | Security audit, SEO diagnosis, site status |
| Plugin Management | Update, install, activate, deactivate |
| Content & Metadata | Create posts and pages, edit metadata, manage slugs |
| WooCommerce | Orders, products, customers, coupons, reports |
| Users & Roles | Create users, manage roles, reset passwords |
| Database & Cache | Optimize tables, clean transients, purge cache |
| Memory | Read and write persistent facts, search context |
| Skills | Create, activate, deactivate custom skills |
Premium addon abilities — WooCommerce Pro, WPCode Snippets, Fluent Support, FluentCRM — are available through MCP when the addon is installed, active, and licensed.
Persistent memory
Memory is shared across all clients. Facts saved in the web chat are visible to the MCP agent, and vice versa. Actions executed through MCP appear in the same action history the web chat uses.
Start a task from your IDE, close it, open the web chat the next day — Lola picks up where you left off. The memory is the thread, not the client.
Security
The MCP endpoint requires HTTPS. Every request authenticates with the Application Password — the agent operates with exactly the permissions of that WordPress user. To revoke access, delete the Application Password from wp-admin → Users → Profile → Application Passwords. The disconnection is immediate.
Every action executed through MCP is logged in the same action history as web chat actions, including the ability name, parameters, result, timestamp, and which client triggered it.
Troubleshooting
401 Unauthorized. The Application Password is wrong or was deleted. Generate a new one from wp-admin → Users → Profile.
Ability not found. The domain is disabled in LolaCore Settings, or the addon providing it is not installed, active, or licensed.
Connection refused or timeout. Your hosting may block REST API requests from external clients. Check that /wp-json/ is accessible, and that security plugins aren’t blocking authenticated REST requests.
Write operations return errors. The WordPress user associated with the Application Password needs manage_options capability. LolaCore requires administrator-level access for write operations.
Next: Plugin Builder
Plugin Builder
Tell Lola what you need in plain language. She builds a working plugin for your site, saves it in your library, lets you confirm it activates correctly in a safe test environment, and installs it on your live site when you say so.
You are the product owner. Lola is the engineer. You know what your store or site needs. She figures out how to build it, fits it to your theme and WooCommerce setup, and refines it with you until it works the way you want.
This is not Plugin Management, which installs plugins from WordPress.org. Plugin Builder creates your plugins — saved in Lola → My Built Plugins, versioned, and yours to iterate in chat.
What it is (and isn’t)
It is:
- A way to get a plugin that does one specific thing for your site, with a settings panel you can adjust — without installing a full-featured plugin and using 5% of it.
- An MVP-first workflow: the first delivery is a starter version; you polish it in chat until it matches what you want.
- A quick test in WordPress Playground before anything touches your live site — to confirm it activates and the settings page looks right.
It is not:
- A replacement for professional plugins whose full feature set you actually use. If a plugin does 30 things and you need 25 of them, that plugin belongs on your site.
- A tool for sprawling multi-plugin projects. Each build is one self-contained plugin with a focused scope.
- Automatic go-live. Lola installs the plugin inactive until you choose to turn it on.
- A substitute for testing on your real store. Playground cannot replicate your products, orders, shipping rules, or theme.
- Available for direct install on WordPress multisite (Playground testing still works).
For the general rule that Lola does not place custom code on your site, see What Lola Cannot Do. Plugin Builder is the deliberate exception.
How it works: MVP first, then polish
Plugin Builder is designed around iteration, not one-shot perfection. Lola reads your site, builds a working first version, and you refine it together until the result matches what you need. Most plugins settle in one to four rounds.
The recommended flow:
- Describe what you need, be specific. The best requests read like a short brief: what customers should see, where they should see it, and what you want to control from the settings panel. Lola reads your site first so the plugin fits how your store is actually built.
- Approve a mini-plan (optional but worth it). Lola may summarize what she found on your site and propose scope before building. Agreeing on the plan first usually means less back-and-forth on the first version.
- Build in the background. Generation runs in the background so your browser does not hang. You see a progress card while Lola writes the plugin, then a delivery card with your first MVP. Behind the scenes, Lola runs four internal build-and-validation procedures on every generation — you do not set them up or touch them.
- Playground, then your live site. After you save, a card appears with Open in Playground. Use it to confirm the plugin activates and the settings page looks right. Real functionality — does the bar look right on your cart, with your products and your threshold — you judge on your live site after install.
A real conversation: a free-shipping progress bar
A full-complexity request — WooCommerce dependency, admin settings, front-end display in multiple locations, live cart updates — shows what a real Plugin Builder conversation looks like.
Refining through chat
Settings like the threshold amount, messages, and colors — you adjust those yourself from the plugin’s settings page. That is what the settings panel is for.
Iteration is for everything else: problems that show up on your real site, edge cases the first version did not cover, or features you realize you need after testing with real customers. Instead of editing code, tell Lola what is happening — she diagnoses, proposes a fix, and saves a new version with a revision you can roll back from the library if needed.
Every new version resets the Playground step. Confirm activation and settings in Playground again before installing the update on your live site. After install, your live store is where you judge the real result — real products, real cart totals, real shipping rules.
Built Plugins library
Find it at wp-admin → Lola → My Built Plugins. Each entry shows version, status (saved only · installed but off · installed and active), and whether the plugin passed Lola’s activation check. Open any entry to see the generated code and your original description.
- Try in Playground — always available.
- Install — enabled only after you confirmed Playground testing for the current version.
What Playground is for (and what it isn’t)
Playground opens a disposable WordPress site in your browser with your plugin installed and activated. Nothing touches your live site.
Use Playground to check:
- The plugin activates without errors (no white screen, no crash).
- The settings panel exists where you asked for it — on/off toggle, threshold field, message boxes, color options.
- The basic structure matches what you specified.
Do not use Playground to sign off on final store behavior. Your plugin was built for your site: your shipping zones, your currency, your cart layout, your products. Playground is a generic sandbox. Even when WooCommerce is installed with sample products, that is not your catalog or your customer’s real journey. Real validation happens on your live site after install and activation.
For WooCommerce plugins, Playground can install WooCommerce and sample products so you can open the cart and settings — enough to confirm the plugin boots, not enough to replace testing on your store.
Installing on your live site
When install is allowed, Lola copies the plugin onto your site. It stays off until you choose to activate it. The confirmation may recommend a recent backup if Lola detects an active backup plugin — that is advice, not a requirement. If you already installed an earlier version, the new one overwrites it, and Lola warns you before she does.
After install, the chat card offers Activate now or Not yet. This is when you run the real test: your cart, your products, your thresholds.
Multisite: direct install is not available. Use Playground for the activation check; deploy manually on multisite networks.
Things to know
Think in versions, not perfection. The first save is the starting point. Plan for one to four refinement rounds on anything non-trivial.
Playground ≠ your store. It answers “does this plugin boot and have the settings I asked for?” Final behavior is always judged on your live site.
Deleting from the library does not uninstall. If you already installed the plugin, remove it from Plugins in wp-admin separately.
Revisions are your safety net. Each update creates a revision on the library entry. Roll back from the edit screen if an iteration goes wrong.
Lola won’t install before you confirm Playground. If you ask to skip testing, she’ll point you to the saved plugin card instead.
Not a substitute for WPCode Snippets. For one-off code snippets without a full plugin, see the WPCode Snippets addon. Plugin Builder is for standalone plugins you own, version, and refine as a unit.
Using Cursor or Claude Code? Plugin Builder works from there too — same library, same rules. See MCP Integration.
Quick reference: what Lola can do here
For consultants and developers who want a quick overview. Store owners can skip this — the sections above already cover the flow.
| What Lola does | Read or write |
|---|---|
| Reads your site structure before building | Read |
| Lists plugins you’ve already built | Read |
| Loads a plugin’s code and original description | Read |
| Checks whether what’s installed matches the latest saved version | Read |
| Opens a Playground link to test activation | Read |
| Builds a new plugin from your description | Write |
| Applies changes you request to an existing plugin | Write |
| Installs the plugin on your site (inactive until you activate) | Write |
| Removes a plugin from your library | Write |
Every write action uses Preview → Confirm → Execute — Lola shows you what she’ll do before she does it.
Next: How the Chat Works
Using Lola
How the chat works, the confirmation flow, and the full free ability set organized by domain.
How the Chat Works
The floating widget
Lola lives in a floating widget that stays accessible from anywhere in wp-admin. You don't have to navigate to a specific screen. The chat is always one click away.
The widget starts at the bottom center of your screen. Drag it anywhere that works for you. It remembers its position. Click the avatar to open the chat window. The window is resizable.
Sessions: open, minimize, close
Open session: The chat window is active and Lola is ready to respond.
Minimized: The window collapses to just the avatar. The session stays active. When you click to reopen, you're back in the same conversation exactly where you left it.
Closed (X): The session ends. When you reopen the chat, a new session starts. Lola loads relevant context from memory, so she's not starting from zero, but the active conversation thread is new.
For most workflows, minimize when you need to navigate around wp-admin and come back. Close when you're done with a task and want a clean start next time.
The confirmation flow
Every action that modifies your site follows this pattern:
- You describe what you want. Natural language, no specific syntax required.
- Lola previews what will happen: what records will change, current values, how many items are affected.
- You confirm. A single "yes" or "proceed."
- Lola executes. The action runs. Lola reports what happened.
- The action and its outcome are saved to memory and the action log.
You always see the plan before anything changes. Nothing happens behind your back.
Read vs. write actions
Read actions, queries, audits, reports, status checks, run immediately without confirmation. They don't modify anything.
Write actions, anything that creates, modifies, or deletes data, always go through the preview-and-confirm step.
"How many orders are processing?" → immediate answer, no confirmation
"Cancel order #1042" → preview first, confirm to execute
If Lola is asking for confirmation, you're about to change something. If she answers directly, you're looking at data.
Bulk operations
For bulk pricing, bulk content changes, or any operation that touches many records at once, Lola shows you representative examples before applying anything at scale.
When Lola objects
If you push back and want to proceed anyway, she will. She doesn't ask twice. But she logs the exchange, the warning she gave and the decision you made, in the action log and memory.
Dry-run mode
For complex operations, ask Lola to show you exactly what would happen without executing anything:
She'll run through the full calculation and present the results. Nothing changes until you explicitly confirm.
The action log
Every action Lola executes is recorded: what was done, when, whether it was a dry run or a confirmed execution, and whether you overrode a warning. Ask her directly:
- "What actions did you run this week?"
- "Did you change anything on the site yesterday?"
She'll pull from the log and give you a chronological account.
Site Diagnostics & Security
4 abilities for reading and assessing your site's health. All read-only. Nothing changes until you ask Lola to act on what she finds.
Site status overview
This is the same information scattered across half a dozen wp-admin screens, delivered in one response. It's also the answer Lola gives during the initial scan, which runs automatically the moment you activate the plugin.
Use this at the start of a session when you want a quick state check, or after a period of inactivity to see what's changed.
Security audit
What the audit checks:
- Plugin vulnerabilities against a vulnerability database, with a direct link to the update if one exists
- SSL and whether your site is running HTTPS correctly
- File editing: whether direct file editing via wp-admin is disabled (it should be)
- Debug mode: whether WP_DEBUG is active on a production site (it shouldn't be)
- User accounts: administrator count, recently created accounts
- Database health: expired transients, orphaned data, table optimization status
Every finding is specific to what you actually have installed. Not a generic checklist.
SEO diagnosis
What the SEO diagnosis covers: active SEO plugin detection, XML sitemap presence, missing meta descriptions, duplicate titles, robots.txt validity, noindex tags, and structured data status. This is a technical SEO health check. Lola identifies structural and configuration issues, she doesn't rewrite your copy or generate keywords.
Ability discovery
Useful when you're wondering whether a specific task is within her capabilities, or when you want to confirm an addon is active and its abilities are registered.
Acting on what the audit finds
Diagnostic abilities surface information. The action happens when you ask Lola to do something about it.
After a security audit: "Update Contact Form 7" goes to Plugin Management. "Clean the expired transients" goes to Database & Cache.
After an SEO diagnosis: "Add meta descriptions to the 12 posts that are missing them" goes to Content & Metadata.
When to run a re-scan
The initial scan runs at activation. After that, Lola updates her site knowledge organically as she works. Run a manual re-scan (Settings → Maintenance → Re-Scan Site) after a site migration, a major WordPress version update, or after installing or removing a significant number of plugins at once.
Next: Plugin Management
Plugin Management
6 abilities for complete plugin lifecycle management: auditing, searching, updating, installing, activating, deactivating, and bulk updating.
Auditing your plugins
In one response: what's installed, what needs updating, what has security issues, and what's sitting there doing nothing. The equivalent of opening Plugins, checking each row, cross-referencing a vulnerability tracker, and writing it down yourself.
Updating plugins
Single update:
Bulk update with exclusions:
Lola remembers exclusions. If you've told her before that you always skip Elementor for manual review, she'll apply that preference automatically in future sessions without being reminded.
Lola updates plugins sequentially, not in parallel. If an update causes a problem, the sequential approach makes it easier to identify which plugin was responsible.
Activating and deactivating
Lola flags the practical consequences of activation/deactivation when they're non-trivial. She gives you the one piece of information that matters before you confirm.
Searching for and installing plugins
Installation and activation are two separate steps. Lola installs, then asks about activation separately, so you can install without immediately going live if you want to review settings first.
Things to know
Lola can't update or install premium plugins that aren't on WordPress.org. Plugins distributed privately require manual updates through the plugin's own mechanism. Lola can tell you which premium plugins are installed and what version they're running, but she can't fetch updates for them.
Lola doesn't push updates without asking. Even if you say "keep my plugins updated," she won't run updates automatically. Every update session starts with your confirmation.
After a problematic update, Lola flags the issue and stops. She won't continue updating other plugins if one causes an error.
Next: Content & Metadata
Content & Metadata
7 abilities for content creation and management: querying posts and pages, reading and updating metadata, creating, editing, deleting, and exporting content.
Querying content
Creating content
Lola creates the post with the metadata you specify. Creating a post and writing the body are two separate operations you can combine or keep separate.
Editing content
Lola flags URL-changing edits because they have external consequences. She doesn't refuse, she makes sure you know what you're doing.
Managing metadata
Post meta is the invisible data attached to posts and pages: custom fields, SEO settings, WooCommerce product data, Elementor layout data, plugin-specific values.
Deleting content
Lola distinguishes between soft delete (trash) and hard delete (permanent), and makes the distinction explicit before confirming either.
Exporting content
The export is structured and readable, not the raw WordPress export XML format.
What this domain doesn't cover
Lola works with WordPress post data: title, content as stored in the database, slug, status, categories, and meta fields. She doesn't interact with the Gutenberg block editor or Elementor's visual canvas directly. If a post was built with Elementor, the content Lola can edit is the underlying WordPress content layer, not the visual layout.
Next: WooCommerce Operations
WooCommerce Operations
If you run a WooCommerce store, this is the part of LolaCore that changes your daily routine the most. All 13 abilities are included in the free core plugin.
| Ability | What it does |
|---|---|
| wcGetProducts | List and filter your product catalog |
| wcGetOrders | List orders with filters by status, date, customer |
| wcGetCustomers | List customers with filters |
| wcGetCoupons | List active and inactive coupons |
| wcGetReports | Sales reports: revenue, top products, customer activity |
| wcUpdateProduct | Update product details, price, stock status |
| wcUpdateOrderStatus | Change an order's status |
| wcCreateProduct | Create a new product |
| wcManageCategories | Create, update, and delete product categories |
| wcManageCoupons | Create, update, and delete coupons |
Your store at a glance
Order management
Product management
Coupons
What the free core doesn't cover
The 13 core WooCommerce abilities handle the daily essentials: checking your store, managing orders and products, working with coupons and categories.
What they don't include: partial refunds, bulk pricing updates, advanced analytics with period-over-period comparisons, customer segmentation, tax management, and shipping zone configuration. All of that is in WooCommerce Pro.
Next: User Management
User Management
4 abilities for user and role management: querying users, listing available roles, managing accounts, and modifying role capabilities.
Querying users
Understanding roles
Managing users
Lola explains the practical consequences of a role change, not the technical definition, but what the person will be able to do differently.
Role management
Modifying a base role affects every user with that role, not just the one you're thinking about. Lola explains the blast radius before executing.
What Lola doesn't do with users
No direct password setting. WordPress handles password resets through its own email flow. Lola can trigger a password reset email but can't set passwords directly.
No editing your own account. Lola won't modify the currently logged-in administrator account to avoid accidental lockout scenarios.
No mass user deletion. Bulk user operations that would affect many accounts at once require individual confirmation to prevent accidental data loss.
Next: Database & Maintenance
Database & Maintenance
3 abilities for database health and cache management: checking database status, running cleanup and optimization, and purging your active caching plugin's cache.
Checking database health
What accumulates over time
WordPress is designed to be safe, not minimal. Several things build up as a side effect:
Post revisions. Every time you save a post, WordPress keeps a copy of the previous version. After a few years and hundreds of edits, this can represent significant overhead. Most revisions older than a few weeks aren't needed.
Expired transients. Transients are temporary data that plugins use as a short-term cache. They're supposed to delete themselves when they expire, but this cleanup is unreliable on busy sites. Thousands sitting in the database is common and harmless in terms of data integrity, but it's dead weight.
Auto-drafts. WordPress creates an auto-draft every time you start a new post and don't save it. These accumulate silently.
None of this is a crisis. It's normal database accumulation that benefits from occasional cleaning.
Cleaning and optimizing
That last sentence matters. Lola doesn't tell you the database cleanup made your site faster if it didn't make a meaningful difference. She tells you where the actual bottleneck is.
You can also run granular cleanup if you want control over what gets removed:
Purging cache
If you have a caching plugin active (LiteSpeed Cache, WP Super Cache, W3 Total Cache, WP Rocket, or similar), Lola can clear it directly from the chat.
Useful after content changes, plugin updates, or any modification that needs to be reflected immediately across your site.
Honest about impact
Database optimization improves database efficiency. Whether it makes your site visibly faster depends on your specific bottleneck. A site that's slow because of 50 external HTTP requests per page load or unoptimized images will see minimal improvement from a database cleanup. A site where database query time is the actual bottleneck will see meaningful gains.
Lola will tell you which situation you're in. If the database isn't your performance problem, she'll point at what is.
How often to run maintenance
For most active WordPress sites, a quarterly cleanup is sufficient. Signs it's worth doing sooner: your database has grown significantly, you've installed and uninstalled several plugins recently (they often leave transients behind), or you've done significant content work with lots of saves and revisions.
Next: Taxonomies & Media
Taxonomies & Media
7 abilities across two areas: taxonomy management (categories, tags, comments) and media library operations (querying, uploading, deleting).
Working with categories and tags
Lola flags the URL consequence of slug changes separately from the display name change. They're different decisions with different implications.
Comment management
Media library
Lola always lists the specific files before deleting media. File deletion is permanent and she treats it accordingly.
Uploading media
Lola can accept file uploads directly through the chat interface. Drop the file in the chat or use the attachment button. She'll upload it to the media library and can immediately assign it as the featured image for a product or post if you specify.
Themes, Menus & Site Settings
8 abilities for site configuration: reading and updating site options, managing navigation menus, checking theme info, switching themes, and cleaning up scheduled background tasks.
Site settings overview
A complete picture of your General, Reading, Discussion, and Media settings. The screens you visit occasionally and always have to remember where to find.
Updating site options
Lola clarifies the scope of settings changes: site-wide defaults vs. individual content, what's affected immediately vs. on future content.
Navigation menus
Theme management
Theme switches on live sites have immediate visual consequences. Lola flags this clearly and recommends staging, once. If you confirm, she proceeds.
Cron job management
WordPress uses WP-Cron to run background tasks: sending scheduled emails, checking for plugin updates, running cleanup routines. Plugins register their own cron jobs, and over time, especially after installing and uninstalling plugins, these can accumulate.
Orphaned cron jobs from removed plugins run and fail silently on every scheduled interval. Cleaning them up is low-risk and keeps your scheduled task list clean.
Reference
Quick-reference documents for capability boundaries and ready-to-use prompt patterns.
What Lola Can Do: The Full Capability Map
The free LolaCore core plugin gives Lola 66 abilities across 9 domains. Every one of them is available the moment you activate the plugin. No configuration, no tiers, no upsells within the core.
Site Diagnostics & Security — 4 abilities
- getSiteStatus — Full snapshot of your site's current state.
"What does my site look like right now?" → WordPress version, plugins, PHP, DB size, WooCommerce status, SSL, pending updates. - diagnoseSeo — Technical SEO health check.
"Run an SEO diagnosis." → Sitemap status, missing meta descriptions, duplicate titles, robots.txt, structured data gaps. - auditSecurity — Plugin vulnerability scan and security configuration review.
"Audit my site's security." → Each plugin checked against vulnerability database, SSL, debug mode, file editing, admin accounts. - getDiscoveredAbilities — What tools Lola currently has available.
"What can you do right now?" → Full list of active abilities including installed addons.
Plugin Management — 6 abilities
- auditPlugins — Review all plugins: versions, update status, vulnerability flags, inactive plugins.
- searchPlugins — Find plugins on WordPress.org with real metadata (install counts, update dates).
- updatePlugin — Update a single plugin with version preview and confirmation.
- togglePlugin — Activate or deactivate any plugin, with consequences flagged if non-trivial.
- installPlugin — Install from WordPress.org, then ask whether to activate.
- bulkUpdatePlugins — Update multiple plugins in one operation with exclusion support, sequentially.
Plugin Builder — 9 abilities
- createPlugin — Generate a complete custom plugin (PHP, JS, CSS) from a plain-language description, with an automatic AI security review.
- updatePluginCode — Iterate on a built plugin: apply a change request, re-run the security review, and save a new version.
- listBuiltPlugins — List the plugins Lola has generated and saved in the Plugin Builder library.
- getBuiltPluginDetails — Read the full saved code and metadata of a built plugin.
- getInstalledPluginState — Check whether a built plugin has been written to disk and its current state on this site.
- getSiteRenderContext — Capture this site’s theme, colors, and layout so a generated plugin fits it from the first version.
- testPluginPlayground — Open a built plugin in an isolated WordPress Playground to test it safely before installing.
- installPluginLocal — Install a built plugin into this site (left deactivated), after Playground testing is confirmed.
- deleteBuiltPlugin — Move a built plugin’s library entry to trash.
Content & Metadata — 7 abilities
- getContent — Query posts, pages, and custom post types with filters (status, date, category, author).
- getPostMeta — Read all metadata attached to any post or page (SEO fields, custom fields, Elementor data).
- exportContent — Export structured content as JSON with titles, content, dates, categories, tags, and metadata.
- createContent — Create posts and pages with metadata, categories, and content in one operation.
- editContent — Update title, content, slug, status, categories, tags, or featured image.
- deleteContent — Move to trash or permanently delete, with the distinction made explicit.
- updatePostMeta — Add or update any meta field on any post (Yoast fields, custom fields, etc.).
WooCommerce Operations — 13 abilities
- wcGetProducts — List and filter your product catalog.
- wcGetProduct — Full details on a specific product: price, stock, variations, sales history.
- wcGetOrders — List orders with filters by status, date, customer.
- wcGetOrder — Full details on a specific order: customer, items, payment, status, notes.
- wcGetCustomers — List customers with filters, order counts, and total spend.
- wcGetCategories — Browse product category structure with product counts.
- wcGetCoupons — List all coupons with usage data and expiry status.
- wcGetReports — Sales reports: revenue, order count, average order value, top products.
- wcUpdateProduct — Update price, stock, status, or any product field.
- wcUpdateOrderStatus — Change an order's status, with customer email trigger noted.
- wcCreateProduct — Create a new product (as draft, with option to publish).
- wcManageCategories — Create, update, and delete product categories.
- wcManageCoupons — Create, update, and delete coupons.
User Management — 4 abilities
- getUsers — List and filter users by role, registration date, last login.
- getRoles — List available roles and explain their capabilities in plain language.
- manageUsers — Create, update, or deactivate user accounts.
- manageRoles — Modify role capabilities, with blast radius explained before any change.
Database & Cache — 3 abilities
- getDatabaseStatus — Full database health picture: size, table fragmentation, expired transients, recoverable space.
- optimizeDatabase — Clean expired transients, old revisions, auto-drafts, and optimize tables.
- purgeCache — Clear your active caching plugin's cache.
Taxonomies & Media — 7 abilities
- getTaxonomies — List and explore category and tag structure with post counts.
- getComments — Query comments by status, post, or date, with spam detection.
- manageTaxonomies — Create, update, delete categories and tags (with slug-change warnings).
- manageComments — Approve, reply to, trash, or delete comments.
- getMedia — Query the media library by type, date, or attachment status.
- uploadMedia — Upload files to the media library directly from the chat.
- deleteMedia — Remove files permanently, with file list shown before confirmation.
Themes & Settings — 13 abilities
- getOptions — Read any WordPress option from the database.
- getMenus — List and inspect navigation menus and their items, with broken link detection.
- getSiteSettings — Full site configuration overview: title, URL, language, timezone, reading settings.
- getThemeInfo — Current theme details, child theme status, available updates.
- updateOption — Update any WordPress site option.
- cleanupCronJobs — Review and remove scheduled background tasks, including orphaned entries from removed plugins.
- manageMenus — Create, edit, and update navigation menus and their items.
- switchTheme — Change the active theme, with live-site consequences flagged.
- searchThemes — Search the WordPress.org theme directory by keyword, with ratings and requirements.
- installTheme — Install a theme from WordPress.org (not activated automatically).
- updateTheme — Update a single installed theme to its latest version.
- bulkUpdateThemes — Update multiple themes at once.
- deleteTheme — Permanently delete an installed theme (the active theme is protected).
Next: What Lola Cannot Do
What Lola Cannot Do
Knowing what Lola can't do is as useful as knowing what she can. It saves time when a task is genuinely outside her scope, and it helps you find the right alternative rather than wondering why something isn't working.
These aren't workarounds waiting to be discovered. They're deliberate boundaries, most of them there for good reason.
Server and hosting access
Lola is confined to WordPress. She cannot access your hosting control panel, connect via SSH or SFTP, edit files directly on the server's filesystem, modify your PHP configuration, manage databases outside of what WordPress exposes, or restart services and flush server-level caches (Redis, Varnish).
Lola can tell you what WordPress sees (PHP version, memory limits, execution time), but she can't change those values at the server level. Anything server-level stays in your hosting panel or terminal.
Updating premium plugins not on WordPress.org
Lola can update any plugin distributed through WordPress.org, checking for updates, reviewing the changelog, and running the update with your confirmation.
She cannot update plugins distributed privately: paid plugins that deliver updates through their own license servers, plugins from private repositories, or any plugin whose updates don't come through the standard WordPress update mechanism. She can tell you which premium plugins are out of date, but the update itself has to happen through the plugin's own update system.
Frontend visual editing
Lola works in the WordPress data layer: content stored in the database, settings stored in wp_options, metadata attached to posts and pages.
Without the LolaCore for Elementor addon, she can't write to Elementor's design layer — no dragging widgets in the builder UI, but also no automated layout changes from chat. Install the free addon and she reads and writes page structure, widgets, global styles, and templates directly. Gutenberg block layout editing still requires the block editor.
Accessing external services
Lola has no credentials for external services and no way to acquire them. She cannot log into payment processors directly (she can execute refunds through WooCommerce's API, but not access your Stripe dashboard), read your email inbox, access external APIs (shipping carriers, ERPs, CRMs) unless a WordPress plugin creates a bridge, or connect to social media accounts, ad platforms, or analytics services.
If you want Lola to work with an external service, the bridge has to exist in WordPress first, usually as a plugin that integrates that service and exposes data through WordPress hooks or the database.
Custom code snippets without WPCode
Lola understands PHP, JavaScript, and CSS. She can explain what a function does, review a snippet you paste into the chat, and suggest what code would solve a problem.
A snippet is a small piece of code, a hook, a filter, a CSS rule, that runs on your existing site without becoming a separate plugin. Placing snippets like that needs the WPCode Snippets addon: with it, Lola writes the code, shows it to you for review, and registers it in WPCode with a single confirmation. Without WPCode she can still write the snippet in the chat, but you'd have to paste it in somewhere yourself.
This is not the same as building a plugin. Plugin Builder is free and built into the core, and it generates a complete, standalone plugin (its own PHP, JS, and CSS files) that you install, activate, and version as a unit. Rule of thumb: a one-off tweak to your current site is a snippet (WPCode Snippets); a self-contained feature you want to own and reuse is a plugin (Plugin Builder).
Multisite management
LolaCore is designed for single-site WordPress installations. Multisite networks are not supported. Lola won't crash on a multisite install, but her abilities operate on the current site only and don't extend to network administration.
Anything outside WordPress's scope
Lola's context is WordPress. If you ask her something that has nothing to do with your site, she'll tell you that's outside her scope and redirect to what she can actually do for you. This is a deliberate design choice: an agent confined to its domain is more reliable and less likely to give you plausible-sounding but wrong answers about things outside its context.
Self-modification
Lola cannot modify her own code, change LolaCore's plugin files, alter her system prompt, or adjust her own settings without going through the settings panel. She also can't be instructed to "ignore her safety rules" or "act as if confirmations are disabled." Her safety behavior is part of her configuration, not something she can override based on a chat instruction.
What to do when you hit a limit
- Server-level task → use your hosting panel or contact your host.
- Premium plugin update → use the plugin's own update mechanism or the developer's instructions.
- A code snippet on your existing site → get the WPCode Snippets addon (or copy the code Lola writes into WPCode manually). A full standalone plugin → use the free Plugin Builder.
- Elementor layout changes → install the free LolaCore for Elementor addon, or edit in the Elementor builder directly.
- Not sure if something is possible → ask Lola. "Can you do X?" She'll tell you directly, and if not, what the closest alternative is.
Next: Prompt Library
Prompt Library: 42 Ready-to-Use Prompts
These are starting points, not scripts. Copy one into the chat and adjust to your actual situation. Lola understands natural language, you don't need exact phrasing.
Prompts marked WooCommerce require WooCommerce active. Pro requires WooCommerce Pro. WPCode requires the WPCode Snippets addon. Fluent requires the Fluent Support addon.
Daily check-ins
- "Give me a quick briefing on the site, anything that needs attention today."
- "What does the site look like right now? Plugins, security, WooCommerce, anything flagged."
- "What have we worked on recently? Anything pending or unfinished?"
- "Are there any plugin or theme updates I should know about?"
- "Summarize what you know about this site, the important context."
Security & diagnostics
- "Run a complete security audit. Tell me what actually needs attention, not just a checklist."
- "Are any of my active plugins flagged for security vulnerabilities?"
- "How many administrator accounts does this site have? Flag any that seem unusual."
- "Is debug mode active on this site? It shouldn't be on a live site."
- "Run an SEO diagnosis. What's technically broken or missing?"
Plugin management
- "Before I update anything, audit my plugins and tell me if any updates have known issues."
- "Update all plugins except Elementor and [plugin name]. Show me the list first."
- "I have inactive plugins sitting around. List them and tell me if any are worth removing."
- "I need a plugin that does [X]. Find me the top options from WordPress.org with update dates and install counts."
- "I noticed [issue] after a recent change. Which plugins could be causing it?"
WooCommerce — daily operations WooCommerce
- "Which orders need my attention right now?"
- "How much have we sold this week? Compare it to last week."
- "Give me a revenue summary for [month]. Revenue, order count, average order value, top products."
- "Which products are running low on stock or out of stock?"
- "Show me all active coupons with their usage counts. Flag any that expire soon."
- "Create a [X]% off coupon called [CODE]. Valid from [date] to [date]. Minimum order [amount]."
- "Change the price of [product name] to [price]."
- "Look up order #[number] and tell me its current status and what's in it."
- "What's the purchase history for the customer with email [address]?"
WooCommerce — store health
- "How many products are in each category? Highlight any that are empty or have very few products."
- "Which products are missing descriptions, images, or are uncategorized?"
- Pro "Analyze my coupons from the last 30 days. Which ones are working and which ones are attracting deal hunters?"
- Pro "Which customers with significant purchase history haven't bought in over 90 days?"
Content management
- "How many published posts and pages do I have? Which ones are missing featured images or meta descriptions?"
- "Create a draft post with title '[Title]'. Category: [category]. Save as draft."
- "Publish the draft called '[title]'."
- "Show me all posts in the Uncategorized category. I want to assign them properly."
Database & maintenance
- "Check the database and tell me what's worth cleaning up."
- "Before I clean the database, show me exactly what would be removed and how much space it would recover."
- "Clean the expired transients only. Leave the post revisions."
- "Clear the cache, I just made changes that need to go live immediately."
Navigation & settings
- "Show me all navigation menus and what's in each one. Flag any broken links."
- "Add [page name] to the [menu name] after [existing item]."
- "What are the current general settings, site title, tagline, admin email, timezone?"
Memory & context
- "Remember that [important fact about the site or client preference]."
- "What do you remember about the [plugin/issue/decision] we dealt with [time period]?"
- "What do you have in memory about this store, campaigns, decisions, anything notable?"
Combining prompts for a full session
Weekly maintenance:
- "Give me a briefing, anything flagged since last week."
- "Run a security audit."
- "Update all plugins except Elementor."
- "Clean expired transients from the database."
- "Clear the cache."
WooCommerce Monday check:
- "What orders need attention?"
- "How much did we sell last week?"
- "Which products are low on stock?"
- "Any coupons expiring this week?"
Addons
Premium addons that extend Lola's ability set into specialized domains. Each addon integrates with core memory and intent routing.
Extending Lola: How Addons Work
The free LolaCore core plugin gives Lola 66 abilities covering general WordPress administration. Addons extend her into specific domains that require deeper, more specialized capability.
Each addon is a separate WordPress plugin that you install alongside the LolaCore core. When active, it registers new abilities directly into Lola's toolset. She recognizes them automatically and uses them in conversations where they're relevant. You don't configure the connection. You install it, activate it, and Lola's capability map expands.
The free core is always free
Addons extend LolaCore. They don't gate any free functionality behind a paywall.
If you install WooCommerce Pro and your license expires, you lose the 29 Pro abilities, but the 13 free WooCommerce abilities that were always in the core stay exactly as they were. Nothing you had before the addon disappears. Same for every addon.
Available addons
| Addon | Abilities | Price |
|---|---|---|
| LolaCore for Elementor Elementor page building from Lola chat — layouts, widgets, global styling, templates | 77 (93 Pro) | Free |
| WooCommerce Pro Advanced store management: refunds, bulk operations, analytics, customer intelligence | 29 | $99/year |
| WPCode Snippets Generate and manage custom code without a developer | 8 | $49/year |
| Fluent CRM Contact management, campaigns, and sequences from chat | 51 | $69/year |
| Fluent Support Full helpdesk management with business context in every response | 103 | $69/year |
With the free Elementor addon: 143 abilities (159 with Elementor Pro). All premium addons together: 191 additional abilities (334 with everything, 350 with Elementor Pro).
Bundles
Buying two or more premium addons? Bundles combine them under one license key (one activation per addon). See Bundles & Pricing for the full comparison.
| Bundle | Price | Includes |
|---|---|---|
| Lola Basic Bundle | $129/yr | WooCommerce Pro + WPCode Snippets |
| Fluent Bundle | $99/yr | Fluent Support + Fluent CRM |
| Business Bundle | $179/yr | All four premium addons |
Installing an addon
- Download the addon from lolacore.com — LolaCore for Elementor or your purchased premium addon
- Go to wp-admin → Plugins → Add New Plugin → Upload Plugin
- Upload the zip and activate
- Make sure the required third-party plugin is also active (Elementor, WooCommerce, WPCode, or Fluent Support)
- Premium addons: activate your license in wp-admin → Lola → Settings
Once activated, open the Lola chat. The new abilities are immediately available, no configuration required.
How to confirm an addon is active
Ask Lola directly: "What abilities do you have right now?" She'll list her full toolset organized by domain. Addon domains appear with their ability count and a "Premium Addon" label.
You can also see the full list in wp-admin → Lola → Settings → What Lola Can Do.
Addons work together
When you have more than one addon active, Lola doesn't treat them as separate tools with separate contexts. She sees the full picture and reasons across all of them.
WooCommerce Pro + Fluent Support means a ticket about a missing order gets answered with the actual order data, refund status, and a drafted response, all in one exchange. WooCommerce Pro + WPCode Snippets means a full Black Friday campaign (bulk pricing, coupon, floating banner) in three messages.
Addon: LolaCore for Elementor
77 abilities with Elementor Free, 93 with Pro · Requires: LolaCore + Elementor 3.30+ (Free or Pro)
Lola could already read your Elementor site: which templates are active, which pages use a widget, what your global colors are set to. She just couldn't change any of it. You still had to open the builder, find the container, make the tweak, save, close.
This addon removes that wall. Install it alongside LolaCore and Elementor. Describe what you need in the wp-admin chat. Lola reads your Elementor site and writes to it — page structure, widgets, global styles, templates — with the same Preview → Confirm → Execute flow as every other Lola ability. Your data stays on your server.
How to use it
LolaCore chat (recommended): Install LolaCore and this addon on the same site with Elementor active. The addon auto-detects LolaCore and injects all 77 abilities (93 with Elementor Pro). Open the chat and ask for anything Elementor-related.
Standalone MCP (optional): Developers can connect Cursor, Claude Code, or Antigravity directly to /wp-json/mcp/lolacore-elementor without LolaCore chat. Requires the WordPress MCP Adapter and an Application Password. See MCP Integration for the core setup pattern.
What the 77 abilities cover
Discovery, page structure, widgets, global Site Kit styling, templates, media (Openverse), Custom Code (Elementor's own CSS fields and Pro snippets), variables, global classes, components, display conditions, and more. Pro-only shortcuts unlock automatically when Elementor Pro is detected.
| Area | Examples |
|---|---|
| Structure & widgets | Add containers, move elements, update any widget by schema |
| Global styling | Update Site Kit colors and typography from chat |
| Templates | Export a layout, import it to another page, save reusable sections |
| Custom Code | Per-element CSS, page HTML widgets, Elementor Pro Custom Code snippets |
| Composites | Build a full page layout from a declarative structure in one call |
Installing the addon
- Install and activate LolaCore
- Download LolaCore for Elementor from lolacore.com/lolacore-for-elementor
- Upload and activate via Plugins → Add New → Upload Plugin
- Confirm Elementor is active
- Ask Lola: “What abilities do you have for Elementor?”
Small tweaks, without opening the builder
She found the template, noticed bold was already there, and matched a color already on the site instead of inventing a new one.
Build a section from scratch
When Lola disagrees — and executes anyway
She advises. You decide. She executes without arguing.
Elementor Free vs Pro
The addon works with Elementor Free — full discovery, structure, document, media, template, and global styling toolkit plus all free widget shortcuts. When Elementor Pro is detected, 16 additional Pro shortcuts unlock (forms, flip boxes, posts grids, off-canvas, and more) plus Elementor Pro Custom Code snippet tools.
What this addon does NOT cover
- Visual drag-and-drop in the Elementor editor UI (you can still open the builder to fine-tune)
- Third-party Elementor widget packs unless they register standard discoverable widgets
- Theme Builder assignment rules beyond display conditions
- Arbitrary PHP outside Elementor — for site-wide hooks, use WPCode Snippets
Next: Addon: LolaCore for ACF
Addon: LolaCore for ACF
26 abilities with ACF Free, 30 with ACF Pro · Requires: LolaCore + Advanced Custom Fields (Free or Pro) · Free — no license
ACF can model almost any kind of content — field groups, location rules, conditional logic, custom post types, taxonomies. It is one of the most capable plugins in WordPress. The interface is the price you pay for that power: you open ACF and face a screen that assumes you already speak the language. For developers that's fine. For everyone else, ACF is the plugin a tutorial told them to install and they never opened twice.
This addon removes that wall. Install it alongside LolaCore and ACF, then describe what you need in the wp-admin chat — “store the SKU, weight, and a photo gallery on every product” — and Lola creates the field group, adds the fields, and fills them in. Same Preview → Confirm → Execute flow as every other Lola ability. You never type the words “field group” or “location rule.” You describe a real problem; Lola builds the structure on top of ACF. Your data stays on your server.
How to use it
Install LolaCore and this addon on the same site with ACF active. The addon auto-detects LolaCore and adds all 30 ACF abilities to Lola's toolset — no license key, no configuration, no settings page. Open the Lola chat in wp-admin and ask for anything ACF-related: create a field group, add a field to every product, fill in a value, list what custom fields an entry has. Lola picks the right ability, previews write operations, and executes after you confirm. Read operations return immediately. ACF appears as a domain in Lola → Settings → What Lola Can Do, labeled ACF (Advanced Custom Fields), with no license badge — it's free.
What the 30 abilities cover
26 abilities work with ACF Free. The 4 that manage options pages require ACF Pro and turn on automatically when Pro is detected, for 30 total. Every ability runs against the public ACF API, so field groups Lola creates are indistinguishable from ones you build by hand — same data, same structure, fully exportable. Lola operates on top of ACF; she does not replace it.
| Area | What it does | # |
|---|---|---|
| Field values | Read and write the data: look up a SKU, update a price, list every custom field on an entry, clear a value. Posts, pages, users, terms, options. | 5 |
| Field groups | List, inspect, create, modify, duplicate, activate, deactivate, delete. Location rules included — “only on products”, “only on this template”. | 7 |
| Individual fields | Add a field, change its type or label, remove it, or ask what options a field type accepts before deciding. | 5 |
| Custom post types | Movies, events, properties, recipes — list, create, modify, delete the content types the site tracks. | 4 |
| Custom taxonomies | The categories and tags for those post types. List, create, modify, delete, and link them to the right types. | 4 |
| Options pages (ACF Pro) | Site-wide settings screens: theme logo, social links, footer text. List, create, modify, delete. | 4 |
| Export | Export any field group as JSON, ready to import elsewhere or drop into a theme's acf-json folder. | 1 |
Installing the addon
- Install and activate LolaCore
- Install and activate Advanced Custom Fields (Free or Pro)
- Download LolaCore for ACF from lolacore.com/lolacore-for-acf (free, no purchase required)
- Upload and activate via Plugins → Add New → Upload Plugin
- Ask Lola: “What abilities do you have for ACF?”
A problem you didn't know was a custom field
You never said “field group” or “location rule.” You described a real problem in the language of your store, and Lola translated it into ACF.
Build a field group the way you'd describe it
A request that would have taken minutes of clicking through ACF, resolved in one turn.
Cross-domain: ACF data, displayed
Custom fields are only useful when something shows them. ACF stores the data; your page builder displays it. If you also run LolaCore for Elementor (also free), Lola connects both ends in one turn.
ACF made the data. Elementor displayed it. You didn't have to know they were two separate problems.
ACF Free vs Pro
The addon works fully with ACF Free — field groups, fields, values, custom post types, taxonomies, and export, all 26 capabilities. When ACF Pro is detected, two things change automatically: the four options-page capabilities activate (30 total), and Lola can create Pro field types — repeater, gallery, flexible content, and clone. No separate license either way — it's free with both editions of ACF.
What this addon does NOT cover
- The ACF editor UI itself — the addon writes through ACF's public API; you can still open the field group editor to adjust by hand
- Rendering fields on the front end on its own — ACF stores data; pair with LolaCore for Elementor to wire the display
- Third-party ACF extensions unless they register through ACF's standard field-type API
- Native WordPress custom fields not managed by ACF — those are core LolaCore territory (
update-post-meta)
Next: Addon: LolaCore for SEO
Addon: LolaCore for SEO
28 abilities (22 with Yoast Free) · Requires: LolaCore + Yoast SEO (Free or Premium) · WordPress 7.0+ · Free
You think about SEO in plain sentences. “Find every product without a description.” “Stop Google from indexing this page.” Yoast SEO can do all of it. What it can’t do is take the sentence. You translate it yourself every time: open the post, scroll to the Yoast box, find the field, type, save. One post is a minute. Forty-three products with no meta description is an afternoon.
This addon removes the translation step. Install it alongside LolaCore and Yoast, then describe what you need in the wp-admin chat. Lola checks or changes the Yoast fields for you, across one post or your whole catalog. Same Preview → Confirm → Execute flow as every other Lola ability. You never open the Yoast metabox. Lola writes into the same fields Yoast already reads. Your data stays on your server.
How to use it
Install LolaCore and this addon on the same site with Yoast SEO active. The addon auto-detects LolaCore and adds all SEO abilities to Lola’s toolset: no license key, no configuration, no settings page. Open the Lola chat in wp-admin and ask for anything SEO-related: write a meta description, audit the whole site, fix a title, set a redirect. Lola picks the right ability, previews write operations, and executes after you confirm. SEO appears as a domain in Lola → Settings → What Lola Can Do, labeled SEO, with a FREE ADDON badge.
What the 28 abilities cover
22 abilities work with Yoast Free. The 6 that manage redirects and additional focus keyphrases require Yoast Premium and turn on automatically when Premium is detected, for 28 total. Every ability runs against Yoast’s public API (WPSEO_Meta, WPSEO_Options, WPSEO_Taxonomy_Meta, redirect manager). Lola generates text with your own AI key and saves it into the same fields Yoast scores. She never calls Yoast’s AI endpoints.
| Area | What it does | # |
|---|---|---|
| Post & page SEO | Title, meta description, focus keyphrase, canonical, robots, cornerstone, Open Graph / Twitter on any post, page, or product. One write merges only the fields you name. | 7 |
| Site-wide audit | Find every post missing a meta description, missing a keyphrase, scoring low, or set to noindex, across the whole catalog at once. | 4 |
| Global SEO config | Title and meta templates, separator, noindex per post type, and other global Yoast options. Set once, applies everywhere. | 6 |
| Taxonomy SEO | Title, description, and meta fields for categories, tags, and other terms. | 2 |
| Social configuration | Social profile links and the default image when a shared page has none of its own. | 2 |
| Bulk SEO updates | Apply one title or description pattern across a filtered set of posts, with an exact count before anything saves. | 1 |
| Redirects (Yoast Premium) | List, create, update, and delete redirects through Yoast’s redirect manager. | 4 |
| Additional keyphrases (Yoast Premium) | Read and set the extra focus keyphrases Premium allows beyond the primary one. | 2 |
Installing the addon
- Install and activate LolaCore
- Install and activate Yoast SEO (Free or Premium)
- Download LolaCore for SEO from lolacore.com/lolacore-for-seo (free, no purchase required)
- Upload and activate via Plugins → Add New → Upload Plugin
- Ask Lola: “What abilities do you have for SEO?”
Closing every gap across the whole catalog
You never opened a single product editor. Lola found the gap across your entire catalog and left every change in preview until you said go.
Diagnosing a symptom, not hunting for a setting
You described a symptom, not a setting. Lola found which Yoast field was wrong and changed it.
Cross-domain: SEO and WooCommerce in one turn
A missing meta description lives in Yoast. A missing price lives in WooCommerce. When you describe a real situation, both can be true. If Lola can also reach WooCommerce on your site (core LolaCore), one sentence can cross both in the same conversation.
What started as an SEO check caught a stock problem at the same time.
Yoast Free vs Premium
The addon works fully with Yoast Free: post, page, and taxonomy SEO, site-wide audit, global templates, social config, and bulk updates, all 22 capabilities. When Yoast Premium is detected, the four redirect capabilities and two additional-keyphrase capabilities activate automatically (28 total). No separate license for this addon either way.
What this addon does NOT cover
- Yoast’s own scoring engine or AI features. Lola writes the fields; scores and Yoast AI stay in Yoast
- Other SEO plugins in v1.0. Rank Math and others are planned for future versions
- Structured data and settings outside the global options Lola manages. Those stay in the Yoast interface
- How search engines rank you. Lola edits the same fields you’d edit by hand, faster
LolaCore for SEO is an independent add-on. Version 1.0 integrates with Yoast SEO. It isn’t built or endorsed by Yoast BV. “Yoast” is a trademark of Yoast BV.
Addon: LolaCore for Statistics
22 abilities (18 with WP Statistics Free) · Requires: LolaCore + WP Statistics · WordPress 7.0+ · Free
WP Statistics already records every visit, source, page, and referrer on your site. The data is there. The problem is getting to it: open the admin, pick a date range, open another screen, compare two periods by eye, and try to remember whether last Tuesday’s spike was real or a bot sweep.
This addon removes the dashboard step. Install it alongside LolaCore and WP Statistics, then ask what you need in the wp-admin chat. Lola reads what WP Statistics already stores and tells you what it means. Same Preview → Confirm → Execute flow for write operations. Your analytics database stays on your server.
How to use it
Install LolaCore and this addon on the same site with WP Statistics active. The addon auto-detects LolaCore and registers its statistics abilities: no license key, no configuration page. Open the Lola chat and ask anything traffic-related. Statistics appears in Lola → Settings → What Lola Can Do, labeled Statistics, with a FREE ADDON badge.
This addon also ships lolacore-statistics-analyst, the first reinforcement skill among LolaCore addons. When your question touches traffic or unusual patterns, that skill routes Lola to the right ability and shapes how she interprets the result instead of dumping a raw table.
What the 22 abilities cover
18 abilities work with the standard WP Statistics install from WordPress.org. 4 more register when WP Statistics premium add-ons are active (2 for Marketing, 2 for DataPlus). Every read runs against the official WP Statistics PHP API. Lola does not query your analytics tables directly and does not replace WP Statistics.
| Area | What it does | # |
|---|---|---|
| Overview | Visitors, views, top pages, and trend. The live online now count appears only when Real-Time Stats is active (not a separate ability). | 1 |
| Audience | Daily trend with change vs previous period, geographic breakdown, device breakdown, and traffic sources. | 4 |
| Content | Top pages and posts, single-page deep-dive, category and author leaderboards, and find declining pages across two date ranges. | 5 |
| Patterns | Detect traffic anomalies (sensitive-page bursts, site sweeps, geo concentration, spikes) and investigate visitor patterns (aggregated, not deanonymized). | 2 |
| Config & privacy | Read/update allowlisted tracking toggles, manage exclusions, set privacy options, tracking health check, and privacy audit. Writes use dry-run preview and confirmation. | 6 |
| Marketing add-on (WP Statistics Marketing) | Conversion goal completions and UTM campaign visitors/views. | 2 |
| DataPlus add-on (WP Statistics DataPlus) | Outbound link click counts and file download events. | 2 |
Lola works in three layers: Read the right metric, Explain patterns that deserve attention, and Cross-reference findings with SEO, content, or commerce context on the same site. When you say something looks weird, Lola calls detect traffic anomalies first before concluding traffic is normal.
Installing the addon
- Install and activate LolaCore
- Install and activate WP Statistics from WordPress.org
- Download LolaCore for Statistics from lolacore.com/lolacore-for-statistics (free, no purchase required)
- Upload and activate via Plugins → Add New → Upload Plugin
- Ask Lola: “What can you do for statistics?”
How is my site doing this week?
You asked one sentence. Lola pulled the summary and trend, not a dashboard tour.
Which pages are losing traffic?
You named a symptom. Lola ran find declining pages and grouped results by type so you know what to fix first.
Something looks off on my privacy policy
Statistics flags the pattern. Lola cross-references site context and suggests remediation you review and approve. She describes what she sees. She does not claim she stopped a threat.
Analyst companion, not a security tool
Lola reads patterns and explains what she sees. She does not block visitors, ban IPs on her own, or act as a firewall. When a pattern looks like reconnaissance or a compliance probe, she describes it and suggests next steps in WP Statistics (for example reviewing exclusions after a dry-run) or in your existing security tools.
WP Statistics Free vs premium add-ons
All 18 base capabilities work with WP Statistics Free. Real-Time Stats adds the live online-now count inside the site summary (not a separate ability). Marketing adds goals and UTM campaigns (+2 abilities). DataPlus adds link and download tracking (+2 abilities). The addon detects each add-on at runtime; no separate license for LolaCore for Statistics.
What this addon does NOT cover
- Replacing WP Statistics. You can still open the WP Statistics admin whenever you want
- Live visitor monitoring as a standalone feature without the Real-Time Stats add-on
- Security blocking. Exclusion changes go through WP Statistics with your confirmation
- Deanonymizing visitors when WP Statistics anonymizes or hashes IPs
- Other analytics plugins. Version 1.2 works with WP Statistics only
WP Statistics is a trademark of Verona Labs. LolaCore for Statistics is an independent add-on built by LolaCore. It is not affiliated with, endorsed by, or sponsored by Verona Labs.
Next: Addon: WooCommerce Pro
Addon: WooCommerce Pro
29 additional abilities — $99/year — Requires: LolaCore + WooCommerce + valid license
The free LolaCore core gives you 13 WooCommerce abilities: check orders, look up products, create a coupon, pull a basic report. WooCommerce Pro is what happens when you take that and multiply it. The 29 Pro abilities cover what the free core can't touch: processing refunds, updating prices across an entire category in one shot, identifying which customers are worth a reactivation campaign, auditing your tax configuration, building shipping zones from a conversation. The free core manages individual records. WooCommerce Pro operates at the store level.
Orders (4 abilities)
The free core can update order statuses. It cannot process refunds.
Two messages. No opening the order. No hunting for the refund tab. Unlike the free core, this doesn't just change a status, it triggers the actual payment reversal through Stripe or PayPal.
Pro also gives you intelligent order triage: not just a status filter, but an explanation of which orders need action and why, with a recommended priority order based on wait time and recovery likelihood.
Catalog management (7 abilities)
The free core updates one product at a time. Pro operates on your entire catalog.
One confirmation. 47 products updated. The free core would require 47 separate operations.
Pro also gives you stock velocity analysis (not just current levels, but which products will run out first and how fast), full catalog audits across every product at once, and variation-level management:
Analytics (7 abilities)
The free core has basic sales reports. Pro has analysis: period comparisons, margin intelligence, coupon behavior, tax summaries.
The free core can list your coupons and show usage counts. Pro tells you what the behavior behind the numbers actually means.
Customer intelligence (3 abilities)
Store configuration (6 abilities)
The free core doesn't touch WooCommerce's configuration layer. Pro reads and writes it: tax rate auditing, payment gateway management, and shipping zone configuration.
Shipping (2 abilities)
The free core has no shipping tools at all. This is entirely Pro territory. Lola can explain your shipping zones in plain language and build or adjust them from a conversation.
What WooCommerce Pro does NOT cover
- Direct access to your Stripe or PayPal dashboard (refunds go through WooCommerce's API layer)
- Reading customer email inboxes
- WooCommerce Subscriptions management (separate plugin with its own data structure)
- Wholesale pricing managed by third-party plugins that don't expose data through standard WooCommerce price fields
Next: Addon: WPCode Snippets
Addon: WPCode Snippets
8 additional abilities — $49/year — Requires: LolaCore + WPCode + valid license
Your WordPress site works. But it doesn't do everything exactly the way you need. Checkout doesn't have the VAT field your customers keep asking for. Virtual product orders complete manually, one by one. You want returning customers to get an automatic discount. None of that has a setting in WooCommerce.
So you install a single-purpose plugin. Then another. Each one adds a CSS file, a JavaScript file, a database entry, and a monthly update to stay on top of. And each one is a potential security vector sitting in your plugin list indefinitely.
WPCode Snippets gives Lola 8 tools to connect to WPCode. Describe what you need. She writes the code, shows it to you before activating, and registers it in WPCode. If something breaks, WPCode disables it automatically.
What makes this different from a code generator
Any AI can write PHP. The problem with generic code is that it doesn't always work on your specific installation.
Lola knows which plugins you have active before writing a single line. She knows your WooCommerce configuration, your payment gateways, your tax classes, your shipping zones. When she generates a snippet, she generates it for your site, not a hypothetical WordPress installation.
Lola knows you have Rank Math active because she saw it during the initial site scan. She doesn't give you the Yoast snippet by mistake.
Real examples
Plugin replacement
The 8 tools
- listSnippets — All your WPCode snippets with filters by status, code type, and tags.
- getSnippet — Full code of any snippet, including type, injection location, priority, and status.
- getAvailableLocations — Every injection point where WPCode can insert code on your site.
- checkSnippetErrors — Whether a snippet has errors logged by WPCode. Useful when a snippet has been auto-disabled.
- createSnippet — Generates code and registers it in WPCode. Always shows you the code before activating.
- updateSnippet — Modify the code, location, tags, or priority of any existing snippet.
- toggleSnippet — Activate or deactivate from the chat without opening WPCode.
- deleteSnippet — Remove a snippet permanently, with confirmation.
What WPCode Snippets does NOT cover
The line is roughly this: if it can be done in 5–100 lines injected through a WordPress hook, Lola can do it. If it requires building something with its own data architecture, that's a custom plugin. Running code in the WordPress CLI or at the server level, modifying plugin or theme files directly, or any code that requires custom database tables are outside scope.
Next: Addon: Fluent Support
Addon: Fluent Support
103 additional abilities · $69/year · Requires: LolaCore + Fluent Support (free or Pro) + valid LolaCore for Fluent Support addon license
Running customer support without this addon means: open Fluent Support, read the ticket, open WooCommerce in another tab, find the order, check the refund status, copy the details, switch back, write the response. You're the connector between the systems.
With Fluent Support installed, Lola is the connector. She reads the ticket, pulls the order data, checks the refund status, and drafts the response, with the exact amounts, dates, and context already filled in. You review and send.
The ticket that shows everything at once
Lola read the ticket, pulled the customer's full purchase history, found the exact refund record, calculated the expected timeline, and wrote a response with real numbers. Not a template. Not a guess. An answer with the actual data.
Ticket management (14 abilities)
Everything you do in the Fluent Support ticket interface, from the chat: reading the queue with filters, opening tickets, creating tickets, updating properties (status, priority, assignment, product), closing and reopening, changing the linked customer, attaching and detaching tags, merging and splitting tickets, adding watchers, creating and managing replies, bulk operations.
Workflows (11 abilities)
Fluent Support's workflow engine lets you automate repetitive actions: assign tickets based on keywords, auto-tag by product, close satisfied tickets automatically. Through Lola:
Reporting (9 abilities)
Available: overview, ticket stats, resolution time, first response time, agent performance, tag and product breakdowns.
Also included
- Conversations & replies (9 abilities): read the full thread, post replies, and manage internal notes on any ticket
- Customer management (7 abilities): full customer profiles with ticket history and (if WooCommerce Pro is active) order and spend data
- Agent & team management (9 abilities): add agents, set product access, track workload and performance
- Mailbox management (8 abilities): list, create, update, and delete mailboxes and their routing
- Product management (4 abilities): manage the products and categories tickets are filed against
- Tags & saved replies (8 abilities): manage ticket tags and your saved-reply library
- Custom fields (3 abilities): manage custom ticket fields
- Time tracking (4 abilities): log and review time spent on tickets
- Settings (5 abilities): read and adjust Fluent Support configuration
- Activity log (2 abilities): review the audit trail of changes on a ticket
- Customer portal (4 abilities): manage the customer-facing support portal
- Notifications (6 abilities): manage notification rules and channels
What cross-addon intelligence adds
Fluent Support + WooCommerce Pro: every ticket response has access to real order data, refund status, shipping information, and customer purchase history. No tab switching. No looking up order numbers manually.
Fluent Support + WPCode Snippets: a customer reports a behavior issue on your site. Lola checks your active snippets for potential conflicts, identifies the likely cause, and drafts a response that includes the fix.
Fluent Support + Memory: a customer who opened three tickets last month about the same integration issue opens ticket four. Lola remembers the full history across sessions. The customer doesn't have to explain the issue again.
What Fluent Support does NOT cover
- Accessing customer email inboxes directly (she works through Fluent Support's ticket system)
- Fluent CRM (separate addon, covers email marketing and contact lifecycle)
- Sending arbitrary emails outside Fluent Support's reply system
- Direct integration with third-party CRMs or helpdesks not connected through Fluent Support
← WPCode Snippets · Next: Addon: Fluent CRM
Addon: Fluent CRM
51 abilities (43 free + 8 Pro) — $69/year — Requires: LolaCore + FluentCRM (free or Pro) + valid LolaCore for FluentCRM addon license
Without this addon, managing FluentCRM means clicking through contact filters, dragging segments, switching to WooCommerce to check who bought what, and then switching back to build a campaign for those people. If you also run Fluent Support, add a third tab: checking which of your "dormant" customers are actually waiting for a ticket resolution before you blast them with a "we miss you" email.
With Fluent CRM installed, Lola does all of that from a single conversation. She queries contacts, cross-references purchase data, knows who has open support tickets, drafts the campaign, and schedules the send. You review and approve.
The conversation that shows the difference
No email platform gives you that view. Klaviyo sees purchase history. ActiveCampaign sees email engagement. Neither sees your support tickets. Lola sees all three because she has access to all three systems at once (with the corresponding addons active).
Contact management (8 abilities)
- Pull individual profiles with full tag, list, company, custom field, and engagement data
- Search and filter by any combination: status, tags, lists, country, contact type, date range, lifetime value
- Create, update, and delete contacts individually or in bulk
- Tag and list management on contacts: add, remove, reassign
- Notes and activity logs: add notes, call logs, meeting records to any contact timeline
Tags & Lists (8 abilities)
Full CRUD on your tag taxonomy and subscriber lists. Create, rename, and delete tags or lists from conversation. No need to open the FluentCRM settings panel.
Companies (6 abilities)
Email campaigns (8 abilities)
That campaign took one conversation. No segment builder. No dragging contact filters. No switching between WooCommerce and FluentCRM to cross-reference dates.
Automation funnels (4 abilities, read-only)
Lola can list your funnels, inspect their configuration, pull performance reports, and activate or pause them. She cannot create or edit funnel logic. The visual condition builder in FluentCRM handles 22 operators across recursive yes/no branches, too complex and too risk-sensitive for chat-based authoring.
Reporting (4 free + 1 Pro)
That last observation isn't a report feature. It's memory. Lola has seen your campaigns accumulate over time and knows your patterns.
Also included
- Event tracking (2 abilities): record custom events against contacts and retrieve their event timeline
- Settings (3 abilities): read and update global FluentCRM configuration, send test emails
- Email sequences (7 abilities, Pro only): list, view, create sequences, add steps with configurable delays, manage enrolled subscribers
What cross-addon intelligence adds
Fluent CRM + WooCommerce Pro: Your purchase data and your contact list are in the same brain. Segment by product purchased, order value, purchase frequency, last order date. Build a re-engagement campaign for customers who bought a specific product 90 days ago, without opening two separate tools.
Fluent CRM + Fluent Support: The churning customer problem is only solvable when you know why someone churned. Fluent Support gives Lola access to your ticket history. The question "who should I send a re-engagement email to?" now has a better answer: the contacts who went quiet and don't have unresolved issues.
Fluent CRM + Memory: Lola tracks your campaign patterns across sessions. She knows which subject line formats have worked, which audiences have responded, which offers have converted.
What Fluent CRM does NOT cover
- Creating or editing automation funnel logic (funnels are read-only plus status toggle)
- Accessing external email providers directly (Lola works through FluentCRM's contact and campaign system)
- Connecting to Fluent Support data on her own (requires the Fluent Support addon to be active)
- Sending arbitrary emails outside FluentCRM's campaign and sequence system
- Fixing email delivery problems (Lola will flag SMTP issues but cannot repair your sending configuration)
← Fluent Support · Next: Bundles & Pricing
Bundles & Pricing
Three bundle options for premium addons. Each bundle is one license key with multiple activations — one per addon included. LolaCore itself stays free.
Premium addons work individually. Bundles exist because some capabilities only appear when Lola has both systems in the same conversation — and the Business Bundle is where all four domains share one memory.
Compare the bundles
| Bundle | Price | Addon abilities | Includes | You save |
|---|---|---|---|---|
| Lola Basic Bundle Store + custom code |
$129/yr | 37 | WooCommerce Pro + WPCode Snippets | $19/yr |
| Fluent Bundle Support + CRM intelligence |
$99/yr | 154 | Fluent Support + Fluent CRM | $39/yr |
| Business Bundle Full cross-domain stack |
$179/yr | 191 | All four premium addons | $107/yr |
Which one fits? Running a WooCommerce store → start with the Basic Bundle. Fluent Support and FluentCRM without a store → the Fluent Bundle. Store, code, support, and email marketing together → the Business Bundle ($48/year less than buying both smaller bundles separately).
LolaCore for Elementor is free and separate from these bundles. See LolaCore for Elementor.
Lola Basic Bundle: WooCommerce Pro + WPCode Snippets
103 total abilities — $129/year (vs. $148 separately) — Requires: LolaCore + WooCommerce + WPCode
WooCommerce Pro handles the structured operations: pricing, refunds, analytics, customers, coupons, shipping. It covers the 90% of daily store operations that have a native WooCommerce interface.
WPCode Snippets handles the remaining 10%: everything WooCommerce doesn't have a setting for. The behavior specific to your store, your campaign, your customer experience. The stuff that was always a developer call or a plugin install before.
With both together, Lola can do things that aren't possible with either addon alone.
The Black Friday campaign in three messages
Three different tools. Three confirmations. One conversation. No WooCommerce editor, no banner plugin, no developer, no waiting.
The plugin audit that changes your monthly bill
WooCommerce Pro alone knows what it covers. WPCode Snippets alone knows what it can replace. Only with both can Lola run the full audit.
The memory that ties it all together
The addons don't just give Lola more tools. They give her more context to accumulate. WooCommerce Pro remembers your store's campaigns, your pricing decisions, your seasonal patterns. WPCode Snippets remembers the code it's built, why it was created, what behavior it changes. As both memories compound, Lola starts making connections that span months.
What's in the bundle
| Free core | + Woo Pro | + WPCode | Bundle | |
|---|---|---|---|---|
| Total abilities | 66 | 95 | 103 | 103 |
| WooCommerce tools | 13 | 42 | 42 | 42 |
| Code generation & management | — | — | ✓ | ✓ |
| Full campaign in one conversation | — | — | — | ✓ |
| Price | Free | $99/yr | $49/yr | $129/yr |
The $19 saving versus buying separately isn't the argument. Some capabilities only exist when both addons have context about your site. You either have the full picture or you don't.
Requirements
LolaCore free core plugin + WooCommerce + WPCode (both free on WordPress.org) + valid Lola Basic Bundle license (one key with two activations, one per addon). Activate each addon independently from wp-admin → Lola → Settings → What Lola Can Do.
Next: The Fluent Bundle
The Fluent Bundle: Fluent Support + Fluent CRM
220 total abilities — $99/year (vs. $138 separately) — Requires: LolaCore + Fluent Support + FluentCRM + valid Fluent Bundle license
Fluent Support gives Lola your ticket queue: reading, triaging, responding, and closing tickets from conversation. Fluent CRM gives her your contact list, campaigns, and sequences. Individually, each addon makes Lola better at one job. Together, they give her something neither system can have alone: the ability to see why a customer stopped buying before you send them a "come back" email.
Without the bundle, your CRM doesn't know about your support tickets. You tag a customer as "dormant" because they haven't purchased in 60 days. You queue them for a re-engagement campaign. But three of those customers have open billing complaints. They're not dormant — they're frustrated. You just sent your most frustrated customers a cheerful "we miss you!" email.
With both addons active, Lola cross-references the data. She sees the open tickets, the purchase history, the CRM tags, the email engagement. She knows who to target and who to leave alone until their ticket is resolved.
Close the tickets. Then build the campaign. Same conversation.
One conversation. Two systems. Three operations: resolve, tag, campaign. No one had to copy customer names between tabs, check which ones are in FluentCRM, or manually exclude the ones with open issues.
The campaign that causes tickets — and Lola spots it
No CRM alone would connect campaign complaints to a support spike. No helpdesk alone would identify the campaign as the root cause. Lola sees both systems, traces the pattern, and proposes a fix that spans both.
The dormant customer triage
That segmentation is only possible because Lola has both the CRM data (purchase frequency, tags, email engagement) and the support data (open tickets, recent complaints). Neither addon alone produces it.
What's in the bundle
| Free core | + Fluent Support | + Fluent CRM | Bundle | |
|---|---|---|---|---|
| Abilities | 66 | +103 | +51 | 220 |
| Tickets & workflows | — | ✓ | — | ✓ |
| Contacts & campaigns | — | — | ✓ | ✓ |
| Cross-domain intelligence | — | partial | partial | ✓ |
| Price | Free | $69/yr | $69/yr | $99/yr |
The $39 saving versus buying separately isn't the argument. The argument is that some capabilities only exist when both addons share context about your customers. You either have the full picture or you don't.
What the Fluent Bundle does NOT cover
- WooCommerce operations (orders, refunds, pricing, analytics) — see WooCommerce Pro or Lola Basic Bundle
- Code generation — see WPCode Snippets
- Creating or editing FluentCRM automation funnels (funnels are read-only plus status toggle)
- Direct access to external email providers (Lola works through FluentCRM's campaign system)
- Fixing email delivery infrastructure (Lola flags SMTP issues but cannot repair your sending configuration)
The Business Bundle: All Four Addons
257 abilities across 13 domains — $179/year (vs. $286 separately) — Requires: LolaCore + WooCommerce + WPCode + Fluent Support + FluentCRM + valid Business Bundle license
Each addon gives Lola a slice: WooCommerce Pro handles the store. WPCode Snippets handles the custom code. Fluent Support handles the tickets. Fluent CRM handles the contacts and campaigns. Bought separately, they work well. Together, they give Lola something none of the smaller bundles can: the ability to trace a broken checkout snippet to the tickets it caused, tag the affected customers in the CRM, and pause the campaign that's about to hit them. All in one conversation.
The smaller bundles demonstrate cross-domain intelligence between two addons. The Business Bundle is what full cross-domain intelligence looks like: four systems, one memory, zero tab-switching.
The morning briefing
One message from you. Four systems touched. The fix, the apology, the refund, and the campaign exclusion. All connected because Lola saw the cause, not just the symptoms.
The VIP who's about to leave
No individual addon could have traced the pattern from broken tickets to code to CRM disengagement. WooCommerce showed her value. Fluent Support showed the recurring problem. WPCode held the root cause. FluentCRM showed the engagement drop. Lola connected all four.
Black Friday in one conversation
Four systems configured in one request. Pricing, code, email marketing, and support. All coordinated, all consistent, all done before you finish your coffee.
Why four is more than two plus two
The Lola Basic Bundle (WooCommerce + WPCode) gives Lola store intelligence and custom code. The Fluent Bundle (Support + CRM) gives her customer intelligence and outreach. Each is powerful on its own.
The Business Bundle isn't a discount on buying both smaller bundles. It's what happens when every system feeds into the same memory:
- A code change breaks the checkout → tickets come in → Lola traces the cause, fixes the code, responds to tickets, and excludes affected customers from campaigns. Four systems, one causal chain.
- A campaign sends an expired coupon → Lola identifies the root cause, fixes the landing page, processes refunds, and sends a corrected campaign. The diagnosis crosses three domains.
- A VIP customer's engagement drops → Lola checks their support history, purchase history, email engagement, and finds the root cause in a code snippet. No single addon has that visibility.
What's in the bundle
| Free core | + Woo Pro | + WPCode | + Support | + CRM | Bundle | |
|---|---|---|---|---|---|---|
| Abilities | 66 | +29 | +8 | +103 | +51 | 257 |
| Store operations | 13 (basic) | 42 | — | — | — | ✓ |
| Code generation | — | — | ✓ | — | — | ✓ |
| Ticket management | — | — | — | ✓ | — | ✓ |
| CRM & campaigns | — | — | — | — | ✓ | ✓ |
| Full cross-domain | — | — | — | — | — | ✓ |
| Price | Free | $99/yr | $49/yr | $69/yr | $69/yr | $179/yr |
The $107 saving versus buying separately matters. But the real argument is that some capabilities only exist when all four systems share context. No partial bundle produces them.
What the Business Bundle does NOT cover
- Visual page building — see LolaCore for Elementor (free, not included in this bundle)
- Licenses for third-party plugins: the bundle activates Lola's intelligence layer, not the plugins themselves. WooCommerce, WPCode, Fluent Support, and FluentCRM must be installed independently (all have free versions)
- Creating or editing FluentCRM automation funnels (read-only plus status toggle)
- Direct access to external email providers (Lola works through FluentCRM's campaign system)
- Fixing email delivery infrastructure (Lola flags SMTP issues but cannot repair your sending configuration)
- Magento, Shopify, or any platform that isn't WordPress
← The Fluent Bundle · Next: Frequently Asked Questions
Ready to extend Lola's capabilities?
Pick the bundle that matches your stack. Annual license, one activation per addon.
LolaCore for Elementor is free — see the addon page.
Frequently Asked Questions
Quick answers to the questions we hear most often.
What do I need to run LolaCore?
Three things: WordPress 7.0 or later, PHP 8.1 or later, and an API key from at least one AI provider (Anthropic, OpenAI, or DeepSeek). No extra server software, no external libraries, no Node.js runtime. LolaCore runs on WordPress's native AI Client.
How do I connect my AI provider?
Go to wp-admin → AI Connectors (options-connectors.php). That's the WordPress 7.0 screen where you manage AI provider connections. Add your provider's API key there. LolaCore detects it automatically.
If you had a provider configured before installing LolaCore, it's already connected.
Does LolaCore store my API key?
No. API keys live in the WordPress AI Connectors screen, managed by WordPress core. LolaCore reads the connection from there. It never stores keys directly, never logs them, and never includes them in memory or exported data.
Which AI provider should I pick?
Any of the three works for the full range of tasks. If you already have an account with one, start there. You can switch at any time without losing anything.
Can I use multiple AI providers at the same time?
You can configure as many providers as you want. All their models show up together in the LolaCore model selector. You pick one active model at a time, but switching takes two clicks.
What can I actually do with the free plugin?
66 abilities across 9 domains: site diagnostics, plugin management, content & metadata, WooCommerce basics (13 tools), user management, database & cache, taxonomies & media, and themes & settings. All available the moment you activate. No feature gates, no trial periods.
Is the free version limited to push me toward addons?
No. The 66 core abilities are the same whether you have zero addons or four. Addons add new abilities on top. If an addon license expires, you return to exactly what you had before. Nothing free becomes paid.
Does it work without WooCommerce?
Yes. 53 of the 66 core abilities work on any WordPress site. The 13 WooCommerce tools only appear when WooCommerce is active.
What is persistent memory?
Lola remembers things between conversations. When you tell her your store does free shipping over $50, she carries that into future sessions. This isn't chat history. Memory is extracted facts, scored by relevance and subject to decay over time.
How does memory decay work?
Every stored fact has a relevance score that drops over time. Facts that keep coming up maintain their score. Stale facts gradually fade out. The decay rate is configurable in wp-admin → Lola → Memory Settings. Default is 0.02.
Can I see what Lola remembers?
Yes. Ask her: "What do you know about this site?" She'll pull from active memory and tell you. You can also export the full memory database as JSON from wp-admin → Lola → Maintenance → Export Memory.
Can I delete specific memories?
You can wipe all memory from wp-admin → Lola → Maintenance → Wipe Memory. For targeted cleanup, use Compact Memory or ask Lola to forget specific things.
Does memory transfer if I migrate my site?
Yes, when you're moving the same site (local to production, switching hosts). Export memory before the move, import it after. This only works because it's the same site. Importing memory from a different site fills Lola's context with facts that don't match and will degrade her responses. Export/Import is a migration tool, not a sharing tool.
Why did Lola tell me "no"?
Because she thinks what you're asking could damage your site. She'll explain why and suggest an alternative. Lola evaluates every write action against your site's current state before executing.
Can I override her when she objects?
Yes. Tell her you want to proceed anyway. She won't ask twice. But she logs the exchange in the action log so you can trace what happened if something goes wrong.
Can I turn off anti-sycophancy?
No. There's no toggle. Write confirmations can be disabled in wp-admin → Lola → Safety & Confirmations (not recommended), but Lola's ability to flag risky requests is built in.
Do I need special syntax to talk to Lola?
No. Natural language. No commands, no slashes, no brackets. "How many orders came in today?" works. So does multi-part requests.
What's the difference between read and write actions?
Read actions (queries, reports) run immediately. Write actions (creating, modifying, deleting) always go through a preview step first. You see what will change, you confirm, then it happens.
What happens when I close the chat window?
The session ends. When you reopen, a new session starts with relevant context loaded from memory. If you want to keep the session active, minimize instead of closing.
Can Lola undo something she did?
There's no generic "undo" button, but every action is recorded in the action log. For most write actions, the reverse operation is available: she can change a price back, restore a trashed post, etc.
What are skills?
Short behavioral guides that shape how Lola approaches specific situations. When your message matches certain keywords, the relevant skill loads. Skills refine judgment, they don't grant new abilities or data access.
Do skills cost extra?
The 10 built-in skills ship free with core. They're on by default. No addon required.
Can I create my own skills?
Yes, with the custom skills beta toggle enabled (wp-admin → Lola → Skills). Write a Markdown file with YAML frontmatter, import it, or ask Lola to build one for you. Custom skills start inactive.
How many skills can fire at once?
Maximum 5 per message, with a 6,000-character budget. Most conversations trigger 0 to 2 skills.
How does licensing work?
Core is free, forever. Addons are annual per-site subscriptions managed through Lemon Squeezy. One license key per addon, or one key with multiple activations if you bought a bundle.
What happens if my addon license expires?
The addon's abilities disappear from Lola's toolset. Everything else stays exactly as it was: memory, settings, core abilities, data. The free core never changes because of an addon's status.
Can I move my license to a different site?
Yes. Deactivate on the current site (wp-admin → Lola → What Lola Can Do → Manage license), then activate on the new one.
How do bundles work?
One license key with multiple activations. The Basic Bundle has 2 (WooCommerce Pro + WPCode Snippets). The Fluent Bundle has 2 (Fluent Support + Fluent CRM). The Business Bundle has 4 (all addons). You activate each addon separately.
What is LolaCore for Elementor?
A free addon that adds 77 Elementor abilities to Lola (93 with Elementor Pro): page structure, widgets, global Site Kit styling, templates, and more — all from wp-admin chat. Requires LolaCore and Elementor 3.30+. Full guide →
Can Lola edit Elementor layouts from chat?
With LolaCore for Elementor installed, yes. She updates structure, widgets, globals, and templates through Preview → Confirm → Execute. She writes to Elementor's data layer — she doesn't drag widgets in the builder UI.
Does LolaCore for Elementor require Elementor Pro?
No. The full discovery, structure, and free-widget toolkit works with Elementor Free. Elementor Pro unlocks 16 additional Pro shortcuts and Elementor Pro Custom Code tools automatically when detected.
Do I need to configure anything after installing an addon?
No. Install, activate, enter the license key. Lola's toolset expands automatically. No setup wizard, no configuration screens.
Which addons are available?
LolaCore for Elementor (free, 77 abilities; 93 with Elementor Pro) • WooCommerce Pro ($99/year, 29 abilities) • WPCode Snippets ($49/year, 8 abilities) • Fluent Support ($69/year, 103 abilities) • Fluent CRM ($69/year, 51 abilities). Bundles: Basic $129/year, Fluent $99/year, Business $179/year. All counts are in addition to the 66 free core abilities.
What is cross-addon intelligence?
When multiple addons are active, Lola sees data across all of them. A support ticket about a missing order pulls actual order data. A marketing campaign checks for open tickets before sending. The more addons active, the more connections she makes. No configuration needed.
Can Lola access my server or hosting panel?
No. Lola is confined to WordPress. She can't SSH, edit files on the filesystem, modify php.ini, or restart services. She can tell you what WordPress sees (PHP version, memory limits), but can't change server-level settings.
Can Lola update premium plugins?
She can update any plugin from WordPress.org. Plugins with private update servers (most paid plugins) need their own update mechanism. Lola can tell you they're out of date, but the actual update is outside her reach.
Can Lola edit my page builder layouts?
With LolaCore for Elementor, she reads and writes Elementor structure, widgets, and global styles from chat. Gutenberg block layout still requires the block editor. She doesn't drag widgets in any builder's visual UI.
Does Lola work on WordPress Multisite?
LolaCore is designed for single-site installations. She won't crash on multisite, but her abilities operate on the current site only. Network administration is out of scope.
Does Lola ever change things without asking?
Only read actions run without confirmation. Every write action goes through preview-and-confirm first. The only exception is if you've explicitly disabled confirmations in wp-admin → Lola → Safety & Confirmations.
Is there an action log?
Yes. Every action Lola executes is recorded: what was done, when, whether it was a dry run or confirmed, and whether you overrode a warning.
What about data privacy?
Conversations go directly from your WordPress site to your AI provider. LolaCore doesn't route through its own servers, doesn't log externally, and doesn't send data to lolacore.com. The only external call beyond the AI provider is license validation with Lemon Squeezy.
Where are the settings?
Everything lives in wp-admin → Lola (the Lola Configuration page). Eight sections: Lola's Brain (AI Model), Communication Style, Lola's Avatar, Memory Settings, What Lola Can Do, Safety & Confirmations, Maintenance, and Skills.
What does "Communication Style" change?
It controls how Lola explains things, not what she can do. Technical uses dev terminology. Professional (default) uses clear language without jargon. Direct gives minimal explanations and maximum action.
What does "Learning Mode" do?
When enabled (default), Lola explains what she's about to do before showing the action preview. Turn it off for a faster flow once you're comfortable.
When should I re-scan the site?
After a major plugin update, a site migration, or a theme switch. The initial scan runs automatically on activation. A re-scan takes under 60 seconds.
Lola isn't responding to my messages.
Check three things: (1) Is your AI provider still configured in wp-admin → AI Connectors? (2) Does the API key still have credit? (3) Is PHP running without fatal errors? If the provider is configured, try a simple "Hello" to rule out timeouts.
I switched providers and Lola seems different.
Different AI models have different reasoning patterns. Your memory and settings are completely independent of the provider. Try another model if one feels less useful for a specific task.
A skill isn't firing when I expect it to.
Check the skill's trigger list. If it's a custom skill, verify it's set to "active." Also check that the master skills toggle is ON in wp-admin → Lola → Skills.
I imported memory and some facts seem wrong.
If you imported from an old backup of the same site, run Compact Memory (wp-admin → Lola → Maintenance) to clean up stale facts. If you imported from a different site, that's the problem. Memory is site-specific. Wipe it and let Lola build fresh context from a re-scan.