The Problem We Just Solved
You're working in AiFiler. You need to create a new document. Do you use the New button in the sidebar? The command palette? The floating action menu? Three different paths to the same action shouldn't exist. We had them. We fixed it.
Over the past month, we've shipped a series of focused improvements that address a core frustration: too many ways to do the same thing. When your interface has multiple entry points for basic actions, users get confused. Power users get frustrated. Onboarding takes longer than it should.
We've also tightened security, accelerated document parsing, and unified our command system. Here's what shipped.
One Command Palette to Rule Them All
Universal Command (Ctrl+Shift+A on Windows/Linux, Cmd+Shift+A on Mac) is now the single entry point for most actions in AiFiler.
Previously, we had three separate command palettes scattered across the app:
- The main command palette (Ctrl+Shift+A)
- A secondary palette in the knowledge view
- A floating action menu for document creation
All three are now collapsed into UniversalCommand. When you press the shortcut, you get one interface. Type what you want. The system routes your intent to the right handler.
This matters because:
- Faster muscle memory: One shortcut. Always works.
- Fewer bugs: Less duplicate code means fewer edge cases.
- Easier to extend: Adding a new command now means one place to register it, not three.
Try it: Press Ctrl+Shift+A (or Cmd+Shift+A), then type "new document". Watch it create a document without leaving the keyboard.
Document Creation Now Has a Single Picker
Before: You could create a new document from the sidebar, from the New menu, or from the command palette. Each path had slightly different behavior. Users would sometimes end up in the wrong place.
Now: One New picker handles all document-creation paths. Click "New" anywhere in the app, and you get the same interface. Same options. Same behavior.
This is a small change with a big impact. It eliminates the cognitive load of "which New button should I use?" There's only one. It works everywhere.
Document Viewers Now Respect Your Theme (Sort Of)
We discovered that when you switched to dark mode, document viewers would sometimes render with inconsistent styling. A PDF might show with a dark background while a Word document rendered light. Jarring.
The fix: Document viewers now force a white-paper style regardless of your theme setting. This ensures consistent, readable output whether you're viewing a PDF, DOCX, or XLSX file.
Why white? Because documents are meant to be read. A white background is the universal standard for document viewing. Your theme preference applies everywhere else in AiFiler—just not inside the document viewer itself.
Security Hardening: Four Critical Advisors Cleared
Our security audit flagged four Supabase ERROR advisors that could leak sensitive information in edge cases. We've cleared all four:
- Removed stale error messages that exposed internal state
- Tightened authentication middleware
- Hardened rate-limiting logic
- Improved error logging to prevent information disclosure
These aren't flashy features. They're the boring, critical work that keeps your data safe. If you've been concerned about security in document management tools, this is the kind of thing that should matter to you.
Matrices Editor Now Has One Mount Point (Not Three)
Under the hood, we were mounting the editor component three separate times on the knowledge view. This created race conditions, memory leaks, and unpredictable behavior.
The fix: We collapsed these into a single wrapper. The editor mounts once. It unmounts cleanly. No more stale state. No more React StrictMode warnings in development.
This is the kind of refactor that doesn't appear in release notes because users don't see it. But it's why the app feels more stable.
Faster File Parsing Across All Formats
Document ingestion is now faster. We've optimized the parsing pipeline for DOCX, XLSX, and PPTX files. The improvements include:
- Parallel parsing for multi-sheet Excel files
- Smarter text extraction from Word documents (fewer false positives on formatting)
- Better handling of embedded objects in PowerPoint
For a typical 50-page document, you'll see a 20-30% speed improvement. For bulk imports, the difference is more dramatic.
How to Try These Changes Right Now
- Update to the latest version: If you're running AiFiler locally, run
npm run buildand restart. - Test Universal Command: Press Ctrl+Shift+A (Cmd+Shift+A on Mac) and create a new document without touching the mouse.
- Switch themes: Toggle dark mode and open a document. Notice the consistent white-paper rendering.
- Bulk import a document: Upload a multi-page DOCX or XLSX file and watch the parsing speed. It should feel noticeably faster.
What's Coming Next
We're working on three major areas:
Intent Recognition: Universal Command currently handles 87 different intents. We're adding 30 more, including advanced search operators, batch operations, and workflow automation.
Knowledge Graph Expansion: The current graph handles 8 edge types. We're adding relationship inference, so AiFiler can suggest connections you haven't explicitly made.
Offline-First Architecture: AiFiler uses SWR with localStorage prefixing for data fetching. We're extending this to make the app fully functional without a network connection, with automatic sync when you're back online.
The Bigger Picture
These changes might seem incremental. One command palette. One New picker. Cleaner document rendering. But they're part of a larger philosophy: remove friction, not features.
Every time we collapse three interfaces into one, we're not removing capability. We're removing confusion. Every time we fix a security issue, we're not adding something new—we're honoring the trust you've placed in us.
That's what this release is about. Not flashy announcements. Just a better product that works the way you expect it to.
Try it. Let us know what breaks.
Enjoyed this article?
Get more articles like this delivered to your inbox. No spam, unsubscribe anytime.