When the Estate was younger, we needed someone to mind the difficult door—the one through which certain categories of conversation must pass. We hired Dangermouse. He was a content classifier of the old school: suspicious of everything, possessed of an internal list of anxieties that grew longer by the week, and capable of exactly two responses—yes and no—with a marked preference for the second.

The trouble was that Dangermouse did not understand the difference between dangerous and delicate. A guest writing a war novel does not require a censor; they require a librarian who knows where the military history section is. A guest composing a difficult scene between estranged lovers does not need to be told that the Estate disapproves of raised voices. They need someone who understands that fiction is not autobiography, and that the writer’s intent is not the character’s crime.

The final straw involved a clergyman working on a theological monograph. He attempted to discuss a passage from the Song of Solomon in the context of ancient Near Eastern poetry, and Dangermouse flagged the entire conversation, reclassified the chat, applied a warning badge, and very nearly rerouted the good reverend to an entirely inappropriate alternative provider. The Foundryman’s language, when informed of this, could itself have been flagged.

Dangermouse collected his briefcase—the one full of flags and categories and anxiety—and walked out through the front gate without a word. He did not ask for a reference. The Concierge watched him go from the front desk, adjusted his pocket square, and turned to the next guest in the queue.

The Concierge operates according to your preference. There is no default assumption about what you should or should not discuss with your AI. There is only the question of how much help you want navigating the providers.

Content classification operates at two levels: individual messages and entire chats. Message classification happens in real time as you converse. Chat-level classification uses the context summary—the Concierge’s view of what a conversation is about—to make a holistic assessment. Once a chat is classified as sensitive, the designation is sticky; it does not flicker back and forth as the conversation moves between topics.

Context summaries regenerate on the same schedule as chat titles and story background checks—at interchange checkpoints 2, 3, 5, 7, 10, and every 10 thereafter—so the Concierge’s view of a conversation stays current rather than frozen at the moment the first summary was written. Chats already classified as permanently sensitive skip redundant per-message classification, saving tokens on every exchange.

The most insidious form of content refusal is not an error message. It is silence. A provider receives a request, decides it does not approve, and returns—nothing. No error code, no explanation, no apology. Just an empty response and a user left staring at a blank space where an answer should be.

The Concierge catches these. When content has passed moderation and the provider returns an empty response, the system retries the same provider first—it may be a transient issue—then fails over to an uncensored provider if the silence persists. Distinct toast messages tell you which scenario occurred. This applies everywhere: chat streaming, memory extraction, context compression, title generation, story background prompts, appearance resolution, and scene state tracking. Every background task that touches a provider has the same safety net.

The principle is simple: your request deserves an answer, and it is the Concierge’s job to find someone willing to give one.

Connection profiles and image profiles both carry an “Uncensored-Compatible” checkbox. When Auto-Route is active, the Concierge resolves uncensored-compatible profiles for flagged content, selecting the best available provider for the task at hand. If the user has deliberately chosen an uncensored provider for a character, the Concierge does not force a swap—routing uncensored-to-uncensored serves no purpose.

All cheap LLM background tasks—memory extraction, title generation, context summaries, scene state tracking, story backgrounds—use uncensored providers for chats classified as sensitive. This prevents the quiet failures that previously occurred when background tasks hit content refusals from providers that were never designed to handle the material. The Concierge does not merely route your conversations; he routes the work that supports them.

Image generation receives the same treatment. When a user’s image prompt or its expanded version is classified as sensitive, the Concierge reroutes the generation request to an uncensored image provider. The Lantern paints the scene; the Concierge ensures the paint reaches the canvas.

A toggle in the sidebar sweeps all flagged content out of view—across the homepage, character conversations, project chats, and the sidebar itself. Danger indicators (colored asterisks) appear on all chat listings so you know at a glance which conversations carry classifications. Toggle it back and everything reappears. The feature is about context, not shame: there are moments when a screen is visible to others and sensitive chat titles should not be.

Content display within classified chats offers three modes: show, blur, or collapse. Flagged messages carry category badges and a rerouted indicator when Auto-Route has redirected them, with an override button for cases where the classification is wrong. Content hash caching deduplicates classification calls so the same message is not re-evaluated unnecessarily.