
*This is less a tutorial and more an honest account of how a throwaway message became a project — and what that taught me about working with AI.*

---

A few weeks ago, a friend and I were doing what most people do at 10pm on a weeknight — complaining about being single heading into winter. It escalated quickly.

![WhatsApp screenshot of the original cuffing season app idea](/images/blog/cuffing-season-whatsapp.jpg)

We were going to be rich. In winters, at least.

I forgot about it. He probably did too.

But I'd dropped it into Woxpas — my personal memory layer that connects to my AI tools — just as a passing thought. Barely a sentence. No plan attached to it.

What happened over the next few days is what this post is actually about. Not the app (it's a scaffold right now, not a product). But the workflow — specifically how I went from a WhatsApp joke to a running project structure across three different AI tools, without ever having to repeat myself or re-explain what I was building.

That part genuinely surprised me. So I figured it was worth writing down.

---

If you'd rather watch than read, I also made a short video walking through the whole workflow — you can see exactly what each AI session looked like in practice:

`[YOUTUBE EMBED]`

Otherwise, here's the full story.

---

## The save that started it

I didn't think much of it at the time. After the WhatsApp thread I just opened Woxpas and typed roughly what I'd said to my friend: *"thinking of a new idea - something to do with dating in the cuffing season. it seems interesting - need to explore more."*

No tags. No project folder. No "is this worth keeping?" deliberation. Just saved it and moved on.

This is the part that sounds small but isn't. Most ideas die because the effort of capturing them properly exceeds the energy you have in the moment. Woxpas removes that friction — you save the mess, it handles the structure. I've started treating it like a brain dump that actually has a memory.

---

## A few days later — ChatGPT expands it

I wasn't planning to work on the idea. I just opened ChatGPT and, on a whim, asked what was in my vault. GPT called Woxpas via MCP and returned a list of things I'd saved. The cuffing season note was right there.

I asked it to expand on the concept — what would the app actually do, who's it for, what makes it different from just using Hinge in October. We went back and forth for a while. By the end I had something that felt like a real product direction: a time-boxed dating experience built around the seasonal psychology of wanting company in winter, not necessarily forever.

Then I asked GPT to save the expansion back to my vault. One prompt. Done.

---

## Claude picks it up — no re-explaining required

Next day, different tool. I opened Claude and typed: *"Pull my cuffing season dating app idea from my vault and recommend a tech stack."*

Claude retrieved everything — the original note and GPT's full expansion — and came back with a proper recommendation based on what the app was actually supposed to do. It understood the concept because the context was there. I didn't summarise anything. I didn't paste in the previous conversation. I just asked.

This is the bit that still gets me. Two different AI tools, two different days, and the second one picked up exactly where the first left off. That's not how AI is supposed to work — except now it kind of is.

I saved Claude's recommendation back to the vault.

---

## Claude Code — from idea to scaffold

With a product direction and a tech stack in the vault, I opened Claude Code and gave it a simple prompt: pull the plan and set up the project.

It did. Files created, dependencies installed, basic project structure in place. What exists right now is a scaffold — the bones of something, not a finished product. Login screen, homepage, core navigation. You could show it to someone and they'd understand what it's trying to be, but there's a long road between here and the App Store.

I'm going to keep building it. Partly because it's a fun problem, partly because I want to see if the idea my friend and I joked about actually has legs. If it becomes something real, Part 2 of this post will be a lot more interesting.

---

## What I actually learned from this

The app is almost beside the point. What this experiment showed me is that the context problem with AI tools — the constant re-explaining, the fresh-slate frustration every time you switch tools or start a new session — is solvable. Not perfectly, not magically, but genuinely.

The workflow is simple enough that I now do it without thinking:

- Save ideas when they happen, without organising them
- Start AI sessions by asking what's in the vault
- Save outputs back before closing a session
- When switching tools, let the new AI pull context instead of you providing it

That last one is the habit that changed things for me. "Pull X from my vault" is three words. It shouldn't feel like a revelation. But compared to copy-pasting between tools or re-explaining a project from scratch, it kind of does.

---

## Where this goes next

The scaffold is sitting on my machine. I'm planning to keep building — probably in short sessions, probably across multiple tools depending on what I need. When there's something worth showing, I'll write Part 2.

If the app turns out to be terrible, I'll write that too. The point was never really the app. It was figuring out a way to work across AI tools without losing everything between sessions.

That part already works. The rest is just building.

---

*Woxpas is the memory layer that made this workflow possible — it connects to Claude, ChatGPT, Cursor and other MCP-compatible tools. [woxpas.ai](https://woxpas.ai)*


I Used 3 AIs to Turn a WhatsApp Joke Into a Working App Scaffold (Part 1)


Last week, 1.5 million people tried to leave ChatGPT. Most of them discovered something uncomfortable: months of carefully built context — their preferences, their projects, their working style — was locked inside a platform they no longer wanted to use.

Anthropic rushed out a memory import tool. Google started testing chat history imports for Gemini. Both solutions involve the same clunky process: export your data, copy it, paste it somewhere else, hope the new system understands it. It's a one-time migration, not a real solution.

And it exposed a deeper problem that nobody in AI is talking about honestly.

## Every AI Platform Wants to Own Your Memory

Claude has memory. ChatGPT has memory. Gemini is building memory. Copilot has memory. Each one stores what it learns about you in its own walled garden. None of them talk to each other.

If you use Claude for writing, ChatGPT for research, Cursor for coding, and Llama locally for sensitive work — congratulations, you now have four separate AI identities. Four cold starts every time you switch tools. Four platforms that each know a fraction of who you are and how you work.

This isn't a bug. It's a business model. The more context an AI has about you, the harder it is to leave. Your memory is the lock-in.

## The Pentagon Fallout Made This Visible

When OpenAI announced its Pentagon deal on February 28, the backlash was immediate. ChatGPT uninstalls surged 295% in a single day. One-star reviews jumped 775%. The "Cancel ChatGPT" movement went mainstream overnight.

But here's what made it painful: people didn't just want to leave. They wanted to leave *with their stuff*. Reddit threads filled with guides on how to export data, how to extract memories, how to migrate to Claude or Gemini without starting over. The switching cost wasn't the subscription fee. It was the context.

Anthropic's import tool was a smart response, but it's fundamentally a band-aid. You paste a prompt into ChatGPT, get a text dump, paste it into Claude. It works once. But what happens when you update your preferences next week? What happens when you want to use a different model for a different task? You're back to managing memory across platforms manually.

## The Real Problem: Memory Shouldn't Live Inside the Model

Think about how your computer works. Your files don't live inside Chrome. They live on your filesystem, and any application can access them. You don't re-upload your documents every time you switch browsers.

AI memory should work the same way. Your preferences, your working context, your projects, your communication style — that's *your* data. It should live in a layer you control, accessible by whatever AI you choose to use at any given moment.

This is what we're building with Woxpas.

## A Memory Layer You Own

Woxpas is a sovereign memory system that sits between you and your AI tools. Instead of each platform maintaining its own siloed understanding of who you are, Woxpas holds your context in one place and makes it available everywhere.

The simplest version of this is a portable preference file. Plain markdown. Editable by you. Loadable by any LLM at the start of a session. No embeddings, no vector databases, no complex infrastructure. Just a file that says: here's who I am, here's how I work, here's what I'm working on.

When an LLM learns something new about you — your preferred coding language, a project you're working on, how you like your responses formatted — it writes to your Woxpas preference file at the same time it writes to its own native memory. Dual-write. The LLM's local memory is a convenience cache. Woxpas is the source of truth.

Switch from Claude to ChatGPT? Your preferences are already there. Spin up Llama locally for sensitive work? Load the same file. Try a new model that launched yesterday? It already knows you.

We just shipped this. It's called the [preference profile](/docs/preferences) — you can read the full docs on how it works, including auto-injection, dual-write sync, and conflict detection.

## Not Just Preferences — A Full Memory Layer

The preference file handles the lightweight stuff: tone, tools, style, role. But Woxpas goes deeper. Our extraction pipeline processes everything you save — meeting notes, ideas, decisions, tasks — and builds a structured knowledge graph of entities, relationships, events, and commitments.

When an AI agent needs to act on your behalf, it doesn't just know that you prefer Python. It knows who John is, what your meeting with him is about, what you decided last week, and what's on your plate today. That's the difference between an AI assistant and an AI that actually works for you.

## Keeping Memory Clean

The hardest part of any memory system is keeping it accurate. Preferences drift. Facts change. You moved from London to Berlin, but your AI still thinks you're in the UK.

We solve this with conflict detection built directly into the preference file. When a new entry contradicts an existing one, Woxpas flags it. These conflicts surface in your daily digest — a personalised briefing that already exists in Woxpas — so you can resolve them with a single tap. The file stays clean, and every AI session going forward has accurate information.

The full cycle looks like this: an LLM learns something about you, it dual-writes to native memory and Woxpas, you can edit the file manually anytime, conflict detection catches contradictions, the daily digest surfaces them, you resolve, and the clean file loads into your next session on any platform.

## Why This Matters for Agents

Every major AI company is racing to build agents — AI systems that can take actions on your behalf. But here's the thing: an agent without context is just a tool following instructions. An agent with access to your memory, your preferences, your tasks, your relationships, your decision history — that agent can actually exercise judgment.

And because Woxpas isn't tied to any specific agent framework, LLM provider, or orchestration layer, your context travels with you. OpenClaw, LangChain, CrewAI, your own custom setup — they all become interchangeable execution layers running on top of the same memory.

The moat in AI isn't going to be the model. Models are commoditising fast. The moat is the memory. Whoever holds the richest, most accurate understanding of the user has the most valuable position in the stack. We believe that should be the user themselves.

## The Memory Layer You Own

Woxpas sits between you and whatever AI you're using. It gives every model, every agent, every tool access to the same understanding of who you are and how you work.

Models come and go. Last week proved that dramatically. But your memory, your context, your identity as an AI user — that should persist regardless of which model you're talking to, which company you trust, or which framework you're building with.

Your AI memory shouldn't be trapped inside someone else's product. It should be yours.

## Take back your memory

Woxpas is in beta now. [Create your account](/register), connect your AI tools, and never lose context when switching models again.


Your AI Memory Is Trapped. Here's Why That's About to Matter.


Every AI tool you use builds its own memory of you — and none of them share it.

You told Claude about your project structure. ChatGPT knows your writing preferences. Cursor has your codebase context. Slack holds your team decisions. But none of these tools talk to each other, and none of them ask what they should remember.

The result? You repeat yourself constantly, contradictions build up silently, and good ideas slip through the cracks.

## Woxpas fixes both problems

Woxpas is a **personal memory engine** — one unified memory layer that sits across all your AI tools and gives you full control over what gets remembered, corrected, or forgotten.

Here's how it works:

### Capture from anywhere

Drop in notes, PDFs, documents, or raw thoughts. Connect it to Claude, ChatGPT, Cursor, or your browser. Everything flows into one memory.

### Understand, don't just store

Woxpas doesn't just file things away. It extracts meaning — commitments you've made, decisions you've taken, facts you've stated — and maps how your ideas connect over time.

### Detect contradictions

When you told Claude one thing and ChatGPT another, Woxpas catches it. Conflicting information gets flagged so you can resolve it before it causes problems.

### Resurface what matters

Forgotten ideas come back when they're relevant. Overdue commitments get flagged. Your daily digest tells you what needs attention — without you having to go looking.

### You own it

No training on your data. Full deletion on request. Every answer cites its source. You decide what stays and what goes.

## Why this matters

AI memory shouldn't be something that happens *to* you inside each tool's black box. It should be something you *own* — portable, transparent, and under your control.

Woxpas is the memory layer those tools never had, and the one you've always needed.

## Get started

Woxpas is currently in beta. [Create your account](/register) and start building your memory today.


The Woxpas Blog

I Used 3 AIs to Turn a WhatsApp Joke Into a Working App Scaffold (Part 1)

Your AI Memory Is Trapped. Here's Why That's About to Matter.

What Is Woxpas? The Memory Layer You Own