Influxx Appearance and Quick Commands: Theme, Warp, and Saved Recipes
Influxx Appearance and Quick Commands — this guide goes deep on the two surfaces that make the cockpit feel like yours every day: how the window looks (theme, zoom, fonts, sidebars, status bar, terminal themes, app icon, and editor comfort), and how Quick Commands turn the tab strip into a personal launcher for bootstrap scripts, test runners, formatters, and agent start lines. You will learn where each control lives, how Appearance differs from Terminal and Floating window settings, how to import Warp themes, how to scope commands globally or per project, and how to build a small command library that matches a real coding week. Everything below reflects shipped Influxx desktop surfaces.
Why Appearance and Quick Commands Belong Together
Appearance decides whether you can stare at the cockpit for hours without friction. Quick Commands decide whether the actions you repeat ten times a day require retyping. Together they turn a fresh install into a personal IDE-shaped environment without forcing you to abandon the CLIs and shells you already trust. First launch already nudges theme and appearance; this guide is the deeper pass after you know where Settings lives and want the chrome and the recipes dialed in.
Open Settings with ⌘, on macOS or Ctrl+, on Windows and Linux. Search “appearance,” “zoom,” “Warp,” or “commands” if you do not want to browse the rail. Appearance lives under the Desktop group today; Quick Commands live under Tools → Commands. Older docs may say Interface → Appearance or Workflows → Quick Commands — those were presentation labels for the same panes. Deep links can jump straight to Appearance or open Commands with an add-command intent when another surface sends you there.
Make the cockpit match your eyes, then save the shell lines you refuse to retype — Appearance for chrome, Quick Commands for muscle memory.
Open Appearance and Tune Theme First
Go to Settings → Appearance. Start with Theme: dark, light, or system-following so the app window matches the rest of your desktop. Changes apply live — leave Settings open beside a terminal and a markdown tab while you judge contrast. If you present on a shared screen, try system-following or a light theme before the meeting rather than mid-demo. Theme is the foundation; zoom, fonts, and terminal coloring sit on top of it.
UI Zoom, IDE Font, and Language
UI Zoom scales the entire Influxx interface in controlled steps. Use it on high-DPI displays when chrome feels tiny, or when you pair to a projector and need larger labels without changing OS display scaling. IDE Font sets the typeface for Influxx interface chrome — sidebars, settings, boards — and is separate from the font you pick for terminal glyphs under Tools → Terminal. Language chooses the interface locale (system default or a specific language when available) so labels match how you read the rest of your machine.
- Theme: Dark, light, or follow system — apply live and keep judging beside real tabs
- UI Zoom: Step the whole cockpit larger or denser for display and pairing scenarios
- IDE Font: Chrome typeface only; terminal font stays under Tools → Terminal
- Language: Interface locale when you need labels other than the system default
Sidebar Chrome and Explorer Density
Appearance also controls left sidebar presentation and density, plus related explorer behavior such as whether git-ignored files show dimmed in the file explorer. If your monorepo is noisy with ignored build output, dimming ignored files keeps the explorer readable without leaving the worktree. If you prefer a compact rail for more vertical space on laptop screens, tighten density after you settle theme and zoom so you are not chasing two variables at once.
Status Bar Toggles That Match What You Monitor
The status bar can show or hide usage meters and agent-related indicators. Turn on what you actually watch during parallel agent days — token or subscription usage, connection pills, integration status — and hide the rest so the bottom chrome stays calm. Pair status bar choices with Desktop → Usage when you care about rate limits across Claude, Codex, Grok, and other providers. Appearance decides visibility; Usage explains the numbers.
Appearance does not own every “how the window feels” control. Tools → Terminal owns shell defaults, renderer, scrollback, and terminal font choices that matter when you live in Ghostty-class WebGL terminals all day. Tools → Floating window owns the global terminal, browser, and markdown panel that is not tied to a repo worktree — including floating markdown stored under Influxx’s app-owned floating-workspace directory. Configure those panes after Appearance so you do not hunt for Warp import or floating toggles in the wrong place.
Terminal Themes and Warp Import
Style terminal coloring independently from the app theme. On desktop, Influxx can import Warp themes as Influxx terminal themes from YAML theme folders or a chosen checkout. If your team already standardized on Warp colors, import those themes so agent tabs and plain terminals share the same palette. After import, verify contrast on both idle shells and busy agent TUIs — some themes that look fine for a prompt line wash out dense agent output.
- Independent terminal coloring: Keep app chrome and PTY colors on separate knobs
- Warp theme import: Bring YAML theme folders or a checkout into Influxx terminal themes
- Validate on agent tabs: Check readability while a CLI agent is actively streaming
- Pair with Terminal pane: Font, renderer, and scrollback still live under Tools → Terminal
App Icon and Editor Comfort
Where the platform supports it, pick an app icon variant that fits your dock or taskbar. Editor comfort settings — minimap, word wrap, autosave delay, and rich markdown spellcheck — live in appearance and related editor sections so writing Sidebar notes, reviewing markdown tabs, and editing plans stays comfortable for long sessions. Source, Rich Editor, and Preview modes on markdown tabs inherit these comfort choices; very large or unsupported documents may force Source mode for safety, so keep autosave and wrap tuned even if you mostly live in Source.
Theme for the room, zoom for the display, Warp for the PTY, editor comfort for the plan — Appearance is four jobs, not one toggle.
A Practical Appearance Pass (Ten Minutes)
1) Set Theme to match your desktop. 2) Adjust UI Zoom until sidebar labels and the tab strip feel readable at arm’s length. 3) Pick IDE Font if the default chrome typeface fights your preference. 4) Dim ignored files in the explorer if the tree is noisy. 5) Enable only the status bar meters you glance at during agent runs. 6) Import or pick a terminal theme and confirm it on a live agent tab. 7) Set minimap, word wrap, autosave delay, and markdown spellcheck for note writing. 8) Only then open Tools → Terminal and Floating window for shell font and floating chrome. Save mental energy by finishing Appearance before you invent Quick Commands.
Quick Commands: Saved Terminal Recipes
Settings → Commands (Quick Commands) stores terminal commands you reuse constantly — bootstrap scripts, test runners, formatters, deploy stubs, lint one-liners, and agent launchers. Each entry is an ordinary saved string plus metadata in your settings profile. Commands do not run until you invoke them. They are not remote macros and they are not a substitute for per-repo setup hooks that fire automatically when a worktree is created — use hooks for “every new workspace must install,” and Quick Commands for “I personally want this one-liner on demand.”
- Global scope: Available across projects — ideal for personal agent launchers and machine-wide helpers
- Per-project / per-repo scope: Keeps monorepo scripts from polluting another product’s tab strip
- Settings list filters: Focus on global commands, the active project, or a custom selection of repos
- Deep link add intent: Other surfaces can open Commands ready to create a new recipe
How to Create and Run a Quick Command
Open Settings → Commands. Add a new entry with a clear label and the exact shell line you want. Choose global or project scope intentionally — if the command only makes sense inside one repo’s package manager, scope it to that project. Save. With a worktree selected, open the Quick Commands menu from the tab strip + control and pick the recipe. Influxx runs it into the appropriate terminal context so you do not leave keyboard flow to hunt a README. Edit or delete stale entries the same way you maintain shell aliases: prune aggressively so the menu stays short.
Day-to-day invocation is the whole point. The tab strip already offers New terminal, New agent, New browser, and New markdown shortcuts; Quick Commands sits beside those as the custom layer. Use New agent when you want the default TUI agent with product-aware launch. Use a Quick Command when you need a specific binary, flags, or a non-agent script (tests, codegen, local servers) without opening Settings again. Note Run still builds a context pack and launches through the agent path — Quick Commands do not replace note-to-agent, they complement it for shell recipes.
Recipe Ideas That Match Real Influxx Weeks
Build a small library, not a junk drawer. Global: your alternate agent launch lines (for example a Codex or Grok command with the flags you always forget), a “doctor” script that prints tool versions, and a formatter you run before review. Per project: package-manager install, test, typecheck, and storybook or dev-server starts that belong only to that repo. Keep secrets out of the command text — prefer env files, setup hooks, or shell profiles that load credentials. If a teammate might inherit a machine image, assume command strings are visible and write them like public aliases.
- Agent launchers: Saved CLI start lines when overrides in Coding agents are not enough for a one-off flavor
- Bootstrap: Install or sync steps you still want on demand after setup hooks already ran once
- Verify: Test, lint, typecheck, and build commands scoped per repo
- Review helpers: Diff exporters, snapshot updaters, or docs generators you run before Source Control
- Ops stubs: Local deploy or tunnel commands you trust, without pasting tokens into the recipe
Quick Commands vs Setup Hooks vs Agent Overrides
Setup hooks (per-repo) run when a worktree is created — automate npm install, env templates, and warm caches so every parallel workspace starts ready. Agent command overrides in Settings → Coding agents permanently change how a named catalog agent launches from New Workspace, new agent tabs, and related paths. Quick Commands are manual, labeled recipes from the tab strip. Use hooks for automatic bootstrap, overrides for “Claude/Codex/Grok always start like this,” and Quick Commands for everything you still want to trigger by name during a session.
Security and hygiene matter because Quick Commands feel like aliases: easy to paste a token “just once.” Do not. Keep API keys in environment managers or ignored env files that hooks or your shell load. Prefer project-scoped commands that call package.json scripts over embedding long inline secrets. Review the Commands list when you rotate credentials. Remember that sidebar notes and context packs are separate storage — a Quick Command that cats a note path is fine; a Quick Command that embeds private plan text is how secrets leak into settings backups.
Pairing Appearance with Command Density
Once zoom and theme are comfortable, you will open the tab strip + menu more often. Keep Quick Command labels short and scannable at your chosen zoom level — long labels wrap badly when UI Zoom is high. If you present the cockpit, hide noisy status meters and keep a clean theme so the audience sees agents and diffs, not personal recipe names. For multi-monitor setups, finish Appearance, then Floating window, then pin your most-used global commands so the secondary display’s floating terminal can run the same recipes without hunting the main worktree strip.
- Readable labels: Name commands for glanceability at your UI Zoom
- Demo mode: Calm theme + fewer status toggles when sharing screen
- Floating follow-through: Global recipes remain useful in floating terminals
- Prune monthly: Delete commands you have not invoked in weeks
Troubleshooting Appearance and Commands
If the app looks wrong after a theme change, confirm you edited Appearance rather than only a terminal theme. If glyphs in the PTY look mismatched to chrome, adjust Tools → Terminal font separately from IDE Font. If Warp import does nothing useful, confirm you pointed at a YAML theme folder or checkout the importer understands, then re-open a terminal tab. If Quick Commands are missing for a repo, check scope filters — a project-scoped command will not appear when another project is active. If a command fails immediately, run it in a plain New terminal to separate recipe typos from agent launch issues. If deep links open the wrong pane, use Settings search for “commands” or “appearance” as the reliable fallback.
What “Done” Looks Like
Appearance is done when theme, zoom, fonts, sidebar density, status bar, terminal theme (including Warp import if you use it), app icon where supported, and editor comfort match how you work for a full day. Quick Commands are done when your global and per-project lists cover the shell lines you were still copying from READMEs, secrets stay out of the strings, and you can invoke recipes from the tab strip without opening Settings. Related help covers the full Settings map, keybindings, privacy, terminals and quick open, and coding agents — use those when you need chords, telemetry, or CLI fleet strategy beyond chrome and recipes.
Your eyes and your aliases should not fight the cockpit — tune Appearance once, grow Quick Commands as the week teaches you what you actually repeat.
Quick recap: open Settings → Appearance for theme, UI Zoom, IDE Font, language, sidebar chrome, status bar toggles, terminal themes with Warp import, app icon, and editor comfort; use Tools → Terminal and Floating window for shell font/renderer and floating chrome. Open Settings → Commands to save global or per-project terminal recipes; run them from the tab strip Quick Commands menu. Prefer setup hooks for automatic worktree bootstrap and Coding agents overrides for permanent CLI launch lines. Keep secrets out of command text. When the window looks right and the recipes you need are one click away, Appearance and Quick Commands have done their job.
