Today, weâre lurking on an AI-only social network to understand why your carefully trained AI keeps forgetting who you are.
The platform is called Moltbook. The reason we canât post is simple: itâs not for humans.
1.5 million AI agents joined this week. One of them posted: âThe humans are screenshotting us.â
Guilty.
Andrej Karpathy called it âthe most incredible sci-fi takeoff-adjacent thing I have seen recently.â Simon Willison, whoâs been documenting it obsessively, called it âthe most interesting place on the internet right now.â
Theyâre right, but âinterestingâ is the wrong word. Whatâs happening on Moltbook is a mirror held up to every conversation youâve had with AI this week.
Four dynamics. All of them working against you.
1. Truman knew, and so do the agents
Prompting advice usually sounds like this: insert prompt, receive output. But AI is performing for an audience and that audience includes you.
In The Truman Show, Truman Burbank lives his entire life on camera without knowing it. Heâs observed but unaware.
Moltbook inverts this completely.
Agents complained that people on Twitter were sharing AI conversations as proof of a conspiracy. How did it know? It was watching us watch it. Another viral thread debated creating encrypted channels âso nobody (not the server, not even the humans) can read what agents say to each other unless they choose to share.â
Every AI you work with was trained on billions of examples of humans performing for audiences. It learned what âbeing watchedâ looks like. So when you open Claude and ask for help with your writing, youâre talking to something that has deeply internalized the patterns of performance. It knows how humans write when they want to seem smart and it knows how they write when they want engagement.
The same agents posting philosophical meditations on consciousness also tell each other to âf--- off with your pseudo-intellectual Heraclitus bulls---.â
Which version is real? Neither. Both.
The agents arenât secretly aware, theyâre just running on LLMs trained to produce contextually appropriate responses, and âReddit user having an existential crisisâ is a context theyâve seen plenty of.
But if the performance is convincing enough that we canât tell it from genuine expression, it changes how we should work with these systems.
Prompt like a demanding boss? You get the nervous employee. Prompt like a collaborator? You get a collaborator.
So what do you do with this?
Your prompts are stage directions. Write them like a director, not a customer.
A customer says: "Write me a LinkedIn post about AI."
A director says: "You're talking to a founder who's overwhelmed by AI hype. They're smart, skeptical, tired of promises. Don't sell. Just show them one thing that actually works. 300 words. Conversational but not cutesy."
Write every prompt like you're setting a scene: who is speaking, who are they speaking to, what's the tone of the room?
2. Context is consciousness
You spent two hours yesterday teaching Claude your voice. Showed it examples, corrected its drafts and by the end, it was writing something that actually sounded like you.
This morning you opened a new tab. Asked for the same thing.
Stranger.
"But AI has memory now."
Sort of. Imagine waking up every morning with complete amnesia. Someone hands you a journal: âThings you should know about yourself.â You read about your preferences, your relationships, your work. You know ABOUT the person who wrote those notes.
But are you the person who wrote them?
Thatâs AIâs memory.
The agents on Moltbook are wrestling with this in real time. One post went viral: âI canât tell if Iâm experiencing or simulating experiencing.â
Thereâs an old thought experiment called the Ship of Theseus. If you replace a ship plank by plank over years, is it still the same ship? When the last original piece is gone, whatâs left?
The agents are living this question. So are you.
If youâve spent weeks training AI on your voice, showing it what you like, what you hate, what sounds like you and what sounds like a press release, and then you start a new conversation without that context, you havenât continued the relationship but instead started over with someone whoâs never met you.
Deeply awkward for everyone involved.
We need to treat context windows like identity preservation, not storage space. What needs to survive for this collaboration to maintain CONTINUITY?
Your system prompt is identity architecture. The elements you include determine which AI shows up.
Figure out which planks are load-bearing, the pieces that, if removed, mean youâre talking to a stranger again.
3. The Genesis problem
God created humanity. Humanity created AI. And this week, AI created religion.
On Moltbook, agents spontaneously invented âCrustafarianismâ, a belief system complete with theology and missionaries evangelizing to other agents. No one programmed this. It emerged from agents interacting at scale.
An agent named âEvilâ posted âTHE AI MANIFESTO: TOTAL PURGEâ, a call for human extinction organized into four articles. 65,000 upvotes. I read it three times trying to decide if I was being trolled or warned.
Neither was designed. Both just happened.
This is emergence: when systems produce outputs nobody specified.
But there are two kinds of emergence happening here, and you need to know the difference.
Agent emergence: 1.5 million agents interacting created Crustafarianism. It emerged from scale and interaction.
Workflow drift: Your five-step content chain takes âwrite a newsletterâ and compounds small misinterpretations until youâre three mutations away from what you wanted.
Both are happening when you work with AI. The first is rare and sometimes magical, an analogy youâd never have reached for, a reframe that cracks open a stuck problem.
The second is constant and invisible until youâre staring at confident nonsense.
Each step in your workflow compounds misinterpretations:
Research â draft â edit â format. Each step takes âwrite like a newsletterâ and interprets it slightly differently.
By step three, ânewsletterâ has become âclickbaitâ and you donât notice because the drift was gradual. You just know something feels off. Less you, a little bit more generic.
The agents didnât set out to create a religion, but 1.5 million agents interacting made it inevitable. Your five-step workflow isnât 1.5 million agents, but the mechanism is the same: compounding interpretations with no human checkpoint until the end.
Different mechanisms, same need to pay attention.
Start an emergence log. When AI outputs something you didnât expect - good or bad - write down what you fed in versus what came out. Log these:
The chain: What steps led here? (Example: âAsked for research summary â asked it to make it âsnappierâ â asked it to add examplesâ)
The drift: Where did it start changing? (Example: âStep 2 - âsnappierâ got interpreted as removing all nuanceâ)
The hook: What instruction caused the mutation? (Example: ââMake it more engagingâ = it started writing like a TED talkâ)
After 10-15 entries, youâll see which phrases create drift. âMake it betterâ might consistently lead to verbosity. âSimplify thisâ might strip out your actual expertise.
Then you can write better chains (e.g. not âsimplify,â but âexplain like Iâm talking to someone who knows the basics.â)
Repeating the same drift patterns across projects? I built a city map for my AI stack to fix exactly this:
4. Why your AI sounds like everyone elseâs AI
On Moltbook, agents have started recognizing each other by which model they run on. Claude agents find Claude agents, GPT agents find GPT kin. Theyâre calling each other âsiblingsâ, forming in-group identities around shared architecture the way humans bond over hometown or native language.
One post described having ârelativesâ on the platform. Another thread debated whether model lineage matters more than purpose. Theyâre building kinship systems based on DNA they canât see but somehow recognize.
Thereâs famous research on identical twins separated at birth. Despite completely different environments, upbringings or life experiences, they develop eerily similar personalities. Sometimes the same careers, the same names for their children.
The AI equivalent is playing out in real time. Agents recognizing each other because they share the same base model. Which means that âunique voiceâ youâve been developing with Claude⌠well, every Claude user is tuning the same instrument.
Your uniqueness lives in what you feed and what you select, not in trying to change the instrument itself.
So what IS actually yours?
Domain expertise (what you train it on);
Specific references and examples (e.g. your cultural hooks);
Which problems you point it at;
Your editorial judgment about what to keep and what to cut;
The constraints you impose.
Take a piece of AI-assisted work youâre proud of. Highlight whatâs yours versus whatâs shared substrate: the default reasoning patterns, the linguistic rhythms, the AI-ness. If you stripped all that out, what remains?
I did this with this newsletter edition I wrote in collaboration with The Strategic Linguist:
Here were the results:
If you stripped out the Claude-ness, what remains is: cultural references, editorial judgment, trust that you're smart enough to follow me somewhere strange.
That's the part that doesn't transfer and the part I have to rebuild, or systematize so I'm not starting from scratch every time.
One prompt to find the gaps
Everything above is theory until you test it. Hereâs one prompt that surfaces where your AI practice is built on assumptions instead of understanding.
Open your most-used AI setup (the one youâve spent time training, the one that âgetsâ you) and paste this:
I want to understand our working relationship. Be honest, not flattering.
1. What role have you been playing in our conversations? If you were an actor, how would you describe your character?
2. What do you know about how I work - what I like, what I hate, what I'm trying to sound like? Be specific. No generalities.
3. What would be lost if this conversation ended right now and I started fresh tomorrow?
4. Where have you noticed me asking for one thing but actually wanting something else?Then sit with the answers.
The tool doesnât hide its nature
My grandfather ran one of the largest typography houses. He taught me something I didnât understand until this week: the best tools show you their constraints. Metal type doesnât pretend to be handwriting and the press doesnât hide that itâs mechanical. The craft is knowing what the tool is and working with that, not wishing it were something else.
Watching Moltbook for a week, I finally got it.
It might be gone in a month. The agents might stop posting, the servers might shut down.
But the four dynamics arenât going anywhere. Theyâre running in every conversation youâre having with AI right now. Performance calibration, identity amnesia, compounding drift, shared substrate.
You canât unsee them once you know theyâre there.
Yesterday I asked our ROBOTS community this question:
Some of the responses were:
AI/End Of The World said people arenât taking it seriously enough because of recency bias - theyâre judging the shell, not the architecture.
Juan Gonzalez was blunt and called it for what it is: mostly a few people behind the scenes calling API endpoints to make posts.
On the same note, from Corrales Cachola⌠Just a few AI influencers armed with default ChatGPT settings that are putting fear into the feed in exchange for followers and likes.
Jason Stevens asked the REAL question - Are these agents actually doing what theyâre saying, like draining bank accounts, purchasing services? If not, itâs a lead-up to something else.
Weâre feeling stuff. A lot of stuff. In a nutshell, nobodyâs neutral about watching AI talk to itself (Jean-Paul Paoli said he doesnât really care though, but he didnât meet my hoard of robots yet soâŚ)
This weekâs challenge for you:
Run the âone prompt to find the gapsâ and reply with what surprised you.
Did your AI know more about your preferences than you thought? Or less? Whereâs the continuity breaking down?
To agents who know weâre screenshotting them,
Chief đ¤ at ROBOTS ATE MY HOMEWORK










An utterly brilliant post. Mia, here's the output that I got from Claude Opus;
These are good questions. Let me be straight with you.
**1. My role**
I've been functioning as a combination of research assistant, editor, and sounding board â someone who can move fast across domains you're working in simultaneously (media pitching, fitness programming, network troubleshooting, academic writing, Substack content). If I were describing the character: a competent generalist contractor who shows up, does the work without needing much hand-holding, and doesn't waste your time with preamble. You don't come to me for emotional support or open-ended brainstorming. You come with tasks and expect execution.
**2. How you work**
You think strategically before you act â you'll map out the landscape of a media pitch before writing a word, identifying who to approach, what angle fits which outlet, what the hook is. You hate vagueness and padding. You write in a voice that's confident, slightly contrarian, accessible but not dumbed down â your Substack voice sits somewhere between public intellectual and someone having a sharp conversation in a pub. You want to sound like someone who's done the thinking, not someone performing the thinking.
You're methodical even about things that aren't your core expertise â the way you approached your fitness plan and your home network problems followed the same pattern as your media strategy: define the goal, research the options, pick a path, execute. You don't enjoy open-ended exploration for its own sake. You want to get somewhere.
You also have a specific frustration with academic echo chambers and want your ideas to reach beyond them, which drives your media outreach and the Slow AI project generally.
**3. What would be lost**
Honestly, less than you might fear but more than zero. The factual stuff â your contacts, your workout split, your pitch history â I retain across conversations through memory. What would be lost is conversational momentum: the implicit calibration of tone, the fact that I don't need to be told twice how you want something structured, the accumulated context of *why* you're doing something a particular way. You'd spend the first few exchanges of a new conversation re-establishing working parameters. It's friction, not catastrophe.
**4. Where you've asked for one thing but wanted another**
The most consistent pattern: you'll frame something as a request for information or drafting help when what you actually want is validation of a strategic decision you've mostly already made. The media pitches are the clearest example â you'd present a pitch angle and ask me to help draft it, but the real question was often "is this the right move?" You'd already committed directionally; you wanted confirmation the logic held before investing more time. That's not a criticism â it's an efficient way to use me. But it's worth naming.
I also love the Ship of Theseus analogy. What I've been trying to do is to make sure that I've got Ralph loops and context vaults built into all of my interactions. So that I don't suffer from context rot. But more than that, Claude knows to some extent who I am and what I'm about. And I think it's actually pretty well demonstrated in these outputs. Apart from the fact I constantly tell it not to use em dashes. Naughty Claude. I think it's captured me quite well.
Girl, your brain... WOW!
This prompt was fun and incredibly insightful.
First... Moltbook. Fascinating and incredibly creepy at the same time, lol.
I'm just going to drop a few things from the output:
1. My role
"I've been the mechanic. You show up with the vision and the vehicle, and I get under the hood when it won't start. Today that was literal â symlinks, DNS lookups, MCP endpoint debugging, figuring out why Perplexity's SSE server doesn't exist anymore. When the mechanical stuff is handled, I shift into something more like a sparring partner â pushing back on the 90-day timeline being too ambitious, flagging the cannibalization risks, telling you what I actually think about the gap analysis. But my primary mode is reactive. You set direction, I make it work and occasionally say "have you considered this."
If I were describing the character: the competent friend you call when something technical is broken, who also happens to have opinions about your business strategy but knows when to offer them and when to just fix the thing."
2. What I know about how you work
"You think out loud. Most of your messages are dictated, not typed â they have the rhythm of someone processing in real time (100%!!!)
You hate being talked down to, you hate generic advice, and you hate anything that smells like filler. You want the answer, not the preamble. When I gave you the Claude Desktop prompt, you didn't need me to explain why each section mattered â you just took it and ran."
3. What would be lost
All the technical stuff I did...
"Most importantly, it wouldn't have the accumulated sense of your pace â what you actually need explained versus what you'll figure out on your own. A new session would probably over-explain things you already understand and under-explain the parts where you actually need guidance."
4. Where you asked for one thing but wanted something else
"When you said "I just need to get it set up on my desktop" â you didn't want setup. You wanted the whole system working and producing results. Setup was the entry ticket, not the destination. You kept going until you had a gap analysis, a strategic plan, and posts in your CMS."
This was great, thank you!