You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since you asked for it, what i liked in wave was the possibility to set a custom background that has nothing to do with the theming. And what also would be an UX improvement -> setting the font with a font dialog that finds available fonts in the system. With freetext fields i am uncertain what to type to swap the font with my favourite one. Ok thats maybe two issues in one :D
Custom backgrounds parallel to theming — Settings → General → Custom background:
Paste any CSS background (gradients, colors, url(…) images) into the free-form field — your example works as-is. There's also a preset dropdown, and the first preset ("Lovely") is literally the gradient from your post.
A Terminal opacity slider (your bg:opacity) controls how much of the background shows through the terminal color scheme — the terminals render with a translucent theme background on top of the custom layer, so it composes with any color scheme.
Live preview right in the settings panel.
Font picker — Settings → Terminal now has a dropdown listing every font family installed on your system (enumerated from the Windows font registry), with a live preview line so you can see the pick immediately. The free-text stack field is still there below it for advanced fallback stacks.
Grab the zip from the release (right-click → Unblock after download), or wait for the in-app update badge. Thanks for the great suggestion — the Wave-style config example made the intent crystal clear!
Reopened for the retest you posted — and you were right, it wasn't working. Fixed for real in v0.25.0.
What was wrong: your instinct ("the theming interfering with the background") was very close. wmux was correctly giving the terminal color scheme a translucent background, but xterm.js 6.0 ships a stock CSS rule that paints its scroll viewport opaque black underneath — in 5.x that layer was overwritten from the theme, in 6.0 it no longer is. So the translucent One Dark background composited over black instead of over your gradient: preview fine (no xterm there), real terminals opaque. One CSS override on that layer fixes it for both renderers.
No new option needed — the existing Terminal opacity slider now does what it always claimed. Pull it down to ~50–60% and you should get the Wave look from your last screenshot. If the effect still feels too subtle at the default 88%, that's expected — it's a per-percent alpha, not a toggle.
Thanks for testing twice and for the screenshots — genuinely useful bug report.
Activity
feat(appearance): custom backgrounds parallel to theming + system fon…
amirlehmam commentedon Jul 11, 2026
Both halves of this shipped in v0.24.0 🎨
Custom backgrounds parallel to theming — Settings → General → Custom background:
background(gradients, colors,url(…)images) into the free-form field — your example works as-is. There's also a preset dropdown, and the first preset ("Lovely") is literally the gradient from your post.bg:opacity) controls how much of the background shows through the terminal color scheme — the terminals render with a translucent theme background on top of the custom layer, so it composes with any color scheme.Font picker — Settings → Terminal now has a dropdown listing every font family installed on your system (enumerated from the Windows font registry), with a live preview line so you can see the pick immediately. The free-text stack field is still there below it for advanced fallback stacks.
Grab the zip from the release (right-click → Unblock after download), or wait for the in-app update badge. Thanks for the great suggestion — the Wave-style config example made the intent crystal clear!
arnonuem commentedon Jul 11, 2026
just wow 🥳
arnonuem commentedon Jul 11, 2026
Not yet working as intended. I guess it has to do with the theming interfering with the background. The preview looks ok
And i can see the background behind the terminals -->
But then i guess an option like - Transparent Terminal is missing (i am currently on one dark theme)-->
How it should look like (example from the wave terminal)
fix(appearance): custom background now shows through terminals (#89, #91
amirlehmam commentedon Jul 13, 2026
Reopened for the retest you posted — and you were right, it wasn't working. Fixed for real in v0.25.0.
What was wrong: your instinct ("the theming interfering with the background") was very close. wmux was correctly giving the terminal color scheme a translucent background, but xterm.js 6.0 ships a stock CSS rule that paints its scroll viewport opaque black underneath — in 5.x that layer was overwritten from the theme, in 6.0 it no longer is. So the translucent One Dark background composited over black instead of over your gradient: preview fine (no xterm there), real terminals opaque. One CSS override on that layer fixes it for both renderers.
No new option needed — the existing Terminal opacity slider now does what it always claimed. Pull it down to ~50–60% and you should get the Wave look from your last screenshot. If the effect still feels too subtle at the default 88%, that's expected — it's a per-percent alpha, not a toggle.
Thanks for testing twice and for the screenshots — genuinely useful bug report.
feat(appearance): custom backgrounds parallel to theming + system fon…
fix(renderer): disable allowTransparency to enable LCD subpixel antia…
feat(ap 8000 pearance): real window transparency via Win11 backdrop materials
fix(appearance): drop the opacity floor to 0 and let custom backgroun…
feat(prompts): the outline as a real pane, and a highlight colour you…
fix(remote): no opaque black slab or native scrollbar under the phone…