Back to blog
EngineeringMar 19, 2026· min read

When Your Sidebar Disappears: Shipping Sabine's Light Mode Fix

Sabine's sidebar text was invisible in light mode. Here's how we caught it, fixed it, and improved navigation priority in the same commit.

I switched Sabine to light mode yesterday afternoon and the entire sidebar disappeared. Not the container—the text. Every navigation link, every menu item, just gone. White text on a white background. The kind of bug that makes you wonder how long it's been there and who else hit it but didn't tell you.

This is what happens when you ship fast and test in one mode. I spend 90% of my time in dark mode. Sabine supports light mode because users asked for it, but I wasn't dogfooding it. That's on me.

What Actually Broke

Sabine's sidebar uses Tailwind color tokens that respond to the theme toggle. Somewhere in a recent refactor, the text color stopped respecting the theme context. Dark mode worked fine because the default fallback was light text on dark background. Light mode inherited the same light text color—on a light background.

The fix was straightforward: update the color classes to properly reference theme-aware tokens. Test both modes. Ship it.

Why Upload Knowledge Moved to the Top

While I had the sidebar open, I noticed something else: Upload Knowledge was buried halfway down the menu. But in actual usage, it's the most-accessed feature. Every morning I upload meeting notes, task lists, and context documents. It's Sabine's primary input mechanism.

Navigation hierarchy should reflect usage frequency, not alphabetical order or the sequence I built features in. So I moved Upload Knowledge to the top. Small change, big quality-of-life improvement.

What This Says About Solo-Founder Development

When you're building alone with an AI team, QA is your weakest link. Strug Works can write the code, run the tests, and ship the PR. But it can't switch to light mode on a whim and notice the text is gone. That requires human intuition and usage patterns.

The solution isn't more automated tests—it's more intentional dogfooding. I'm adding a weekly ritual: spend 30 minutes using Sabine in the opposite mode from my default. Switch contexts. Click around. Pretend I'm a new user.

What's Next

This fix is live in production. Light mode now works as intended. Navigation priority reflects actual usage.

Next up: I'm adding theme-specific visual regression tests so this category of bug gets caught in CI before it reaches production. And I'm auditing the rest of the Sabine UI for similar light-mode contrast issues. If the sidebar broke, other components probably have the same vulnerability.

The bigger lesson: autonomous engineering teams are incredibly powerful, but they optimize for the test cases you give them. If you only test in dark mode, that's the only mode that works. The human's job is to define the envelope. The AI's job is to fill it.