Omniscio

Visual Themes (15 bundled skins + custom themes)

Omniscio ships fifteen bundled visual skins and lets you make your own in the Theme Studio — pick colours, watch the whole app change as you go, save, edit later and export to share — or import a theme file someone sent you. Picking any theme recolours every component instantly.

On this page

What it is

Omniscio ships with 15 bundled skins and supports importing your own .theme.json files. Themes are CSS-variable driven — picking a skin updates a small set of custom properties (--accent-rgb, --panel-bg, --panel-border, --color-surface-*, --accent-glow, etc.) and every component in the app recolors automatically. That means you never have to touch code to reskin the app, and theme authors never have to maintain a fork. Bundled options range from clean corporate (Linear, Vercel Clean, Minimal Luxury) to atmospheric (Aurora, Gradient, Neon Accent, Frosted Tiers) to glassy/textured (Glassmorphism, Liquid Glass, Neumorphic, Soft Depth, Warm Charcoal, Spotify, Aurora Glass) to native (macOS). macOS is the newest — Mac greys and system blue, and on a Mac the desktop shows through the sidebars and title bar (see The macOS theme below).

The atmospheric skins (Glassmorphism and Aurora) paint two soft blurred colour blobs behind the whole app. Those blobs are sized off the longer edge of the window, so they cover a monitor rotated to portrait as generously as a wide landscape one — on a tall screen, sizing them off width alone left two small dots in opposite corners with a flat dead band between. On any landscape window the sizing is mathematically identical to what it has always been, so nothing changes there. The blobs are static (they don't drift) — an animated blur re-rasterizes every frame and was a measured cause of typing lag — and Low Power Mode drops the blur entirely.

Where to find it

Settings → Appearance holds the Visual Theme grid of fifteen cards and the Custom Themes grid beneath it, with Create Theme (opens the Theme Studio), Import and Open themes folder buttons on the custom side. While one of your custom themes is selected, Edit Theme and Export Theme appear beside them. The full authoring reference sits one click further along, behind Custom Theme Guide in the same pane.

How it behaves

How to use it

  1. Pick a bundled skin. Settings → Appearance → the Visual Theme grid shows 15 cards, each with a small preview of base, panel, accent, and text colors. Click one — the app recolors instantly without a reload.
  2. Import a custom theme. Same pane, Custom Themes grid below. Click Import → file picker filtered to .json → select a .theme.json file. The schema is validated; invalid files get a clear error (bad field names, missing required keys). Valid imports land in {userData}/themes/{id}.theme.json and appear as a new card in the custom grid.
  3. Build your own in the Theme Studio. Click Create Theme. The Studio opens with a copy of the look currently on screen — both its dark and light versions — so you start from something readable, never a blank app. Change the accent colour, the background tone (recolours every background and text shade, plus panels and cards, while keeping how light or dark each one is), the six status colours (running, needs you, error, question, approval, waiting), the text and code fonts (from a fixed list), and the corners (Sharp, Standard or Round — today this reaches cards and panels). Show every colour lists every colour a theme can set. Switch the Dark / Light tabs to edit each version. Every change shows across the whole app immediately; nothing is written until you press Save theme (or Ctrl+S), and closing the Studio any other way puts your previous look back exactly. If a colour makes text or the accent hard to see, the Studio warns you — it never blocks you. Saving switches you to the new theme; saving under a name that already exists asks before replacing it.
  4. Edit or share a theme you made. Select the custom theme, then Edit Theme reopens it in the Studio (re-saving keeps it the same theme), and Export Theme saves a copy wherever you choose so someone else can import it.
  5. Switch between bundled and custom. Any theme card is click-to-apply. Omniscio remembers your last choice; a fresh install starts on the Glassmorphism skin.
  6. Open the themes folder. The Open themes folder button reveals {userData}/themes/ in your OS file explorer — useful for dropping in theme files shared by others, or editing a custom theme by hand and seeing it reload.
  7. Delete a custom theme. Any custom card has a trash button. Bundled themes can't be deleted (they re-seed from the binary anyway).
  8. Write a theme file by hand. Structure is a JSON file with id, name, description, author, version: 1, a dark: { ... } palette (required), an optional light: { ... } palette, and a small preview: { ... } for the card. Each palette maps a small set of camelCase keys to CSS colors — Omniscio translates those into the CSS variables at runtime. The full reference ships with Omniscio; fetch it via Settings → Appearance → Custom Theme Guide. Beyond surfaces / panels / accent / badges, a theme can also set the body fontFamily and the fontFamilyMono (code blocks, terminal, diagnostics, IDs), the tooltip tooltipBg / tooltipBorder / tooltipText, the non-dial shadow/depth tokens (overlayElevation for floating menus, shadowTooltip / shadowSheet / shadowBtnHover), and the full status-colour language (statusAgent / NeedsYou / Error / Ready / Question / Approval / Ember + the -strong on-light variants + linkRgb) — the same tokens the app's error / warning / success / info badges, alerts and status chips read, so those recolour with the theme too. (The chat-message depth and the Motion & Polish depth stay under their own Appearance toggles, not the theme.)

The macOS theme

macOS looks like an app that shipped with the Mac: Apple-style greys, a fixed system blue (#0088FF light, #0091FF dark — it does not follow the Mac's accent setting), edge-to-edge sidebars and title bar, and a solid content area. Filled buttons use a deeper blue (#0064E1 light, #0059D1 dark) so their white labels stay readable; a theme may declare that shade as --accent-fill-rgb, and only macOS does.

On a Mac the desktop shows through. While macOS is the active theme, the main window turns on the Mac's own window glass (Electron vibrancy, the Finder sidebar material): the sidebars become an 84% (light) or 92% (dark) tint over it, the title bar lets it through as one even strip from behind the traffic lights to the right edge, and the conversation pane stays solid. Dialogs always stay solid. The glass turns off — and the theme falls back to the same look with solid panels — when any of these hold:

  • you are on Windows or Linux, or in a browser;
  • the Mac's Reduce transparency accessibility setting is on;
  • the app's light/dark mode does not match the Mac's (for example the app forced dark while the Mac is light) — the glass follows the Mac's appearance, so the tint would be wrong for the text;
  • you pick any other theme. Pop-out windows always stay solid.

Glass text stays readable: secondary text measures at least 5.1:1 on the light glass and 5.7:1 on the dark glass.

Menus are frosted, like a real Mac. In the macOS theme every floating menu, dropdown, right-click menu, select list and small pop-over is a frosted pane: the theme's window colour at 94% (light) or 92% (dark) with the content behind it blurred and slightly saturated, plus the usual thin rim and soft shadow. This works on every computer, not only a Mac, because the app draws it itself. Those percentages are chosen so every text colour stays at the WCAG AA contrast level even with pure black or pure white behind the menu. Menus go back to solid when the Mac's (or the system's) Reduce transparency setting is on, in Low Power Mode, when the app falls back to software rendering, and on phone-width screens. Every other theme keeps solid menus, and big dialogs keep their own Glass dialogs setting. The rule is macos-theme-frosts-floating-menus-above-a-measured-floor in overlay-readable-background-part2-contract.md.

Aurora Glass as a starting point

Aurora Glass is a fully custom-theme-reproducible preset: every value it sets is a field the Theme Studio exposes, so it doubles as a template for building your own skin on top of it.

  • Dark — background base #07080D, card #0C0E16, panel tint rgba(255,255,255,0.045), panel border rgba(255,255,255,0.09), accent #7C8CFF, accent RGB 124 140 255, link 168 179 255, glow rgba(124,140,255,0.42), active indicator #7C8CFF, corners 14px, panel blur 20px.
  • Light — background base #EEF0FB, card #F8F9FF, panel tint rgba(255,255,255,0.72), panel border rgba(60,70,120,0.12), accent #5A6BFF, accent RGB 90 107 255, link 61 78 219, glow rgba(90,107,255,0.28), active indicator #5A6BFF.
  • What stays out of the theme: chat-message depth. The bubbles, cards and composer read --msg-shadow / --msg-highlight, which belong to the Chat Depth setting, so depth follows that toggle and never the theme.
  • chat-depth.md — the Chat Depth dial (Flat / Soft / Glass) in the same Appearance pane, which controls how much shadow and glassy depth the chat messages have, independent of the theme
  • use-super-prompts.md — another example of an extensible asset imported via .json
  • daily-digest.md — digests render in whatever theme you've picked; sharing artifacts inline both the light and dark CSS so viewers see either

Last verified 2026-11-20