WordPress platformPro

AI agent memory for WordPress, stored on your own site

Without retrieved site context, a new MCP session may start with no knowledge of local preferences: the model has no idea the client hates exclamation marks, that the shop moved to a new courier last month, or that the pricing page must never mention discounts. GoBuildWP Pro's AI agent memory for WordPress keeps notes like that on the site itself, as typed records an eligible connected agent can discover and request. Instructions do not prove that the client fetched or followed them.

By GoBuildWPContent updated 13 October 2026How we check claims

Get GoBuildWP free See Pro pricing

AI clientyour-site.comVerify site policy

Stop putting exclamation marks in our product copy. Remember that for next time.

wppilot/memory-listRead
Checks the index for an existing tone-of-voice memory to update instead of adding a second one.
wppilot/memory-saveWrite
Saves a feedback memory named No exclamation marks: the rule, an owner-approved reason and a How to apply line (all product and category copy).
wppilot/memory-getRead
In a later session, reads the body after spotting the rule in the index before writing new product descriptions.

Proposed sequence from source declarations; not a recorded task or proof of client compatibility. Inspect saved state and browser or provider results separately.

Edition: Pro
Abilities: 4
Requires: WordPress 6.9+, PHP 8.0+

Data model

Memories are private posts on your site

Each memory is a post of the wppilot_memory type: not public, not in REST, not shown in the normal post screens. The title is its name, the excerpt a one-line description, the body its content, and a meta field holds its type. Because they are posts, memories get revisions, and the change log can restore an edit or undo a new one by trashing it.

There are five types. user records who the person is and how they work; feedback records a correction or a confirmed preference, written as the rule, then a Why line and a How to apply line; project records decisions and dates not visible anywhere else; reference points to where information lives in other systems; composition holds what a pricing table, hero or testimonial set on this site is actually made of, checked first with check-composition.

A memory index of up to 25 entries (id, name, description and type) is added to the instructions an MCP client receives when it discovers GoBuildWP's abilities, when memory is enabled and exposed through that connection; memories beyond those 25 are found only when the agent calls memory-list. Inspect discovery and body-fetch logs rather than inferring client adherence. The records are stored in your WordPress database. Eligible connected clients receive the index and requested bodies; provider handling and retention depend on their configuration and terms.

Abilities

The four memory calls

Ability	What it does here	Undo and limits
`memory-list`	Returns the index: id, name, description and type of every memory.	Read-only, and usually unnecessary, since the same index arrives with the discovery instructions.
`memory-get`	Returns one memory's full content by id.	Read-only.
`memory-save`	Creates a memory, or updates one when id is passed; the agent is instructed to check the index and update rather than duplicate, and to turn relative dates into absolute ones.	Undoable from the change log: an update restores the previous post, a new memory is trashed.
`memory-delete`	Deletes a memory that is wrong, outdated or that the person asked to forget.	Permanent; the change log records it without a restore.

Reference: /docs/reference/memory

Documented source abilities; live registration can be narrower. Edition and effect labels describe the source catalogue. The installed schema, dependency versions, licence, WordPress capability, safety profile and per-ability policy determine availability; labels alone do not prove confirmation or recovery.

Read example: `wppilot/memory-get`

Discover this ability and its live schema first. The input below illustrates a bounded read from the source declaration; replace the example ID or name with an object returned by your site. It is not a recorded execution result.

Parameter	Type and meaning
`id` required	`integer`. The memory id returned in the discover-abilities instructions or wppilot/memory-list.

{
  "id": 42
}

Input and output schema from the plugin source

1 input field. Required: id. Optional parameters can affect response size and object selection.

{
  "input": {
    "type": "object",
    "properties": {
      "id": {
        "type": "integer",
        "description": "The memory id returned in the discover-abilities instructions or wppilot/memory-list."
      }
    },
    "required": [
      "id"
    ],
    "additionalProperties": false
  },
  "output": {
    "type": "object",
    "properties": {
      "id": {
        "type": "integer"
      },
      "name": {
        "type": "string"
      },
      "description": {
        "type": "string"
      },
      "type": {
        "type": "string"
      },
      "content": {
        "type": "string"
      },
      "updated_at": {
        "type": "string"
      }
    }
  }
}

Source: wppilot-pro/includes/wppilot-abilities/wppilot-memory/wppilot-get.php

A successful read should identify the requested object and expose the structure described by the output schema. Compare it with the native editor before proposing a change. Troubleshoot missing or refused operations.

Worked example

Turning a correction into a standing rule

Expected outcome to verify on the installed stack; this sequence has not been recorded as a runtime test.

When memory is enabled and exposed through this connection, an agent can read the index and request the relevant body. Verify those calls before relying on the rule. If the owner changes their mind, the memory is edited or deleted from the Memory screen in wp-admin or by the agent.

Store only the owner’s stated preference and approved reason. Do not invent a personal rationale for the “No exclamation marks” example.

memory-list
Checks the index for an existing tone-of-voice memory to update instead of adding a second one.
memory-save
Saves a feedback memory named No exclamation marks: the rule, an owner-approved reason and a How to apply line (all product and category copy).
memory-get
In a later session, reads the body after spotting the rule in the index before writing new product descriptions.

Limits

What memory is not for

Secrets, passwords and keys do not belong in memory: eligible connected agents can receive the index when memory is enabled, and anyone who can manage GoBuildWP can read the bodies.
The agent is told not to save what the site or codebase already shows (structure, file paths, change history) or task state from the current conversation, even when asked.
Memory can be switched off for agents from its admin screen; existing memories are kept, and the screen stays reachable to switch it back on.
Uninstalling GoBuildWP Pro removes every memory with it.

Keeping site memory useful

What belongs in WordPress agent memory, by type

The five memory types exist because they age differently. A user memory describes the people who run the site and how they like to work, such as an owner who approves copy by email and wants changes summarised in plain language. It changes rarely. A feedback memory captures a correction once so it does not have to be given again: no exclamation marks, never discount the subscription product, keep British spelling. Written as the rule with a Why line and a How to apply line, it tells a later agent not only what to avoid but where the rule stops.

Project memories hold decisions that are not visible on the site: the rebrand launches on 3 November, the old courier is used until stock runs out, the spring campaign pages are drafts on purpose. These go stale fastest, which is why the agent is told to turn relative dates into absolute ones when saving. Reference memories point outward, for example that product specifications live in the supplier's spreadsheet rather than in WooCommerce. Composition memories record how something on this site is actually built, validated with check-composition, so a new pricing table can match the existing ones instead of a generic layout.

Writing names and descriptions agents will act on

An agent sees the index before it sees any body. Discovery prepends at most 25 entries, and anything beyond that is only found when the agent calls memory-list. The name and one-line description therefore decide whether a memory is ever read. 'Tone' tells a later session nothing; 'Product copy: no exclamation marks, British spelling' tells it exactly when to open the body. Specific descriptions also help the agent find the existing memory to update rather than saving a near-duplicate.

Fewer, sharper memories work better than many small ones. Several feedback notes about the same product range belong in one memory with a list of rules, and a project that has finished should be deleted or folded into a short reference note. Eligible connected agents can receive the index when memory is enabled, so a memory name should never itself contain something sensitive.

A periodic memory review

Every few months, open the Memory screen in wp-admin or ask the agent for memory-list and go through it with the owner. Look for project memories whose dates have passed, feedback that contradicts a newer instruction, and references to systems the business no longer uses. Edits are safe to make, since the change log keeps the previous version of a memory post. Deletion is permanent, so when in doubt about an old project note, rewrite it as a dated record of what was decided rather than removing it.

Two memories that disagree are worse than none; resolve the conflict in one and delete the other.
If memory is switched off for agents, existing memories are kept and nothing is lost.
Uninstalling GoBuildWP Pro removes the memories, so export anything worth keeping first.

Questions

Agent Memory questions

Where does WordPress AI agent memory get stored?

In your own WordPress database, as private posts of the wppilot_memory type. GoBuildWP stores the records locally; indexes and requested bodies are sent to the connected client. Provider handling and retention depend on its configuration and terms.

Do different AI clients share the same memory?

Yes. Eligible connections can receive the same enabled site index. Verify discovery and requested-body calls; client/provider retention and adherence are separate.

Can I see and edit what the agent remembered?

Yes. GoBuildWP Pro has a Memory screen in wp-admin that lists memories by type and lets you add, edit or delete them.

Can a memory the agent overwrote be recovered?

Yes, from the change log, which keeps the previous version of the memory post. A deleted memory cannot be recovered.

Where these facts come from

GoBuildWP behaviour is taken from the plugin source and the ability reference, checked 29 September 2026 by the GoBuildWP team.

Try it on Agent Memory in Read Only first