At heart the Console is a capable, concise, neutral assistant—a general-purpose chat with whichever model you point it at. It persists, lists your past conversations, and lets you resume any of them exactly where you left off. Every message in the transcript, yours and the engine’s alike, wears a small copy mark that tucks its original Markdown onto your clipboard.

The Console keeps the same body whichever way you summon it. Opened as a tab in the two-pane workspace, it reuses the very dialog the floating window uses rather than duplicating a line of logic—so the tab and the window are not two consoles that resemble one another but literally the same console, docked instead of hovering. Close the tab and the mode turns off with it; close the floating window and nothing is lost that was not already lost.

Beyond plain conversation, the Console carries a deliberately small set of tools. It can search across your past conversations and every document store, including their knowledge folders. It has full reach into your document stores—reading, listing, grepping, and writing files. And when the connection profile permits, it can search the web; with the curl plugin installed, it can fetch URLs directly. A thorny question is rarely settled in a single stroke, so the Console works one the way any diligent clerk would—a query here, a document read there, each step a turn at the telegraph key—taking as many turns as the matter demands, up to a ceiling you set yourself.

That ceiling was for some while a hardcoded twenty-five, which a deep search through the ledgers could exhaust in the middle of an investigation. It is now yours to set: Settings → Chat → Brahma Console carries a field reading “Let the Console take up to N turns”—anywhere from five to two hundred, and fifty by default. Raise it when you find the Console repeatedly running out of rope halfway down a ledger; lower it if you would rather it answered briskly from whatever lies near to hand. The same figure governs the Console summoned from the sidebar and the @Brahma line called from the Salon floor alike.

And exhausting the budget no longer ends in silence. A run whose final turn was spent on yet another tool call used to save nothing whatsoever and leave the client waiting on an answer that was never coming—after an expensive investigation, which is the galling part of it. The Console now salvages what it did find and says plainly that it reached its budget. The separate guard against a model asking the same question over and over is unchanged, so a genuine loop still stops early however generous the rope.

Behind every character, conversation, memory, document, and tallied expense there are three great ledgers—Quilltap’s databases—and the Console may read them directly. Ask it a question in the plain language of your world—“how lopsided is this character’s sense of importance?”, “which engine has cost me the most this fortnight?”, “how many conversations mention the airship?”—and it quietly translates the question into a query, consults the right ledger, and answers you in your own terms. You need never see a line of SQL unless you ask to.

And the working is laid bare when curiosity strikes. Each query slips two panels into the transcript—a Query panel with the exact SQL, syntax-highlighted and copyable, and a Result panel laying the answer out as a proper table. Should a query go awry, the Result panel reports the ledger’s own complaint in plain words rather than a polite shrug, and the Console takes the rebuff as a cue to inspect the schema and try again rather than guess twice.

For the keeper who would rather read a standing account than compose a question, the Console has a companion instrument: the Almanack, rebuilt this cycle and at last taught to read the whole house. Stores by kind, blobs by type, hard-link groups and the deduplication they buy, character-vault health, wardrobe by tier, the Post Office, the state cascade, Pascal’s Workbench inventory including the definitions that failed to parse, a dramatis personae, and wire records with per-profile latency and prompt-cache hits—including the lifetime token figures that had read a serene and entirely fictitious zero since the beginning. It lives with the rest of the machinery, in the Foundry.

The Console need not be summoned from the sidebar to be of use. From inside any Salon conversation it answers to the name Brahma, reached through the same reference-desk machinery as any Carina answerer—type @Brahma: for a public reply or @Brahma? for a whispered one, or let a tool-using character consult it via ask_carina. The answer drops straight into the scene as a tidy reference card.

Reached this way Brahma is a pseudocharacter, not a character: no row in the cast, no participant, no memories formed. It keeps all of its console powers—read-only ledger inspection, document-store access—but loses every scrap of continuity, each query wholly standalone. Because those powers are not handed about lightly, the Salon line opens only for you (the proprietor), for your own user-controlled persona, and for characters you have granted system transparency; to anyone else, Brahma simply does not answer. A real character named “Brahma” always wins the name. The turn budget above governs an answer given this way exactly as it governs one given at the sidebar; it is the same clerk at the same key.

An answer dropped into a scene this way is part of the scene, and travels with it: Brahma’s Salon replies are carried into a conversation’s Export Markdown transcript under his own name, alongside Carina’s.