A theme, in most applications, changes a few colors and calls it a day. In Quilltap, a theme can redefine the entire personality of the application.

Quilltap’s theming system is built on a layer of semantic CSS variables—the qt-* utility classes—that map to every UI surface: cards, panels, buttons, chat bubbles, sidebars, message styling, typography, form inputs, status badges, and alert states. A theme overrides these tokens and can embed its own fonts, CSS, background images, and visual personality. Switching themes happens live, instantly, with no page reload. The entire application redraws itself around you like a room being redecorated while you sit in the chair.

Themes can also override subsystem names and navigation card descriptions. The room called “The Foundry” in one theme becomes “Settings” in another and “The Machinist’s Floor” in a third. The characters who personify each subsystem adjust their presence to match the current theme’s register. The Estate speaks in its own voice, whatever voice you choose.

Release 4.8 reshaped the surface all of that dressing hangs upon. The Estate is now a two-pane workspace of kept-alive tabs, and it is the room you land in after you sign in. Picture a writing desk with two working surfaces side by side and a row of tabs along the top: conversations, documents, terminals, the Brahma Console, the Wardrobe—all open at once, all a click apart, the whole application rearranged around how you actually move through it rather than a stack of separate pages you navigate between.

Open as many tabs as you like across the two panes. Drag a tab to the center of a pane to split the view and set two things side by side—a conversation and the document it is about, a chat and its terminal, two conversations watching each other—and drag the divider to decide how much room each is given.

The important part is what does not happen when you switch tabs. A streaming conversation keeps streaming while you look at something else—an inactive tab is hidden, never unmounted, so the tokens keep arriving and the scene is exactly where you left it when you return. Split a pane mid-response and the response survives the split. Keyboard shortcuts live under Ctrl/Cmd+Alt for moving between tabs, jumping to the nth, closing one, or toggling the split. And if you would rather have the old per-page routes back, set NEXT_PUBLIC_WORKSPACE_TABS=0 and everything renders exactly as it did before.

The backdrop, meanwhile, is now arbitrated rather than left to each surface to settle for itself. A conversation carrying a story background wins the argument outright and fills the screen with it. With the panes unsplit, the single active tab’s background is what you see; split them, and each pane’s background dominates its own side, the two crossfading across the divider. The per-view ::before layers that used to paint each page’s own image are suppressed inside the workspace precisely so that this one arbitrated backdrop can be trusted—one image, one decision, no argument between two rooms about whose wallpaper the guest is looking at.

All that furniture now keeps the same time, which it had not been doing. Every relative timestamp on screen—“4m ago,” “Today,” a budget counting itself down—ran an interval of its own, started at whatever moment its component happened to mount, so they drifted apart and turned over one at a time like a badly wound orchestra. There is now one shared ticker per granularity, aligned to the boundary rather than to the mount: it fires just after each minute, each second, and each local midnight, so every “4m ago” in the house becomes “5m ago” together, and a chat card rolls from Today to Yesterday at midnight rather than whenever it happens to feel like it. It stops entirely while the tab is hidden, on the sound principle that nobody is watching.

Keeping time is one thing; having something worth telling the time about is another. The date on that chat card was made honest in the same release, and now names the last time somebody actually spoke in the conversation rather than the last time anything whatsoever about it changed—a backdrop finishing, a summary folding—which is set out at length under the Salon.

The Estate’s two-pane workspace—its strip of kept-alive tabs, the divider between the panes, the drop-zone that blooms when you drag a tab to split the view—is Calliope’s to color like everything else. Every accented workspace surface derives from a single master token, --qt-workspace-accent, which falls back to --color-primary when a theme says nothing of its own. Each bundled theme sets that one token to its signature hue—so the active tab, the pane divider, and the split drop-zone glow in the theme’s own voice rather than a borrowed default.

And because a theme author should never have to guess, a Workspace preview joined the @quilltap/theme-storybook SDK and the create-quilltap-theme bundle template. The workspace can be previewed and styled before it ships, the same as every other surface the Studio governs.

Quilltap ships with six bundled themes alongside the built-in default. Most dress for both light and dark; Madman’s Box is the sole holdout, declining daylight altogether and declaring as much in its manifest so the mode toggle does not offer a mode it does not keep. The theme selector shows each theme’s name in its own heading font, with rich previews—now opening as a full-page contact sheet—that show actual UI elements, the theme’s bundled imagery, and (for a theme like Madman’s Box) its entire redrawn iconography.

In 4.7 a theme stopped being merely a palette and a set of fonts: it can now redraw the application’s entire iconography. Every glyph in Quilltap routes through a single <Icon> component backed by a registry of 85 canonical icons—the app-wide migration off inline SVGs reached the last page files in that same cycle—and the theme manifest gained an icons field. The registry has grown since: 4.8 admitted the thinking glyph as entry number eighty-five, the little quill that rocks while a reply is on its way having spent its whole career outside the catalogue.

A theme supplies either an .svg (masked and tinted by the UI’s currentColor, like every other icon, including the brand mark) or a full-color .webp, and the live theme switch picks it up. Icon-override URLs are version-stamped, so re-releasing a theme with a changed glyph can never leave a browser stuck on the stale one.

Madman’s Box is the proof of the idea. At version 1.1.7 it overrides all 85 canonical icons with original SVGs in its own design language—circular glyphs evoking the script of some ancient time-traveling, spacefaring species, with sharp butt caps, miter joins, disciplined stroke weights, and geometry-only currentColor masks—so the entire interface, not just its colors, is drawn in the theme’s hand. (The mail and tetra-radial Brahma Console icons each arrived with a matching Madman’s Box override; the newer thinking glyph did too, mapped to the theme’s own brand mark and set turning slowly through a full revolution every six seconds.) A mechanical lint enforces the SVG contract and reports 85/85 coverage, contract clean.

The inline “expanded card” preview in Settings → Appearance became a full-page modal with a Light/Dark toggle that drives both the banner and a live element preview. For a theme like Madman’s Box, the modal now shows two contact sheets: a gallery of the theme’s bundled images, and an icon sheet rendering each overridden icon in four states—default, muted, hover, and on-primary—inside a theme-scoped container so the bundled override CSS and color tokens are actually in effect. You can see the whole redrawn iconography and image set at a glance before you commit.

The banner is not merely a showroom window. From it you may Apply the theme outright, Export it as a .qtap-theme bundle, or—for a bundle theme not presently being worn—Uninstall it. Close the window by the ×, the Escape key, or a click upon the surrounding gloom; nothing is committed until you press Apply.

Themes also gained control of per-page backgrounds: the content pages (Aurora, Prospero, Salon, Files, Scriptorium, Photos) resolve their subsystem background image through the manifest, the same mechanism Settings already used, and a theme can suppress a page’s background entirely by setting it to "none". Madman’s Box wires all eight subsystem background textures and picked up refreshed Settings backgrounds late in the 4.7 cycle. Note, though, that 4.8 changed where those backgrounds actually hang: inside the tabbed workspace the per-view background layer is suppressed in favour of the single arbitrated backdrop described under The Tabbed Workspace, and of the six content pages only the Salon still paints within it. The full per-page arrangement—Settings tabs included—is what you see on the legacy standalone routes, under NEXT_PUBLIC_WORKSPACE_TABS=0.

The little quill that rocks back and forth while a reply is on its way has been rebuilt as a proper themeable icon, which—to its lasting embarrassment—it never was. A theme may now swap the glyph, retune its motion, or replace the animation outright. In passing it acquired three graces it had been getting along without: it takes the colour of the text around it rather than sitting in one fixed livery; it pivots on its nib, so the feather swings above a still point instead of wobbling about its own middle like a top losing its nerve; and it holds its peace for anyone who has asked their system to reduce motion. Madman’s Box, ever the first to accept an invitation, sets its own quill turning slowly through a full revolution.

Madman’s Box also stopped shouting. Its headings now render in true small capitals rather than flattening every name into a telegram—“Charles Sebold” is once again distinguishable from “CHARLES SEBOLD”—and its buttons, which had been uppercasing exactly those few labels that happened to sit on real <button> elements while leaving their neighbours alone, now agree with one another and render their labels as written.

And the whispers can be read. The “whispered to X” label, at three-quarters of a rem, had been failing WCAG AA against its own bubble in light mode in every bundled theme but one—and in the default theme besides. Art Deco measured 1.07:1, which is a polite way of saying invisible. Each theme’s label was darkened within its own palette; Art Deco’s whisper bubble was lightened as well (its muted sits so dim for a light theme that no violet in the palette could clear the bar on its own); and three dark-mode values were corrected on the way past. All six bundled themes and the default now clear 4.5:1 on both the label and the announcement chip’s audience tag, in both modes—twenty-six measurements, the lowest a comfortable 4.65.

Calliope does not guard the studio door. Theme creation is supported through two paths, both designed so that you never need access to Quilltap’s source code—and a third that the Studio would rather you did not take.

The third path is the one the Studio is politely showing the door. Themes were historically distributed as npm packages, and that format is now deprecated: existing plugin themes go on working and are labelled with a “(deprecated)” badge in the theme selector, but nothing new should be built that way. npx create-quilltap-theme my-theme scaffolds a bundle; the legacy format now requires you to ask for it by name with --plugin, which is roughly the amount of ceremony Calliope thinks it deserves.

A registry system with Ed25519 signature verification lets you browse, search, and install themes from remote sources. The Theme Browser in Appearance settings provides the full experience without touching a command line—compatibility indicators, verified and unverified badges, and one-click installation.

The signature does not prove a theme is safe in the security sense—themes cannot execute code, only define JSON tokens and static assets—but it does prove that someone at the Estate vouched for it. Registry sources can be added and removed. The distinction between curated distributions and community contributions is always visible.

Everything the Theme Browser does, the command line does too, for those who prefer their errands typed. quilltap themes registry list, add, remove, and refresh manage the sources—an add may carry --key ed25519:BASE64KEY so the registry’s signatures are checked against a key you nominated yourself—while themes search looks across every configured registry at once and themes update asks whether anything you have installed has been improved upon since. Registry indexes are plain JSON: each theme listed with a download URL, a SHA-256 hash, and an optional Ed25519 signature.

Should you wish to keep a registry of your own—a studio’s house collection, or a shelf shared among colleagues—the same CLI holds the signing tools: registry keygen mints an Ed25519 keypair and registry sign puts your name to a directory of themes. Calliope approves of anyone willing to vouch for their own work in writing.

Themes are Calliope’s most visible work, but the Studio governs the entire user experience. Every layout decision, every interaction pattern, every piece of visual feedback passes through the same aesthetic judgment.

Underneath every theme is the qt-* utility class system—a comprehensive layer of CSS variables that maps to every visual surface in the application. This is what makes Quilltap’s theming possible without the theme author needing to know the component structure, and what makes theme switching instant without a page reload.

The system covers backgrounds (qt-bg-surface, qt-bg-card, qt-bg-muted, qt-bg-default), borders (qt-border, qt-border-primary), text (qt-text-secondary, qt-text-warning), buttons, alerts, entity badges, status badges, plugin source badges, form inputs, filter chips, file previews, chat messages, sidebar elements, wardrobe action notices, memory whispers, and more. The 2.x and 3.x cycles ported the bulk of the application from raw Tailwind color classes to these semantic tokens; 4.0 swept up the stragglers, converting 1,314 hard-coded visual classes across 234 files in a single cycle. The result is the same in both directions: a single theme override changes the application consistently, leaving no orphaned colors behind.

The @quilltap/theme-storybook package reached comprehensive coverage of all qt-* classes during the 3.3 cycle, with 4.0 normalizing the bundled themes (the redundant declarations stripped out, file sizes shaved by 6–34%, --qt-* defaults now properly scoped to every theme) and 4.2 extending coverage with the wardrobe and whisper tokens that accompanied the new clothing and memory surfaces. If you are building a theme, every variable you might want to override is documented, previewable, and testable before you ship.