Use Character AI pinned memories to keep selected messages available as story context, then review the selection when the story changes. The important decision is often which old message should stop representing the current situation.
This guide uses official documentation checked November 11, 2026, and an original fictional message audit. We have not operated a logged-in account or tested model recall. EchoMelon publishes this guide and operates an AI character roleplay product.
Find the message controls
The official Pinned Memories help page describes these controls:
| Task | Web instructions | Mobile instructions |
|---|---|---|
| Pin a message | Open its menu and select Pin message. | Long-press the message and select Pin. |
| Review the collection | Open Chat Details. | Open the three-dot menu at the top of the chat. |
| Remove a pin | Select the pinned message in Chat Details. | Long-press the pinned message to unpin it. |
The web removal instructions stop at selecting the message; check the removal control your interface offers rather than assuming another button name.
Character.AI's Memory announcement describes another layout: open the notebook icon in the chat header or Memory in the chat menu. It places pinned messages within Story Memory, alongside context you write yourself. Facts are separately captured information, while Memory Usage describes how context is being used. These are related features, not interchangeable names for pinning one message.
Follow the layout visible in your account. The help page and plan documentation disagree about allowances, so check your account's displayed limit instead of relying on a universal number. Pinning a conversation in the chat list is also a different task from selecting a message inside it.
Audit seven candidate messages
Meet three fictional adults: Rosa, 41, coordinates a neighborhood puzzle swap; Dev, 36, helps collect donations; Mina, 52, manages their community room. The numbered messages below are authored examples, not transcripts. The numbers are references for this worksheet.
At Monday's checkpoint, Rosa and Dev have agreed on their collection arrangement. Read each whole message before deciding whether to pin it:
| Message | Authored text | Selection decision |
|---|---|---|
| 1 · Monday 09:00 · Rosa | “Dev and I agreed: we'll collect the donation crates on Wednesday at 10:00 in the reading room.” | Keep initially. A confirmed arrangement with a time and place. |
| 2 · Monday 09:02 · Dev | “Maybe we could use the courtyard if it's sunny.” | Skip as current instructions. Nobody has accepted this suggestion. |
| 3 · Monday 09:04 · Dev | “I think Mina has printed the donor labels, but I haven't asked.” | Keep if the unanswered printing question matters. Preserve the uncertainty. |
| 4 · Monday 09:05 · Rosa | “That pigeon looks as though it owns the building.” | Skip for this task. It adds atmosphere, not a collection requirement. |
| 5 · Monday 09:06 · Rosa | “Our club records a donation as complete only after the donor marks the inventory card.” | Keep. This established club convention affects the upcoming collection. |
| 6 · Tuesday 11:20 · Mina | “The reading room is unavailable on Wednesday. Could you collect in the workroom at 11:00 instead?” | Don't use as the final agreement. It reports a problem and proposes a replacement. |
| 7 · Tuesday 11:25 · Rosa | “Dev and I have both confirmed Wednesday at 11:00 in the workroom. This replaces our 10:00 reading-room arrangement.” | Use as the replacement. It explicitly records acceptance and supersedes message 1. |
The decisions serve this particular story. A joke could deserve a pin if it later becomes a password or a meaningful shared memory. Here it has neither role. Likewise, a proposal may matter as a proposal without becoming an agreed plan.
Message 3 records Dev's unverified belief. Saving it should not become an excuse to write “The donor labels are printed” in another note. If a message mixes a confirmed arrangement with an assumption, consider whether preserving the entire message helps or creates ambiguity.
Replace the stale agreement at the right moment
At Monday 09:06, the suggested selection is messages 1, 3 and 5. That records the accepted arrangement, the unresolved printing question and the club convention.
At Tuesday 11:20, message 6 makes the original location unavailable, but the proposed alternative is not yet accepted. Don't silently convert that offer into a booking.
At Tuesday 11:25, message 7 establishes the new agreement. Now review the saved collection:
- Locate message 1 and remove its pin so the old arrangement no longer sits among your selected current instructions.
- Pin message 7, which records the accepted replacement.
- Reopen the collection and check for 3, 5 and 7. Confirm that 1 is no longer pinned.
The earlier agreement remains part of the story's history. Removing its pin is not a request to delete the conversation, erase model knowledge or rewrite other memory entries. Review any separately written notes containing the old arrangement as their own task. Nothing in the update confirms whether the labels are printed.
Keep a small maintenance note
Copy this for each message you retain:
Message reference:
Why keep it:
Confirmed, proposed, or uncertain:
What would make it outdated:
Still pinned when checked: yes / no / not checked
Checked at:
For message 7, the expiry condition could be another accepted change to Wednesday's collection. For message 3, it could be learning whether the labels have been printed. If you need help composing a new summary, use our roleplay recap guide; this worksheet tracks saved-message choices instead.
Check the collection and the reply separately
These checks are proposed, not performed here. First reopen the relevant panel: are the intended messages visibly pinned? Record that observation separately from anything the character says.
Then ask a question that does not supply its answer, such as “When and where are we collecting the crates?” or “What do we know about the donor labels?” Record the actual reply as correct, contradictory, unanswered or untested. A correct answer once cannot establish reliable recall or an improvement caused by pinning.
Character.AI's limitations guide acknowledges forgotten details and inconsistent responses. Don't assume pins transfer automatically to another chat, or that information in saved context is necessarily something every character knows. Keep reviewing what is saved and what the conversation actually establishes.
Comments
Join the discussionNo comments yet. Be the first to comment.

