You've probably noticed something different when you open AiFiler today. We've been quiet for a few weeks—not because nothing was happening, but because we were rethinking how the product fits together.
The result: a leaner interface, faster file operations, and a command system that actually understands what you're trying to do.
The Big Change: One Command, 87 Intents
Until last month, AiFiler had three separate command palettes. One for creating documents. One for navigation. One for AI operations. You'd hit different keyboard shortcuts depending on what you wanted to do, and the system had to guess which palette you meant.
We've unified all of that into Universal Command (Ctrl+Shift+A on Windows/Linux, Cmd+Shift+A on Mac). It now routes 87 different intents—everything from "create a new spreadsheet" to "batch-tag these documents" to "search for contracts signed in Q1"—through a single, intelligent router.
Here's what changed for you:
Before: You'd open the command palette, realize it was the wrong one, close it, hit a different shortcut, and try again.
After: Hit one shortcut. Type what you want. Universal Command figures out your intent and executes it.
The routing happens in lib/intelligence/universalRouter.ts. It uses heuristics and context to understand whether you're asking for a creation action, a search, a batch operation, or something else entirely. No more modal roulette.
View Mode Gets a Visual Refresh
Document viewers should feel like reading, not like using software. We forced all document viewers in view mode to render with a white-paper style, regardless of your theme preference.
This means:
- PDFs, DOCX files, and XLSX spreadsheets now display with consistent typography and spacing
- Dark mode users still get dark mode everywhere else, but documents render on white backgrounds for readability
- No more theme bleeding into embedded viewers
The change is in components/view/ and the document rendering pipeline. It's a small thing, but it removes cognitive friction. You're reading a document, not configuring a UI.
Three Editor Mounts Become One
The knowledge view used to mount three separate editors—one for the main content, one for metadata, one for relationships. Each mount had its own state management, its own lifecycle, and its own opportunities to break.
We collapsed them into a single wrapper component. This means:
- Faster load times for knowledge documents (the wrapper batches state updates)
- No more race conditions between editor instances
- Simpler debugging when something goes wrong
If you've ever seen a knowledge document flicker or fail to save metadata, this fixes it.
New Document Picker Replaces Three
Related to the editor consolidation: we replaced three separate "new document" pickers with a single New Picker. Whether you're creating from the sidebar, the command palette, or the dashboard, you now use the same interface.
The picker understands context. If you're inside a project, it defaults to creating a document in that project. If you're in the knowledge graph, it offers to link the new document to existing nodes. It's the same tool, but it adapts to where you are.
Collaboration Fixes: 18 Bugs, Zero Breaking Changes
We audited the entire collaboration system and fixed 18 bugs without changing the API or breaking existing workflows:
- Fixed race conditions in real-time cursor tracking
- Resolved permission checks that were incorrectly denying access
- Corrected timestamp handling in conflict resolution
- Improved offline-first sync behavior
None of these are flashy. All of them matter if you work with other people. If you've had documents that wouldn't sync or permissions that felt broken, these fixes are for you.
Faster File Parsing, Better Skill Reliability
File parsing now uses a two-stage pipeline:
- Fast path: For common formats (DOCX, XLSX, PPTX), we extract text and structure immediately
- Skill path: For complex operations (table extraction, image OCR, entity recognition), we queue the work and call the appropriate skill
This means your files appear in AiFiler instantly, and the AI analysis happens in the background. You're not blocked waiting for Claude to read a 50-page PDF.
We also smoke-test all document skills against the live Anthropic API before deployment. Run npm run skills:smoke locally to verify your setup. This catches skill failures before they hit production.
How to Try It
Universal Command: Open any document or the dashboard, then press Ctrl+Shift+A (or Cmd+Shift+A). Type "create spreadsheet" or "find contracts" or "batch tag" and watch the router figure out what you mean.
View Mode: Open any document in view mode. Notice the clean, white-paper rendering. Switch your theme to dark mode and notice that the document stays readable.
New Picker: Click the "+" button in the sidebar or use the command palette to create a new document. The picker will adapt based on your context.
Collaboration: If you share documents with teammates, you should notice smoother real-time updates and fewer permission errors.
What's Next
We're working on:
- Search parsing improvements to handle more complex queries (date ranges, nested filters, boolean operators)
- Intent handler expansion to recognize more domain-specific commands
- Mobile tap target refinement for better touch-friendly interaction
The architecture is in place. We're just expanding what it can do.
These changes are live now. No migrations, no new setup. If you're on the latest version, you already have them.
Questions? Hit us up in the community forum or reply to this email. We read everything.
Enjoyed this article?
Get more articles like this delivered to your inbox. No spam, unsubscribe anytime.
