April 2025: Cleaner Document Views, Unified Commands, and Faster Parsing

The Problem With Distraction

You're reviewing a contract. Your theme is dark mode. The document viewer suddenly inherits your theme settings—dark backgrounds, custom colors, whatever you've configured. The text is harder to read. The formatting looks wrong. You switch themes just to review one document, then switch back.

That friction shouldn't exist.

This month, we've made three focused improvements to AiFiler that remove exactly this kind of friction: cleaner document viewing, a unified command system, and faster file parsing. These aren't flashy features. They're the kind of changes that make you realize something was broken only after it's fixed.

Document Viewers Now Always Use White-Paper Style

Starting today, all document viewers—whether you're looking at a PDF, Word document, or spreadsheet—render in a consistent white-paper style. Your theme settings no longer bleed into the document view.

What changed: Previously, document viewers inherited your workspace theme. If you preferred dark mode for the interface, documents rendered dark too. This made reading difficult and broke the visual hierarchy of the actual document.

What happens now: Click into any document (via the three-dot menu → "View" or by pressing Enter on a selected row), and you'll see a clean, white background with black text. No matter your theme. No matter your workspace settings.

This applies across all document types:

• PDF files
• Word documents (.docx)
• Excel spreadsheets (.xlsx)
• PowerPoint presentations (.pptx)

The change is automatic. No settings to toggle. No preference to configure. Just open a document and read it the way it was meant to be read.

Knowledge View Now Has a Single Editor Mount

The Knowledge view used to have three separate editor instances mounted simultaneously. This was a legacy artifact from when the interface was being refactored. It worked, but it was inefficient—three mounts meant three subscriptions, three state updates, three potential sources of lag.

What we fixed: We collapsed these three mounts into one unified wrapper. The result is cleaner code, fewer re-renders, and a snappier interface when you're adding or editing knowledge entries.

You won't see a visual difference. But you'll feel it. Typing in the knowledge editor is now more responsive. Switching between documents and knowledge entries is faster.

Universal Command Now Handles All Document Creation

Before this update, you had multiple ways to create new documents:

• The "New" button in the sidebar
• The "New" picker in the toolbar
• Context menus on specific views
• Keyboard shortcuts for specific document types

This was confusing. Which button did what? Where should you click to create a spreadsheet versus a document?

What changed: We unified all document creation paths into the Universal Command (Ctrl+Shift+A on Windows/Linux, Cmd+Shift+A on Mac).

Now, when you need to create anything—a new document, spreadsheet, presentation, or knowledge entry—you open Universal Command and type what you want:

• Type "new doc" → creates a document
• Type "new sheet" → creates a spreadsheet
• Type "new presentation" → creates a presentation
• Type "new knowledge" → creates a knowledge entry

The old scattered buttons are gone. One command. One interface. Consistent everywhere.

This also means the command palette no longer has three separate "New" pickers competing for space. It's a small UI cleanup, but it makes the interface feel more intentional.

File Parsing Is Faster

We've optimized the file ingestion pipeline. When you upload a document, AiFiler now parses it faster—especially large files.

The technical detail: We improved how the system batches parsing requests to the Anthropic API and how it handles the file store (via the Anthropic Files API). Previously, large documents would queue up and wait. Now they process more efficiently.

What you'll notice: Uploading a 50-page PDF now takes seconds instead of 10-15 seconds. Batch uploads (multiple files at once) are even faster because the system processes them in parallel rather than sequentially.

This is particularly useful if you're doing bulk imports—moving documents from another system, uploading client packages, or ingesting historical records.

How to Try These Changes

For document viewing:

1. Open any document in your workspace
2. Click the three-dot menu on the document row
3. Select "View" (or press Enter)
4. Notice the clean white background, regardless of your theme

For Universal Command:

1. Press Ctrl+Shift+A (Windows/Linux) or Cmd+Shift+A (Mac)
2. Type "new" to see all creation options
3. Select the document type you want
4. Start editing immediately

For file parsing:

1. Upload a document via the "Upload" button or drag-and-drop
2. Watch the parsing progress in the status bar
3. The document will be searchable and indexed faster than before

What's Coming Next

We're working on three areas for the next update:

Smarter search operators. Right now, you can search by filename, tags, and date. We're adding intent-based search—things like "show me all contracts from Q1" or "find documents mentioning budget."

Offline-first knowledge. The Knowledge view will soon cache locally, so you can browse and search your knowledge entries even without an internet connection.

Batch document operations. Select multiple documents and perform actions on all of them at once—tag them, move them, export them, or archive them.

These changes are in active development. We'll have more details in May's update.

The Philosophy Behind These Changes

You might notice a pattern: none of these updates add new features. They remove friction from existing features.

That's intentional. AiFiler already does a lot. The question isn't "what else can we build?" It's "what's making the current experience slower or more confusing than it needs to be?"

Document viewers that inherit your theme? Friction. Multiple "New" buttons scattered across the interface? Friction. Slow file parsing? Friction.

We've removed three sources of friction this month. That's the work of April.

Try the update. Let us know what breaks. And if you find something else that feels slow or confusing, tell us—that's what the next update will fix.