The Three Fixes That Matter
You've probably noticed something feels cleaner when you open a document in AiFiler lately. That's not your imagination. Over the last few weeks, we shipped three focused improvements that address real friction points in how you view, edit, and navigate documents.
These aren't flashy features. They're the kind of fixes that don't announce themselves but make your day noticeably smoother.
View Mode Now Ignores Your Theme Preference
Here's the problem we solved: When you switched to dark mode in AiFiler settings, document viewers would follow that theme. Sounds reasonable, right? Except documents—especially PDFs, Word files, and spreadsheets—are designed to be read on a white background. Dark mode made them harder to read, not easier.
The fix: Document viewers now force a white-paper style regardless of your workspace theme setting. Your dark mode preference still applies everywhere else in AiFiler. Just not where it matters most—the actual content you're reading.
This is a small change with outsized impact. If you've been squinting at dark-themed documents, try opening one now. The difference is immediate.
Command Palette Just Became Singular
Before this week, AiFiler had three separate command palettes floating around:
- The Universal Command (Ctrl+Shift+A) for general actions
- A separate palette for document creation
- Another for workspace navigation
This wasn't intentional fragmentation. It happened as features grew. But it created a cognitive load: users had to remember which palette did what.
The fix: We collapsed all three into the Universal Command. Now when you press Ctrl+Shift+A, you get one unified router that handles all 87 intents—from "create a new spreadsheet" to "search my knowledge graph" to "invite a collaborator."
The architecture change was significant (it required rewriting the universalRouter.ts to handle doc-creation paths), but the user experience is simple: one keyboard shortcut, one command palette, every action you need.
Try it: Press Ctrl+Shift+A and type "new sheet" or "invite" or "search contracts." Everything works from the same place now.
Knowledge View Editor Mounts Collapsed Into One
This one's technical, but it affects performance. The knowledge view—where you see all your documents, relationships, and metadata—was mounting three separate editor instances. Each mount had its own state management, its own re-render cycle, its own memory footprint.
The fix: We wrapped all three into a single editor mount with unified state. The knowledge view still shows you everything it did before. But now it does it with one-third the component overhead.
You'll notice this most when you're working with large document collections (50+ documents in a single view). Scrolling is smoother. Switching between documents feels faster. The app doesn't lag when you're making rapid edits.
Why These Fixes Matter Together
Individually, each fix solves one problem:
- View mode fix = better readability
- Command palette unification = simpler navigation
- Editor mount collapse = better performance
Together, they represent something bigger: we're consolidating the interface. Fewer moving parts. Fewer places to look. Fewer reasons for the app to stutter.
This is the opposite of feature creep. It's feature focus. We're not adding new capabilities. We're making the existing ones work better.
How to Experience These Changes
- For view mode: Open any document (PDF, DOCX, or spreadsheet). Notice the white background regardless of your theme setting.
- For unified command: Press Ctrl+Shift+A and try creating a new document, searching, or inviting a team member—all from the same palette.
- For performance: Open the knowledge view with 20+ documents and scroll through. The smoothness is the point.
If you're on mobile, the command palette is accessible via the three-dot menu in the top navigation bar.
What's Coming Next
We're not done with consolidation. The next phase focuses on:
- Sidebar cleanup: Reducing the number of navigation panels without losing functionality
- Search parser optimization: Making complex queries faster and more intuitive
- Offline-first improvements: Better handling of large document sets when you're not connected
The goal remains the same: fewer abstractions, more clarity, faster workflows.
These three fixes shipped over the last two weeks. If you're running the latest version of AiFiler, you're already using them. If you notice anything that feels off or want to suggest the next consolidation target, let us know.
Enjoyed this article?
Get more articles like this delivered to your inbox. No spam, unsubscribe anytime.
