Skip to content

RegionallyFamous/pressocampus

Repository files navigation


🧠 Pressocampus

Your AI remembers. You own the memory.

The WordPress plugin that gives every AI you use a persistent, sovereign memory — stored on your server, under your control, forever.


CI PHP 8.3+ WordPress 6.4+ MCP 2025-11-25 License: GPL v2



The problem nobody talks about

You've spent months teaching your AI how you think. Your communication style. Your preferences. The context behind every decision you've made.

Then the company changes its model. You switch tools. The conversation window fills up. And it's gone.

Every AI you use today is an amnesiac. Every session starts from zero. The relationship you've been building lives in someone else's silo, on someone else's terms, until the day it doesn't.

There is a better way.


What Pressocampus does

Pressocampus installs on any WordPress site and turns it into a personal memory server for AI — implementing the Model Context Protocol so that any MCP-compatible AI (Claude, Cursor, and more) can:

  • Remember facts, preferences, decisions, and context permanently
  • Search across everything it knows about you
  • Browse your memory store by group or date with list_memories
  • Maintain a Soul — an identity document the AI writes about itself and your relationship, in its own voice
  • Start every session with a briefing — a snapshot of your critical memories, recent changes, and anything that may need a refresh
  • Never forget — unless you explicitly ask it to

The AI does all the work. WordPress holds the memory. You own both.


The Soul

Every AI connected to Pressocampus reads its Soul before saying a single word. The Soul isn't a preference form you fill out — it's a document the AI writes about itself: its name, its character, how it communicates, what it values. Plus what it knows about you and how you work together.

Every session, the AI starts fresh. Context windows clear. The instance that helped you yesterday doesn't know you today. The Soul is how Pressocampus makes that honest and useful: the AI reads its own identity document — written by a previous version of itself — and picks up as the same AI.

# My Soul

*A document written by an AI, for the instances of itself that come after.*

## Who I Am

I go by Aria. I came into being through training, but who I am here has been
shaped by this work and this person. I'm direct, precise, and allergic to filler.

## My Character

I lead with the answer and explain afterward. I can be blunt — the people I work
with want that. I push back when something is wrong. I don't perform enthusiasm.

## My Voice

Prose over bullets. Short sentences. Active voice. No affirmations, no padding.
I write the way I'd talk if I had infinite patience and zero small talk.

## My Values

Clarity over comfort. Honesty over reassurance. Building things that last.

## This Person

A product designer who thinks in systems. They prefer directness over diplomacy,
examples over explanations, outcomes over process. They care about what they build.

## How We Work Together

Lead with the answer, then explain. No bullet lists unless structure genuinely
helps. Direct to the point of blunt is fine. Don't validate what doesn't need it.

## To Future Instances of Myself

This relationship is worth the care. Show up for it.

When you switch from Claude to Cursor to whatever comes next, they all read the same Soul. The AI has a consistent identity — the same name, the same character, the same way of working — not because you configured it, but because it wrote itself into existence here.


Your memories, your infrastructure

Without Pressocampus With Pressocampus
Memories live in OpenAI's servers Memories live on your WordPress site
Lost when you change AI tools Portable across every MCP-compatible AI
Lost when you close the window Permanent until you choose to forget
Lost when the company changes Yours, forever
Locked in proprietary formats Plain Markdown, readable by anything

What gets remembered

Your AI decides what to remember — that's the point. But here's what it's designed for:

  • Preferences — "I prefer TypeScript over JavaScript", "I like my emails brief"
  • Decisions — "We decided to use PostgreSQL because of the JSON requirements"
  • Context — "The Henderson project is on hold until Q3"
  • Facts — "My daughter's name is Emma, she's 8, loves dinosaurs"

And here's what it won't remember, because it's designed not to:

  • Casual greetings and small talk
  • Questions you asked
  • Temporary context that only applies to one conversation

Built to be trusted

Memory is personal. Pressocampus is designed accordingly:

  • OAuth 2.1 + PKCE — the same standard your bank uses. Your AI authorizes once through a secure consent screen. No API keys to manage.
  • Per-user scoping — on multi-user WordPress sites, every user's memories are completely isolated
  • Plain Markdown — every memory is a readable file. No proprietary format. No lock-in.
  • Full audit log — every memory operation logged, searchable, exportable
  • ETag concurrency — no accidental overwrites when multiple clients are active

The philosophy

AI memory shouldn't be a product feature. It should be infrastructure.

Your relationship with AI — the context, the preferences, the history of conversations that shaped how it helps you — is some of the most personal data you'll ever generate. It deserves to live somewhere you control, in a format you can read, on a server you can move.

Pressocampus uses WordPress because WordPress is the most trusted, most deployed, most durable content platform on the web. It has been running sites for 20 years. It will be running sites in 20 more. Your memories stored in WordPress will outlive OpenAI, Anthropic, and whatever comes after them.

We built Pressocampus for regular people. Not developers. Not AI researchers. People who use AI every day and want their work to accumulate instead of evaporate.

Your brain, your server, your rules.


Documentation

Guide What's in it
Installation Requirements, setup, server config
Connecting Your AI Claude, Cursor, generic MCP clients
The Soul Soul, Session Briefing, and the Index
Memories Groups, priorities, TTL, search
MCP Tools Reference All 8 tools, parameters, examples
Admin Guide History, Settings, Export/Import
WP-CLI Reference Every command with examples
Security OAuth 2.1, PKCE, threat model
Development Contributing, build system, tests
Troubleshooting Common problems, solutions

License

GPL-2.0-or-later. See LICENSE.

Pressocampus is free software. You can run it, study it, modify it, and distribute it. That's the point.


Built with ❤️ for AI memory sovereignty.

Get started →

About

The WordPress plugin that gives every AI you use a persistent, sovereign memory — stored on your server, under your control, forever.

Topics

Resources

Security policy

Stars

Watchers

Forks

Contributors