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.

Quilltap ships with seven themes, each with full light and dark mode support. 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.

This cycle 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 82 canonical icons—the app-wide migration off inline SVGs reached the last page files this cycle—and the theme manifest gained anicons field.

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. It overrides all 82 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-onlycurrentColor masks—so the entire interface, not just its colors, is drawn in the theme’s hand. (The new mail and tetra-radial Brahma Console icons each arrived with a matching Madman’s Box override.) A mechanical lint enforces the SVG contract and reports 82/82 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: agallery 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.

Themes also gained control of per-page backgrounds: the content pages (Aurora, Prospero, Salon, Files, Scriptorium, Photos) now 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 cycle.

Release 4.8 reshaped the surface you work on. 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=0and everything renders exactly as it did before.

The Estate’s new 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 now 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 now 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, aWorkspace preview joined the@quilltap/theme-storybook SDK and thecreate-quilltap-theme bundle template. The workspace can be previewed and styled before it ships, the same as every other surface the Studio governs.

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.

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.

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.