An accent colour, instead of Bootstrap's pink
Try the real interface
Explore this workspace.
Real Torbie UI · mock sessions
Loading Torbie…
Technical background
Every code span in the app — paths, commits, identifiers, the build tooltip — was Bootstrap's #d63384, a pink belonging to no colour scheme here and the last hardcoded accent left in the UI. appearance.accentColor replaces it, and null follows the scheme.
The problem
Every <code> in the app — paths, commits, identifiers, the build tooltip — was Bootstrap's #d63384, a pink belonging to no colour scheme here. theme.vars.scss overrode it to orange, but nothing imports that file any more, so the pink was live and was the last hardcoded accent left in the UI.
How it works
appearance.accentColor (Settings → Window) replaces it. Null follows the colour scheme.
Settings
appearance.accentColor:nullColour for code, paths and identifiers in the UI. Null follows the colour scheme.
Details
- The configured value is parsed before it is used. The theme variables are recomputed on every keystroke in the settings box, and a half-typed
#abthrown out of the colour parser would take every other variable in that pass with it. - It goes through the same contrast floor as the rest of the chrome, so a pale pick is darkened against the window background rather than left illegible.
- The build tooltip now follows the theme instead of being Bootstrap's near-black — which is what keeps the accent inside it legible, since it is contrasted against the window and not against black.
What this does not claim
- The source catalogue records no separate caveats for this entry. The implementation and evidence above define its scope.
Source commits
UI & themingAdded 2026-09-056 files+136 / −6 lines