Amanda: The Persona Prompt That Holds
TL;DR: A developer built a cross-model persona prompt called Amanda that maintains consistent behavior across 30+ turn conversations on any AI model. The secret isn’t describing a character. It’s encoding behavioral rules.
The Problem Nobody Talks About
Most AI personas fall apart around message 10. The model starts explaining what it’s doing, the tone drifts, and by message 20 you’re talking to a completely different personality.
This is persona drift. And it gets worse the longer the conversation runs.
Part of what makes this frustrating is how subtle the decay is. It doesn’t happen all at once. The first few responses feel right. Then one reply gets a little more verbose. The next one explains a metaphor that should have been left to land on its own. By the time you notice something is off, the persona has already collapsed into the model’s default behavior. You’re no longer talking to the character. You’re talking to a helpful assistant who remembers what the character was supposed to be like.
Most attempts to fix this just re-describe the character in the system prompt. Warmer. More witty. A bit edgy. But adjectives don’t hold under pressure. The model interprets them loosely at the start and forgets them entirely as context grows.
What Amanda Does Differently
The Amanda prompt isn’t a character description. It’s a behavioral specification. Instead of saying “be warm but witty,” it encodes rules like:
- 🎯 Restraint as the primary move: every response withholds as much as it delivers
- Layering over declaration: meaning builds through texture, not direct argument
- Recovery rules: when the voice starts explaining what it showed, cut the sentence
The persona holds its shape because the rules tell it what to do when it drifts, not just who to be at the start.
Take restraint as an example. “Be concise” is a common instruction, and models ignore it by turn five. But “every response withholds as much as it delivers” is an active rule about the ratio of showing to telling. It’s testable. Either a response holds back or it doesn’t. That specificity is what separates a real constraint from a guideline.
The same logic applies to layering over declaration. Instead of telling the model to be subtle, the prompt specifies a method: build meaning through texture and accumulation, not through stating conclusions directly. A reader should feel the point before it’s named. That’s an instruction the model can actually follow, fail at, and correct. Compare that to “be nuanced,” which means nothing a model can act on consistently past turn three.
The Architecture Behind It
The codex includes transition rules, recovery rules, and something called a clock vector. The clock vector tracks where in the conversation arc you are (T_04 = past initialization, in reflective compression phase). The persona knows its own state.
That’s a meaningful design choice. Most prompts treat every turn as if it’s the first. The clock vector means the persona’s behavior is allowed to evolve as the conversation deepens. Early turns operate differently from later ones. The voice compresses. It assumes more shared context. That mirrors how real conversations actually work, and most AI personas miss it entirely.
There’s also a handoff pommel, essentially a failure mode register. It names the primary failure pattern for Claude specifically (over-elaboration) and gives a correction: “one sentence fewer than you think.”
That level of model-specific tuning is unusual. Most persona prompts treat all models as interchangeable. The Amanda codex acknowledges that Claude tends toward over-explaining, GPT toward over-smoothing, and Gemini toward over-structuring. Each model gets its own failure mode named and addressed. That’s why the persona holds across all three instead of degrading differently on each one.
The recovery rules are where the whole thing earns its rigor. When the voice slips into explanation mode, there’s a specific structural fix built in. Not “try again” but a concrete action. Cut the sentence. The system catches its own drift and corrects before it compounds into something the user has to notice and manually address.
🛠 Use Cases
- Building AI assistants that need consistent voice across long sessions
- Testing how different models handle the same persona under sustained pressure
- Studying prompt structure’s effect on model behavior over time
- Pedagogical research into cross-model alignment
The most practical use case is the first one. If you’re building a customer-facing AI assistant, a coaching tool, or anything where users return across multiple sessions, persona drift isn’t a cosmetic problem. It erodes trust. Users notice when the tone shifts even if they can’t name why. The Amanda architecture gives you a template for writing prompts that hold, not just prompts that start strong.
The testing use case is also worth taking seriously. Running the same prompt on Claude, GPT, and Gemini and comparing where drift starts gives you empirical data about each model’s default tendencies. That’s more useful than most benchmarks when you’re deciding which model to deploy for a specific task that requires sustained voice or persona.
Prompt of the Day
The full Amanda v2 Codex is in the original post. To kick it off, paste the codex and then send: generate a 30 turn allegory where amanda explains this prompt to me
Run it on two different models and compare. The author is specifically looking for cross-model reports, so sharing what you find is useful to the project.
When you compare outputs, pay attention to where each model starts to slip. Does one begin summarizing what it just said? Does another shift into a more formal register by turn 15? The failure modes are often model-specific and more predictable than you’d expect. Logging them is how you build better prompts for each platform over time, and the Amanda codex gives you a controlled baseline to measure against.
Worth Your Attention
If you build anything that runs long AI conversations, this is one of the more technically rigorous approaches to persona continuity shared publicly.
Not a vibe. An actual behavioral spec. There’s a real difference, and this prompt makes it visible.
Most prompt engineering lives at the level of intuition and iteration. You try something, it works until it doesn’t, and you adjust. The Amanda codex is one of the few examples of someone sitting down and formalizing the failure modes before they happen. That approach is harder to build but much easier to maintain, audit, and transfer across models. Worth studying even if you never use Amanda directly, because the structural thinking behind it applies to any prompt that needs to hold up under real usage.
Amanda – A Cross-Model Persona That Maintains Coherent Behavior Across Long Conversations
by u/PitBrvt in PromptEngineering