May 2025: Unified Interfaces, Faster Document Views, and Security Hardening

The Headline: One Interface, One Way to Work

Over the last month, we've shipped a series of focused improvements that sound small but add up to something bigger: AiFiler now works the same way everywhere. We collapsed three separate editor mounts into a single wrapper, unified all command palettes into the Universal Command, and standardized document viewing across every theme. No more switching between interfaces. No more hunting for the right palette. One consistent experience.

Why We Built It

Consistency matters more than most people think. When you're working with 200 documents and switching between knowledge view, matrix view, and inline editing, your brain burns cycles just remembering which interface you're in. Three different command palettes meant three different ways to do the same action. Document viewers looked different depending on your theme setting.

We heard this from power users: "I shouldn't have to relearn the same action in different parts of the app." They were right.

The changes we shipped this month directly address that friction.

What Changed

One Editor Wrapper (Audit-013)

Previously, the knowledge view mounted three separate editor instances—one for inline editing, one for the full editor modal, and one for the matrix data-mode editor. This meant:

• Slower initialization (three mounts instead of one)
• Harder to maintain consistent behavior across editing contexts
• More memory overhead
• Inconsistent undo/redo state

Now, a single wrapper manages all three contexts. The editor initializes once, and the same instance handles inline edits, full-screen editing, and matrix operations. You won't notice the difference in your workflow, but you'll feel it in responsiveness.

How to try it: Open any document in knowledge view. Click to edit inline, then open the full editor modal. Notice the editor loads instantly instead of reinitializing.

Unified Command Palette (Audit-011)

We had three command palettes scattered across the app:

• The main Universal Command (Ctrl+Shift+A)
• A separate palette in the knowledge view
• Another in the matrix editor

Now there's one. Universal Command handles all 87 intent handlers across every context. Whether you're in knowledge view, matrix mode, or document view, Ctrl+Shift+A opens the same palette with the same commands.

This matters because it means:

• You don't have to remember which palette is active
• Keyboard shortcuts work consistently everywhere
• New commands automatically available in all contexts
• Fewer bugs from maintaining parallel command systems

How to try it: Press Ctrl+Shift+A in any view. Type "batch" to see batch operations, "search" for search operators, or "create" to spawn a new document. Same commands, same behavior, everywhere.

White-Paper Document Viewing (View-Mode Styling)

Document viewers now force a white-paper style regardless of your theme setting. This means:

• PDFs, Word docs, and spreadsheets always render with consistent contrast
• Dark mode doesn't break document readability
• Print previews match what you see on screen
• Accessibility improves (white background + black text = highest contrast)

Before, if you had dark mode enabled, some document types would render with inverted colors or poor contrast. Now the viewer overrides your theme preference for documents specifically, while keeping your theme everywhere else.

How to try it: Enable dark mode in settings. Open any document in view mode. Notice the document always displays on a white background with black text, while the rest of the interface stays dark.

Consolidated New Document Picker (Audit-012)

We had multiple ways to create a new document:

• A button in the sidebar
• A button in the matrix toolbar
• A button in the knowledge view header
• A keyboard shortcut

Now there's one unified picker. Click the "New" button anywhere in the app, and you get the same dialog: choose document type, set workspace, add tags. Same experience whether you're in matrix view or knowledge view.

How to try it: Press Ctrl+N (or click any "New" button). You'll see the same creation dialog regardless of where you are in the app.

The Numbers

These changes reduced our codebase complexity by:

• 3 editor mount instances → 1 wrapper
• 3 command palettes → 1 Universal Command
• 4 document creation flows → 1 unified picker
• 2 document viewer implementations → 1 white-paper standard

Fewer code paths mean fewer bugs, faster feature development, and more predictable behavior.

What's Coming Next

We're working on:

• Smarter intent detection in Universal Command (fewer keystrokes to find what you need)
• Offline-first document editing (edit while disconnected, sync when you're back online)
• Batch operation templates (save your favorite batch workflows and reuse them)
• Knowledge graph visualization (see how your documents connect visually)

The pattern here is clear: we're removing friction, standardizing interfaces, and making AiFiler feel like one cohesive tool instead of a collection of features.

How This Affects Your Workflow

If you're an existing AiFiler user, you'll notice:

1. Faster app startup (one editor instead of three)
2. Consistent keyboard shortcuts (Ctrl+Shift+A works everywhere)
3. Better document readability (white-paper styling in all themes)
4. Simpler document creation (one picker, one workflow)

If you're new to AiFiler, you'll notice there's less to learn. One command palette. One way to create documents. One way to view them.

That's the goal: make the tool disappear so you can focus on your work.

---

Questions? Reply to this email or open Universal Command (Ctrl+Shift+A) and search "help" to reach our support team.