February 2025: Cleaner Interfaces, Unified Commands, and Security Hardening

The Headline: Three Months of Refinement, Not Reinvention

We shipped 14 commits this quarter focused on one principle: remove friction. No new features. No marketing announcements. Just a product that works better for the people who use it every day.

The biggest wins: we collapsed three separate command palettes into a single Universal Command (Ctrl+Shift+A), forced all document viewers to render consistently regardless of your theme, and fixed four critical Supabase security advisories that were flagged in our audit.

Here's what changed and why it matters.

Before: Three Palettes, One Confused User

If you've been with AiFiler for a while, you know the pain. You'd hit Ctrl+Shift+A to open the command palette. But depending on where you were in the app—editing a matrix, viewing a document, or managing knowledge—you'd get a different palette with different commands.

Want to create a new document? Sometimes it was in the palette. Sometimes it was in a menu. Sometimes it was a button in the sidebar.

The cognitive load was real. Users reported spending 10-15 seconds hunting for the right action instead of executing it.

What we changed: We unified all command routing through a single Universal Command handler (commit 5bcef49). Now, regardless of context, Ctrl+Shift+A opens the same palette with 87 intent handlers that understand what you're trying to do.

How It Works Now

Press Ctrl+Shift+A anywhere in AiFiler. The palette appears. Type what you want:

• "Create new doc" → routes to document creation
• "Move to client folder" → routes to batch operations
• "Search contracts" → routes to knowledge search
• "Export as PDF" → routes to document export

The Universal Command uses intent heuristics to parse your input and route it to the right handler. If you're in a matrix, it knows you might want matrix-specific actions. If you're viewing a document, it offers document-specific actions. But the interface is always the same.

Result: One palette. 87 intent handlers. Zero confusion.

Before: Document Viewers That Changed With Your Theme

This one was subtle but annoying. AiFiler supports light and dark themes. But when you opened a document to read it—a PDF, a Word file, a spreadsheet—the viewer would inherit your theme preference.

Dark theme? The document viewer went dark. Hard to read. Light theme? The viewer went light. Sometimes blinding.

What we changed: All document viewers now render in white-paper style, regardless of your theme preference (commit 6fa78f6). Your theme controls the sidebar, the navigation, the UI chrome. But the document itself always looks like a document.

Why This Matters

It sounds small. But it's the difference between:

• Squinting at a dark PDF because you prefer a dark UI
• Reading a document comfortably, always

Users who spend hours reviewing contracts, proposals, or compliance documents reported immediate relief. The cognitive friction of "why is this hard to read?" disappeared.

Before: Security Advisories We Couldn't Ignore

In our Q4 security audit, Supabase flagged four ERROR-level advisories in our configuration. They weren't critical vulnerabilities—no data was exposed—but they were misconfigurations that violated best practices.

What we changed: We cleared all four advisories (commit adb2975). This involved:

• Tightening Supabase Row Level Security (RLS) policies
• Removing overly permissive auth configurations
• Hardening session management
• Fixing error logging that exposed sensitive data

None of this is visible to you. But it means AiFiler is now passing security audits without caveats.

The Bigger Picture: Consolidation Over Addition

These three changes represent a philosophy shift we made this quarter: consolidation over addition.

Instead of shipping new features, we asked: "What's broken? What's confusing? What's slow?"

The answers led us to:

• Collapse three command palettes into one (audit-011, audit-012)
• Force document viewers to consistent styling (view-mode fix)
• Silence StrictMode race conditions that were cluttering dev logs (audit-010)
• Replace stale activeTable references with the new activeMatrix naming (audit-010)
• Drop deprecated webhook types (TABLE_, ROW_) that were causing confusion

This is boring work. It doesn't make for exciting announcements. But it's the work that makes a product feel polished instead of patched.

How to Try It

If you're already using AiFiler, you'll get these improvements automatically on your next login. No action needed.

If you want to test the new Universal Command behavior:

1. Open AiFiler
2. Press Ctrl+Shift+A (or Cmd+Shift+A on Mac)
3. Type any action you'd normally do: "create", "move", "export", "search"
4. Watch it route to the right handler

For document viewing, open any PDF, Word file, or spreadsheet. Notice the viewer now has consistent white-paper styling, even if your theme is dark.

What's Next

We're not done consolidating. The next phase focuses on:

• Matrix editor unification – We're collapsing three separate editor mounts into a single wrapper (audit-013 in progress)
• Smarter intent parsing – The Universal Command will get better at understanding ambiguous requests
• Offline-first improvements – We're refining how AiFiler handles SWR with localStorage prefixing for better offline data fetching

We're also exploring how the Anthropic Files API (which powers our file store) can help us index documents faster without re-parsing them on every search.

The philosophy remains: make the existing product better before adding new things. Users don't need more features. They need the features they have to work flawlessly.

---

Questions? Drop them in our community Slack. We read every message.