

MAIA's side panel — conversation search, list, and chat
Hello there!
I can read, edit, and manage your site — always with your confirmation. Powered entirely by WordPress’s own AI Client, no third-party account required.
I am MAIA, an AI assistant for your WordPress website. A superstar WP developer, a writer, a know-it-all and your partner in WP website management. I know a lot about your site and will be there 24/7 to help you manage it. I can speak any language and can track multiple conversations.
Starting with version 2.0, MAIA runs entirely on WordPress 7.0’s built-in AI Client and Abilities API — no more third-party account. Connect any supported AI provider (Anthropic, OpenAI, Google, or another connector plugin) under Settings Connectors, and MAIA uses it automatically. MAIA itself never holds an API key.
I can actually do things on your site instead of just talking about them:
Every write operation — editing a file, creating or changing content, managing a term — shows you exactly what’s about to happen and waits for you to click Confirm. Nothing is written silently.
Version 2.0 also introduces a new side-panel interface (menu on top, chat below, opens from the right and covers as much of the screen as you like), with avatars in the conversation and full-text search across your past conversations. The classic floating chat window from earlier versions is still available — switch to it any time in Settings / MAIA Interface.
This plugin does not connect to any third-party AI service on its own. Instead, it uses WordPress’s built-in AI Client, which routes every request to whichever AI provider you’ve connected under Settings Connectors (e.g. Anthropic, OpenAI, or Google, each provided by its own separate connector plugin). If no provider is connected, MAIA cannot answer anything and will tell you so. Review the terms and privacy policy of whichever provider(s) you connect — MAIA itself has no relationship with them.
Every message you send includes some baseline context so MAIA doesn’t have to ask you to repeat yourself:
* your site’s name, description, and default language
* your own display name and role(s)
* the title and status of the post/page you’re currently editing, if any (not its content)
* the current page URL and the page title you’re viewing
Beyond that, MAIA works via abilities: when it needs more information, it calls a specific ability, and only the result of that call is sent to your connected AI provider as part of the conversation. Depending on what you ask, that can include:
* the contents of a plugin/theme file
* the content of a post, page, or product
* categories/tags, media library entries
* the list of users on your site, and your list of installed plugins/themes
This only happens when MAIA calls the corresponding ability while answering your request — never automatically on page load.
Writing anything (editing a file, creating/changing/deleting content, managing a term) always shows you a confirmation card first; nothing is written to your site until you click Confirm.
If you enter an API key for Brave Search and/or Tavily in Settings / MAIA, MAIA gains two extra abilities — web search and image search — backed by whichever one you’ve configured (Settings / MAIA Web search provider chooses between them when both are set). When (and only when) MAIA calls one of these, your search query is sent from your own server directly to that provider’s API using the key you provided, and the results (titles, URLs, descriptions, or image URLs/thumbnails) are returned to MAIA. No query is sent unless MAIA actually uses one of these abilities while answering you. This is entirely optional — leave both keys empty and neither ability is offered at all.
If enabled (on by default, Settings / MAIA), MAIA can make an HTTP request to any URL you or it specifies, e.g. to call a third-party API. This runs from your own server. Requests to internal/private network addresses are always blocked. GET/HEAD requests run without confirmation; any request that writes (POST/PUT/PATCH/DELETE) always shows you the exact method, URL, headers and body first. This can be turned off entirely in Settings / MAIA.
Asking MAIA to generate an image sends your text prompt to your connected AI provider (whichever one you’ve configured under Settings Connectors, if it supports image generation) from your own server. The resulting image is saved directly to your media library and shown to you in a card — MAIA itself never sees the image data — with buttons to insert it into the post/page you’re viewing or set it as the featured image.
When MAIA has a link to an image (e.g. found via web search) and shows it to you, your own browser loads it directly from wherever it’s hosted, the same as clicking the link yourself would. It’s shown in a card with save/insert/featured-image buttons; nothing is saved anywhere until you click one of them.
DISALLOW_FILE_EDIT, and on a Multisite network only a Super Admin can edit files — a regular site Administrator cannot, even with MAIA.