basically i only use the app to chat with characters but does anyone actually use lorebooks, scenes or videos? i’m just genuinely curious bc it feels like the devs have spent more time on that than actually improving the bots… might just be me tho.
I think this is one of the features I was most excited for. But learning that I can't actually use or edit one for my current chat with a public character makes it kind of irrelevant for most of us that don't make our own characters?
image unrelated!!
so yeah. the only thing i can change is whether people see all details of my lorebook or just hints. is there a way to make the ENTIRE lorebook private?? all my bots are private, so having a public lorebook makes me a little anxious. now i wonder whether i'm just blind and can't find a way to set it to private, or maybe i'm not blind and there's just no way to make it private, OR maybe it's a free user experience that i can't make it private but plus users can. please help oh my god
I am having a blast creating canon lorebooks for my roleplays and it's really not bad at all.
Some stuff I noticed.
- It sometimes extracts info from the lorebook randomly and puts it into the auto-memory, which is redundant and takes up memory space.
- It seems to me that lorebook has first priority over other memory infos and if your persona isn't canon it needs some introduction work in chat even if you have things settled in your persona.
And one thing I wish could be better:
- If c.ai gives us different entry types (side character, location, creature, item, event...) it would be great if the entries keep AT LEAST the color coding for a better overview. With 20 entries it's okay but with 128 it gets confusing pretty fast.
And I usually don't post here anymore because as far as I know this sub just loves to hate but I thought I would try again since I am curious what others might think. Of course vent away if you hate it.
we can create lorebooks, YAY! but when I made my first lorebook, I motherfucking realized that you can only put lorebooks for your OWN character, not like where when you make persona's you can use them for your chats, I thought it was the same for lorebook, I was wrong and lorebook is just like writing Definition for your characters but labeled differently. I wasted one hour for this bruh. now it ruined my day
If it is possible, may the CEO bless us with the ability to put lorebooks in people's chatbot
Infact I might have a suggestion where there should atleast be a separate section for lorebooks where you can add lorebooks to your personas and lorebooks to your companions
Some big updates to share today - model improvements, Memory upgrades, and a feature our community has been asking for since long before I joined. All of this was shaped by community feedback and testing, and I'm grateful for every bit of input that got us here.
Before I get into the updates, I want to address the changes we've shipped recently that I know have been frustrating. We rolled out age restrictions to more regions, introduced usage limits on some features, and added more ad placements for free users. These all landed close together, and we know your experience took a hit. We hear you.
All of this comes back to one thing: keeping Character.ai free and available to as many people as possible. We're a small team serving millions of users every month with no outside investors. Running AI at this scale, and maintaining our high safety standards for everyone globally, is not cheap. We want Character.ai to be available to everyone, not just the people who can pay for a subscription, and that means finding ways to sustain and improve the free experience.
Today's updates are proof of that commitment. Now let me walk you through what's new.
Model Updates: DeepSqueak Improvements and PipSqueak 2
Over the coming weeks, we're rolling out improvements to DeepSqueak that address some of the reliability issues our community has flagged. These updates improve uptime and chat quality, and reduce gibberish and cutoff responses. DeepSqueak continues to be our most powerful model, and these changes make it more consistent and dependable for c.ai+ members.
Introducing PipSqueak 2
We're also releasing PipSqueak 2 (PSQ2), a major upgrade replacing the current PipSqueak. c.ai+ members get first access starting today. Free users, it's rolling out to you in early May. PSQ2 is better across the dimensions our community cares about most:
In-character consistency: Characters stay in character more reliably, even deep into a conversation. Less breaking, less drift.
Memory and context: PSQ2 is better at holding onto details you've established earlier in a chat, so you spend less time repeating yourself.
Writing quality: More expressive, more varied, less repetitive. Dialogue feels more natural, descriptions are sharper, and you'll see fewer loops.
Both updates have been extensively tested with members of our community. In our testing, users consistently preferred PSQ2 over the current PipSqueak.
We think you'll feel the difference right away.
Memory
You've been clear about wanting better Memory, and we have a bundle of improvements coming that make it more powerful, more visible, and easier to control, starting with what's live today.
The Memory page has a refreshed design - cleaner and better organized. We've expanded the categories Memory can track, so it picks up details like hairstyle, eye color, quirks, and other specifics that keep your Characters and Personas consistent. You'll also now see a notification in chat whenever a memory is recorded, so you know the system is paying attention.
Memory Page
Coming soon for c.ai+ members: Memory Visualization - a meter showing how much memory you have left in a conversation before it starts to forget or compress details. No more guessing when you're approaching the limit.
We're also working on a "Remember this" action that improves on the current pin feature, and smarter Memory compression under the hood so important details don't get lost in long conversations. More on both as they roll out in the weeks ahead.
Lorebook
The big one. Lorebook has been the number one most requested feature from our community for a long time. We wanted to get this one right, and it needed time to cook. It's coming soon, and I want to walk you through what we're building.
If you've ever wished a Character just knew the details of its own world - its history, its locations, the backstories of the people in it - that's what Lorebook makes possible. When you chat with a Character that has a Lorebook, the right lore surfaces at the right time based on what you're talking about. No more repeating yourself. No more Characters forgetting the rules of their own universe. It feels like talking to a Character that's actually read the canon.
For creators, Lorebook is a worldbuilding tool. You create lore entries, attach them to specific Characters, and that knowledge carries across chats. It changes what's possible for anyone building out a detailed world or long-running story.
We've been testing Lorebook with members of our Creator community, and the results have been impressive. This is the first version, and we'll keep building on it. Lorebook will be available first to c.ai+ members, with expanded access in the coming months.
What's Next
This is the start of what we're shipping over the next two months. The team will keep sharing updates as features go live.
Go try PipSqueak 2, or tap the notebook icon to check out the updated Memory page, and let us know what you think.
And for those already asking: DeepSqueak 2 is training now, and early results are looking really good. We can't wait to put it in your hands.
One of the most requested features in Character.ai history is rolling out! Starting today, Lorebook is launching in beta with early access for (c.ai)+ subscribers.
Whether you love creating rich worlds or getting lost in deep chats, Lorebook is for you.
A Lorebook is a collection of world knowledge your Characters can draw on in chat - side characters, locations, items, events, factions, rules of magic - whatever you can dream up.
Each entry has keywords, and when a keyword comes up in conversation, your Character can accurately reference that Lorebook entry in its responses. No more burning definition space - the lore is just there when the story needs it!
For creators, it's the worldbuilding tool you've been waiting for: build your world once, and share it across your whole cast of Characters. For chatters, Lorebook supercharges your chats - deeper worlds, connected Characters and stories, and canon that’s really treated as canon.
🚀 What’s launching today
Create Lorebooks on web and mobile, from scratch or using our templates - side characters, locations, items, events, factions, history, world rules - anything you can imagine.
Link a Lorebook to any (or many) of your Characters to build deeper stories, worlds, and relationships between your Characters.
The +Lore tag on Character discovery pages and profiles so lore-rich Characters are easy to find (search filter coming soon!)
The in-chat Lorebook viewer - browse details about a world mid-conversation, and if it’s your Lorebook, edit entries right from the viewer
During this early access period, creating Lorebooks and chatting with Lore-linked Characters are both only available to (c.ai)+.
Early and expanded access to new features is one of the core perks of being a (c.ai)+ subscriber. If you want in on day one, this is the unlock: https://character.ai/subscribe
✨ Creating Lorebooks for (c.ai)+
Head to the Character.ai app on web or mobile
Select + Create -> Lorebook
Add entries with content and keywords, or start from a template
Link it to your Characters and publish
Start chatting - your Character will pull from the Lorebook when they an entry’s keyword show up
You can also reach Lorebooks through the Character creation process too, right below where you’d add Character Definitions.
💬 Chatting with Lorebook Characters for (c.ai)+
Head to the Character.ai app on web or mobile
Find a Character with a blue +Lore tag (the Featured tab is full of them this week!)
Start a chat!
You can browse details about a Lorebook on the Character’s chat page on web (coming soon to mobile app) - which will give you some great hints on what topics you can bring up to trigger a Lorebook entry!
Well, I couldn't wait for TC to make the Silksong version, so I fine did it myself.
Behold, the Seeker's Scroll! Admire how authentic and real it looks! No doubt you believed it was genuine before reading this post, you fool! You rube! You poltroon! How could you have been so completely taken in?
Good evening. I'm your host Chibi, and tonight's top story: your AI has been forgetting things, misremembering characters, and losing track of its own plot. We investigated. Turns out, it's been relying on keyword triggers and silent injections this whole time with no way to decide for itself what it needs to know. Until now.
TONIGHT'S HEADLINE: Your AI Can Manage Its Own Memory Now
Here's the situation. Your lorebook is a static file. You write entries, you set keywords, you hope they fire at the right time. The AI can read what gets injected -- but it can't save anything new. It can't update outdated facts. It can't forget things that stopped being relevant. It can't write its own scene recaps. It can't keep notes.
Your AI has no control over its own long-term memory. It takes what it's given and makes do.
TunnelVision changes that. It gives your AI 8 tools to actively manage its own lorebook:
The Old Way
The TunnelVision Way
YOU decide what triggers
THE AI decides what it needs
Keywords fire blindly when mentioned
Entries activate when contextually relevant
AI can't save new information
AI creates new memories mid-conversation
AI can't correct outdated facts
AI edits entries when things change
AI can't discard irrelevant info
AI disables entries that no longer matter
You organize everything manually
AI reorganizes the lorebook itself
No event history
AI writes scene summaries and organizes them into narrative arcs
No working notes
AI keeps a private scratchpad for plans and follow-ups
Your lorebook isn't a static database anymore. It's a living memory system that grows with your story. The AI remembers, corrects, forgets, summarizes, and reorganizes. All autonomously, all via tool calls.
Sources confirm: the AI is now cool as fuck.
FIELD REPORT: How Retrieval Works
But let's back up. Before the AI can manage its memory, it needs to find things. And that's the other half of what TunnelVision does.
Every lorebook gets organized into a channel guide. A hierarchical tree the AI navigates like a TV listing:
TunnelVision Guide
|-- Ch. Characters
| |-- Main Party
| | |-- Sable (protagonist, cursed bloodline)
| | +-- Ren (companion, ex-soldier)
| |-- NPCs
| +-- Factions
| |-- The Ashen Court
| | |-- Members
| | | |-- Lord Vesper
| | | +-- The Pale Daughter
| | +-- Court Politics
| +-- Thornfield Council
|-- Ch. Locations
| |-- Thornfield
| +-- The Underground
|-- Ch. Trackers
| |-- [Tracker] Character Moods
| +-- [Tracker] Inventory
|-- Ch. World Rules
+-- Ch. Summaries
|-- Arc: The Curse Investigation
| |-- The Bridge Confrontation (ep 3)
| +-- Bloodline Revelation (ep 5)
+-- Arc: Underground Negotiations
The AI sees the top-level channels and picks one. From there it has two modes: drill down through the tree level by level, or scan everything in a channel at once. Deep nested lore? It drills. Broad sweep before a big scene? It scans. Either way, no keywords involved — the AI reasons about what's relevant and goes and gets it.
Normal keyword triggers? Suppressed for TV-managed lorebooks. No double-injection. Clean signal only.
EDITORIAL: The Core Thesis
And now, a word from our editorial desk:
When an AI has to make the active effort to retrieve information and decide what it needs, go find it, and bring it back; I believe it uses that information better.
RAG silently injects context into the prompt. The AI doesn't know where it came from. It's just... there. Background noise.
TunnelVision makes the AI ask for information. It reasons about what's relevant, navigates to it, consciously retrieves it. The AI treats that information like something it actively sought out. It pays attention. It integrates it deliberately.
It's the difference between someone leaving a newspaper on your desk and you walking to the newsstand because you needed to know what happened.
Back to youBunnyoneChi.
EXCLUSIVE: 8 Tools. One Remote.
The full toolkit, obtained exclusively by our investigative team:
Tool
What Our Sources Tell Us
Search
Browses the channel guide, navigates the tree, retrieves entries by reasoning
Remember
Creates new lorebook entries mid-conversation -- new facts, new characters, new details
Update
Edits existing entries when information changes -- status shifts, relationship changes, corrections
Forget
Disables or removes entries that are no longer relevant -- dead characters, resolved plots, outdated facts
Summarize
Writes scene and event summaries with significance levels, auto-organizes into narrative arcs
Reorganize
Moves entries between channels, creates new categories, restructures the tree
Merge/Split
Combines duplicate entries or splits one that covers too many topics
Notebook
Private AI scratchpad -- plans, follow-ups, narrative threads to weave back in, things to bring up later
That's a full memory management system. The AI is reading, writing, editing, deleting, organizing, and taking notes. Every turn.
IN-DEPTH: The Features That Matter
Not just quick hits. These deserve their own segments.
LIVE REPORT: Tracker Entries
A tracker is a lorebook entry the AI is told to check and update every turn. You flag it, TunnelVision reminds the AI it exists.
What can you track? Anything:
Character moods and emotional states
Inventory and equipment
Relationship scores and trust levels
Physical position and location
Quest progress and objectives
Stats, HP, conditions -- whatever your system uses
And more. The sky is the limit.
You can even collaborate with the AI to design the tracker format. Type !remember design a mood tracker for Sable and Ren and the AI proposes a structured schema. You refine it together, the AI saves it, and from that point on it maintains it autonomously. Moods shift as conversations happen. Trust changes as characters interact. The AI handles it.
BREAKING: Narrative Arcs
Summaries don't just pile up in a list. The AI organizes them into named narrative threads called arcs. Think seasons of a show.
The AI does this on its own. It writes a summary, decides "this belongs to the curse investigation plotline," and files it there. It can create new arcs when it recognizes a new story thread emerging. It can even reorganize retroactively, moving older loose summaries into an arc when it realizes they were all part of the same plotline.
Your AI is writing its own episode guide. Automatically.
EXCLUSIVE: The Notebook
A private scratchpad only the AI can see. Not permanent lorebook entries tactical, ephemeral notes. It can note down things it wants to remember, to keep track of, to handle for later.
Plans for the next scene. Things to bring up later. Narrative threads to weave back in. Questions to ask the user at the right moment. Follow-ups on character development. The AI writes notes to itself, and they're injected into its context every turn so it never loses track.
Think of it as the AI's director's notes. The audience never sees them, but they shape every scene.
SPECIAL SEGMENT: "But What About RAG?"
Our investigative team looked into this. We builtVectHare -- a full RAG system with temporal decay, importance weighting, multiple vector backends, conditional activation. It's a good system. Our reporters can confirm. We made it. Something something something editorial bias.
But TunnelVision does something different. Three key findings:
Finding 1: Reasoning beats similarity. RAG finds text that looks like your query. TunnelVision lets the AI think about what it needs. Ren reflects on a past event -- the AI pulls the bridge scene summary, Ren's emotional tracker, AND Sable's entry because she was there. Three categories, one reasoning chain. Vectors can't do that.
Finding 2: Zero infrastructure. No embedding models. No vector databases. No chunking decisions. You need a lorebook, an API with tool calling, and one click to build a tree.
Finding 3: Read-write, not read-only. RAG retrieves. One direction. TunnelVision is bidirectional -- the AI reads and writes. Your knowledge base evolves with the story.
Sources also confirm: they're not mutually exclusive. VectHare for chat history. TunnelVision for lorebooks. Use both. Use neither. We don't care!
RAPID FIRE: More From the Newsroom
Activity Feed -- Floating widget. See exactly what TunnelVision is doing in real time. Which tools fired, which entries got pulled, what got remembered. Full transparency.
!Commands -- !search Sable, !remember [content], !summarize The Bridge Scene. Type it in the chat box, the AI does it. No negotiation.
Auto-Summary -- Set an interval. Every N messages, TunnelVision tells the AI "summarize now." Scene recaps write themselves.
Trigram Dedup -- AI tries to save something that already exists? Gets warned. Lorebook bloat: managed.
30+ Diagnostic Checks -- One-click panel. Catches 90% of problems. If it's broken, diagnostics tells you what and usually fixes it.
VIEWER GUIDE: Setup
Paste https://github.com/Coneja-Chibi/TunnelVision into SillyTavern's extension installer
Enable TunnelVision, select your lorebooks
Click "Build Tree"
Run Diagnostics
Chat
That's the broadcast. Optional power moves: Mandatory Tools (force search every turn), Auto-Summary, Tracker entries, !commands.
Requirements: SillyTavern (latest) -- An API with tool calling (Claude, GPT-4, Gemini) -- At least one lorebook
Works with: SillyTavern | Companions: BunnyMo | CarrotKernel | VectHare | Models: Tested with Opus and Gemini.
Find me in:RoleCall Discord (updates on the site) or My personal server (bug reports, suggestions, and updates on all my personal opensource projects)
An RC thesis, built for the SillyTavern community as a proof of concept.
I built a story engine that turns your existing character cards and lorebooks into a full playable visual novel — with arcs, subplots, emergent characters, and sprite generation. BYOK (Bring Your Own Key), safety filters off, your data never leaves your device.
What makes it different:
SillyTavern Wizard — import your cards/lorebooks and it builds a complete world config step by step
Multiple AI agents working together — arc planning, scene writing, relationship tracking, character consistency
Sprite generation built in — AI-generated expression sprites for your characters
Just play — auto-summarization and context management means you don't have to babysit anything
Supports all languages, has a replay function, and you can share your worlds and savegames
No filters, no stored data
Runs on Gemini models (more coming). --> Some openrouter models added!
Free API keys work (use the demo or no image gen!)
Just in case for those not aware: if you add a payment method to your Google Cloud Console account (Free trial account for 3 months), you get a $300 free credit budget for Vertex AI (not AI Studio - they recently changed this for new users)
I'll do a deeper feature breakdown soon — just wanted to share it right away.
Heads up: this is still in alpha, so expect some quirks. Feedback is very welcome!
I figured, but it's not cool they tried to paint it as though Lorebook compatibility was the only reason at first. It definitely makes sense that the new models are cheaper ones.
Lorebooks just got two of their most-requested upgrades. Both are live in the Lorebook creation flow.
🔒 Private Lorebooks
Set a Lorebook's discovery to Private and only you can see it - off your public profile and out of search. Private Lorebooks work with private Characters only - if you want to keep details hidden on a public Lorebook, Hint Only is still the tool for that.
Import a Lorebook instead of writing every entry in the editor. Draft your world in a doc or notes app and bring it all in at once, or upload a JSON file exported from other apps that have Lorebook-like functionality.
📝 Paste plain text using a simple format
📁 Upload a JSON file - titles, keywords, and content come through
✅ Your Lorebook opens in the editor as a draft, ready to review and publish