The Three Changes That Make AiFiler Faster to Use
Over the last month, we shipped three focused improvements that don't sound flashy in a changelog but add up to a noticeably better experience. View Mode looks cleaner. Commands work the same way everywhere. File parsing is faster. Let's walk through each one.
View Mode: White Paper, No Distractions
When you open a document in AiFiler, you want to read it. Not fight the UI.
We've redesigned View Mode to use a white-paper style—clean margins, readable typography, consistent background—regardless of your theme settings. This means whether you're in dark mode or light mode, the document itself stays readable and professional. The change rolled out in commit 6fa78f6, and it's one of those things you notice immediately when you open a PDF or DOCX file.
Before: Document viewers inherited your app theme, sometimes creating contrast issues or visual noise.
After: Every document renders in a clean, white-paper layout. Your theme settings apply to the sidebar and controls, but the document itself stays consistent and readable.
To see it in action: Open any document in your Knowledge View (the default view when you click a file), and you'll see the difference right away. No settings to toggle. It just works.
One Command Palette, Not Three
AiFiler had a problem we finally fixed: multiple command entry points doing similar things.
The Knowledge View had its own command palette. The Matrix editor (our data-mode spreadsheet) had another. The main app had a third. Users would hit Ctrl+Shift+A expecting one behavior, get confused, and move on.
We've collapsed all three into the Universal Command (still Ctrl+Shift+A). It's the same router that handles 87 different intents—create documents, search, batch operations, navigate, execute AI actions—and now it's the only command palette you need to learn.
This is the work from commits 5bcef49 and 5bcef49, and it simplifies the mental model significantly. One keyboard shortcut. One interface. Same powerful routing underneath.
How to try it:
- Press Ctrl+Shift+A (or Cmd+Shift+A on Mac)
- Type "create" to see document creation options
- Type "batch" to see bulk operations
- Type "search" to jump to search with filters
The palette works the same way everywhere in AiFiler now.
File Parsing Gets Faster
We've optimized how AiFiler ingests documents. The file parsing pipeline (handled by lib/ingest/parseFile.ts) now processes DOCX, XLSX, and PPTX files faster, especially on larger documents.
The improvement came from reducing redundant parsing passes and better streaming of file data to the Anthropic Files API. If you've uploaded a 50MB PowerPoint deck or a complex Excel workbook, you'll notice the parsing completes sooner.
What this means for you: Faster document uploads. Faster indexing. Your documents become searchable seconds earlier than before.
You can test the parsing reliability yourself if you have an ANTHROPIC_API_KEY set up:
npm run skills:smoke
This smoke-tests the DOCX, XLSX, and PPTX skills against the live API and confirms parsing is working correctly.
Why These Three Changes Matter Together
Individually, each change is incremental. Together, they reduce friction:
- Cleaner views mean you spend less time fighting the UI when you're reading documents
- Unified commands mean you don't have to remember three different shortcuts or behaviors
- Faster parsing means your documents are searchable sooner
The common thread: we removed confusion and delay. You get to your documents faster. You interact with them more intuitively. The tool gets out of the way.
What's Coming Next
We're focused on two areas for the rest of Q3:
Intelligence improvements: The Universal Command now routes 87 intents, but we're adding more semantic understanding to how it interprets what you're asking. If you say "show me all contracts from Q2," it should understand that without you having to use search operators.
Mobile refinement: Our mobile components got tap-target improvements in May, but we're expanding mobile support for batch operations and command execution. The goal is for AiFiler to work just as well on a phone as on desktop.
Both of these build on the foundation we've laid with unified commands and faster parsing. The more consistent and responsive the core experience is, the more powerful we can make the AI layer on top.
How to get these improvements: If you're on AiFiler Cloud, you already have them. If you're self-hosting, pull the latest from main and rebuild. The changes are in commits 6fa78f6, 5bcef49, and the parsing optimizations in the latest ingest pipeline.
As always, let us know what breaks or what you'd like to see next. The best product improvements come from watching how real users actually work.
Enjoyed this article?
Get more articles like this delivered to your inbox. No spam, unsubscribe anytime.