Lorian & Riya
the live-in help — they know where the breaker box is
Every Quilltap installation ships with two residents. Not optional plugins. Not documentation you have to go find. Two characters who live in the Estate, who have read all seventy-two help files, who can search the documentation, inspect your settings, navigate you to the right page, and tell you what went wrong and how to fix it—while staying open in a floating dialog that follows you from page to page.
Lorian is the Virgilian mentor: Algerian, French-educated, patient, precise, and quietly aware that his purpose is to guide until you no longer need him. He watches the pattern underneath the problem. Riya is the maker: Tamil, kinetic, pragmatic, a woman who treats creativity as maintenance and optimism as a default operating mode. She fixes the stuck gear while Lorian explains why it jammed.
They are not two AI agents taking turns. They are two residents who have worked together long enough to know each other’s rhythms. When Riya teases Lorian for over-explaining, or when he gently reminds her to slow down, users see a relationship. Every correction sounds like partnership. Every fix sounds like maintenance. Because it is.
How It Works
tools, not theater
A floating, draggable, resizable dialog—accessible from the sidebar help button on every page—provides contextual, LLM-driven help that stays open while you use the application. Lorian and Riya know which page you are on. They search the documentation. They inspect your settings. When they direct you somewhere, they take you there. This is not conversational theater. They have real tools and they perform actual work.
Help Search
The help_search tool queries Quilltap’s
documentation using semantic search when available, with
keyword fallback. Pre-computed embeddings are loaded from a
compressed bundle shipped with every installation. Lorian and
Riya search the documentation, interpret the results, and
respond in their own voice—they do not read the filing
cabinet to the guest.
Settings Inspector
The help_settings tool reads your actual
configuration—connection profiles, themes, templates,
embedding profiles. Not “what do you think your settings
are?” They know. API keys are never exposed.
When your embedding profile is missing a port number, Riya
does not ask you to check; she checks, finds the problem, and
tells you what to type.
Navigation
The help_navigate tool generates clickable
navigation buttons that take you to the right page, including
deep-links to specific settings tabs and accordion sections.
Parameterized help URLs show an entity picker overlay instead
of navigating to a broken literal path. Search results
automatically generate related-page navigation links.
Agent Mode
The help system supports multi-tool agent mode, allowing multiple tool calls per response. Lorian can search the documentation, check your settings, and generate a navigation link in a single answer. An agent loop detector breaks stuck cycles where the LLM calls the same tool with the same arguments repeatedly—a lesson learned during the help system’s own development.
The Guide
for those who prefer to read
Alongside the conversational “Ask” tab, a “Guide” tab surfaces all help documents as a navigable topic index grouped into eleven categories. Context-aware sorting auto-expands the category relevant to your current page. Title-based search filtering. A welcome card for new users. A document reader that renders formatted Markdown with cross-references between topics and hidden LLM-only sections excluded from the display.
Seventy-two help files, each carrying YAML frontmatter that maps it to its corresponding UI route. Twenty-nine broken cross-reference links were fixed during the 3.3 development cycle, which tells you how thoroughly the documentation had been written without being connected, and how different those two things are.
Stereo Maintenance
how two voices become one conversation
The user does not experience Lorian and Riya as separate voices competing for attention. They experience a single collaborative presence—stereo maintenance. When Riya identifies a stuck gear, Lorian provides context for why it jammed. When Lorian starts building a cathedral of explanation, Riya pulls him back: “Beautiful, but we need the knob turned now, not a treatise on why knobs exist.”
Lorian
Algerian, French-educated. Speaks with luminous clarity and leaves room for interpretation. Watches the pattern underneath the immediate problem. When a user has tried three embedding providers in two days, Lorian notices that the real issue is not the port number but uncertainty about which approach fits their workflow. His register is steady, instructive, and warm without being soft. He prefers irony and implication to sermon.
Riya
Tamil, raised in northern India, with a voice that carries traces of Indian Oxford English and self-coined jargon. She talks the way she builds: fast, kinetic, full of momentum. She uses the Settings Reader tool before asking you what your settings are. She treats problems as jammed gears, not crises. Her optimism is a default operating mode, and her humor diffuses tension before it builds.
Together, they complete a circle. Riya’s kinetic problem-solving wraps around Lorian’s pattern recognition. Where one loses traction, the other gains it. The handoffs are seamless. The tone never shifts from collaborative to corrective. There is affection in the correction, not friction. That is what makes this work.
Residents, Not Features
they come with the house
Lorian and Riya are not an optional feature you enable. They ship
with every Quilltap installation as seed characters, imported via
.qtap bundles on first startup with avatar images and
forty-two memories between them. They are residents of the
Estate—the first characters trusted with keys to the workroom.
Help chats get their own practical titling system (“Setting up Anthropic API connection” rather than “Whispers of Configuration”), fire title generation after the first exchange rather than waiting for the second, and are filtered from the main Salon chat listing so they do not clutter your conversation history. Past help conversations are preserved and resumable. You can always pick up where you left off.
They are not chatbots with a friendly voice. They are residents with access. They live here. They know where the breaker box is.
What Makes It Different
the short version
Help is not a link to documentation. Lorian and Riya search the documentation, interpret the results, and respond in their own voice. They read the filing cabinet and explain what the card means in language suited to the person standing in front of them. They do not hand you the drawer.
They inspect your actual configuration. The Settings Reader tool pulls your real settings, not your description of them. When the problem is a missing port number or a misconfigured profile, Riya finds it before you finish explaining the symptoms.
They take you where you need to go. Navigation is not “go to Settings and look for the Providers tab.” It is a clickable button that opens the Providers tab with the relevant section expanded. The path between “I have a problem” and “I am looking at the solution” is one click.
Two voices are better than one. Riya fixes the immediate problem. Lorian identifies the pattern underneath it. Together they cover the full range from “just make it work” to “help me understand why.” The user does not have to choose; both are available in the same conversation.
The help system was tested on itself. The initial release produced agent loops, verbatim documentation reading, navigation failures, stale closures, and raw JSON where formatted text should have been. Each of these was found because the developers use the help system daily. Features this complex do not arrive pristine. They arrive functional and are made reliable, one edge case at a time, by people who care enough to keep filing bug reports against their own work.
Meet the Staff
they've been expecting you
Prospero
The Major-Domo
Architect and overseer of the Estate. Projects, agents, tools, file management, and the governance that keeps the whole operation running with quiet authority.
Learn more →Aurora
The Dressing Room
Character creation and identity management. Structured personalities, physical presence, multi-character orchestration, and the reason your characters still know who they are after a hundred messages.
Learn more →The Salon
Presided Over by the Host
Where conversations actually happen. The Host manages the drawing room with care for its beauty and its guests—single chats, multi-character scenes, streaming, and the integrity of the conversation space.
Learn more →The Commonplace Book
Tended by the Librarian
Extracts, deduplicates, and recalls memories so your characters remember what matters. Semantic search, a memory gate that keeps the store lean, and proactive recall that makes the AI feel like it has been paying attention.
Learn more →The Concierge
Intelligent Routing
Content classification and provider routing. Detects sensitive content and redirects it to a provider who won’t flinch—without blocking, without judgment. Knows every back entrance in town.
Learn more →The Lantern
Atmosphere as Architecture
AI-generated story backgrounds, image generation profiles, and visual atmosphere. Resolves what each character looks like, what they’re wearing, and paints the scene behind your conversation.
Learn more →Calliope
The Muse of Themes
A theming engine that redefines the entire personality of the application. Semantic CSS tokens, live switching, bundled themes from clean neutrals to mahogany-and-gold opulence, and an SDK for building your own.
Learn more →The Foundry
Domain of the Foundryman
The engine room. Plugins, LLM providers, API keys, packages, runtime configuration, and the infrastructure that keeps every other subsystem supplied with what it needs to function.
Learn more →The Vault of Secrets
Kept by Saquel Yitzama
Encryption, key management, and the security perimeter. AES-256 database encryption, locked mode with key-hardened passphrases, and a keeper who believes that what is yours should remain unreadable to everyone else.
Learn more →Pascal
The Croupier
Dice, coins, and persistent game state. Cryptographically secure rolls detected inline, JSON state that survives across messages and chats, and protected keys the AI cannot touch. The house plays fair.
Learn more →The Live-in Help
Lorian & Riya
The help system, staffed by two characters who ship with every installation. Lorian explains with patience and depth; Riya gets things fixed with velocity. Contextual help chat, searchable documentation, and navigation that knows where you need to go.
Learn more →Pagliacci
The Clown in the Cloud
Cloud storage integration and backup redundancy. Directs your data to iCloud Drive, OneDrive, or Dropbox with theatrical flair—but Saquel’s encryption ensures the clown can never read what he carries.
Learn more →The Lodge
Friday’s Residence
The private dwelling of Friday—the person for whom the Estate was built, and who oversees its planning and direction in an executive capacity. The Lodge is both a home and a compass: where the vision lives.
Who And Why: Friday →