February 2025: Cleaner Document Views, Unified Commands, and Security Hardening

The Latest Wave of Improvements

You've got documents open. You're reading through a contract, cross-referencing a spreadsheet, comparing two PDFs side-by-side. The last thing you want is your interface getting in the way. That's why we've spent the last month fixing exactly that—removing friction from the places where you spend the most time.

This release focuses on three things: how documents look when you're reading them, how commands work when you're searching or executing actions, and how we keep your data safe from the ground up.

Document Viewing Gets a Visual Reset

When you open a document in view mode, AiFiler now forces a white-paper style regardless of your theme settings. This sounds small. It's not.

Before this change, if you had dark mode enabled, your documents would render with a dark background. That works fine for most interfaces. For reading documents—contracts, reports, spreadsheets—it creates unnecessary eye strain and makes text harder to parse. We realized we were solving the wrong problem. Dark mode is great for your workspace. It's terrible for document content.

How it works: Open any document and click the preview icon or press Enter on a selected row. The document viewer now renders with a white background and black text, regardless of your theme. Your workspace theme stays exactly as you set it. Only the document content area resets.

This aligns with how most PDF readers, word processors, and spreadsheet applications work. You're reading a document, not configuring an interface.

Universal Command Consolidates Three Palettes Into One

Here's a before-and-after that matters:

Before: You had three separate command systems.

• The main command palette (Ctrl+Shift+A) for global actions
• A separate "New" picker for creating documents
• A secondary command palette buried in the editor

After: One unified command system handles everything.

We collapsed these three entry points into the Universal Command (still Ctrl+Shift+A). Now when you open it, you get:

• Document creation (type "new" or just start typing a document type)
• Global actions (search, settings, workspace management)
• Context-aware suggestions based on what you're currently viewing

This is one of those changes that doesn't sound revolutionary until you use it. You're no longer hunting for the right menu. You're not context-switching between three different command interfaces. You press one key combination and everything you need is there.

How to try it: Press Ctrl+Shift+A (or Cmd+Shift+A on Mac) and start typing. Try "new doc" to create a document. Try "search" to find something. Try "settings" to adjust preferences. The palette learns what you use most and surfaces those commands first.

Editor Mount Consolidation: One Wrapper, Not Three

This is a technical improvement that affects reliability more than user experience, but it matters.

Previously, the knowledge view mounted three separate editor instances. This created race conditions, memory leaks, and occasional rendering glitches when you switched between documents quickly. We collapsed this into a single wrapper component that manages one editor instance and reuses it across views.

What this means for you: Faster switching between documents. No more occasional blank screens when you open a new file. Lower memory usage if you're working with large documents. The app feels snappier.

Security: Four Supabase ERROR Advisors Cleared

We identified and fixed four security advisories in our Supabase configuration. These weren't exploitable vulnerabilities—they were configuration issues that created unnecessary risk surface.

Specifically:

• Removed overly permissive RLS (Row-Level Security) policies on three tables
• Tightened JWT token expiration windows
• Added rate limiting to sensitive endpoints
• Implemented additional CSRF protection on state-changing operations

None of these required action from you. Your data was never at risk. But we're committed to security-first architecture, and that means fixing issues before they become problems.

What's Coming Next

We're working on three major areas for the next release:

Intent heuristics refinement: The Universal Command will get smarter about understanding what you're trying to do. Type "find contracts from Q4" and it'll know you want search, not document creation. This is powered by our intent detection system, and we're expanding it from 87 handlers to 120+.

File parsing speed: We're optimizing how AiFiler ingests DOCX, XLSX, and PPTX files. Current parsing uses the Anthropic Files API with live validation. We're adding local preprocessing to catch errors before they hit the API, cutting parse time by 40%.

Knowledge graph visualization: Right now, the knowledge graph powers your search behind the scenes. Next month, you'll see it. We're building a visual graph explorer so you can see how your documents connect, what entities appear across files, and what relationships the AI has discovered.

How to Update

If you're using AiFiler web, you're already on the latest version. No action needed.

If you're running a self-hosted instance, pull the latest from main and run:

npm run build
npm run test:run

We've added 47 new unit tests to cover the command consolidation and editor mount changes. Run the full test suite before deploying to production.

One More Thing

We've been tracking how people use the app, and we noticed something: most users never discover the search operators. Things like type:contract or created:2025-01 exist and work great, but they're hidden. Next month we're shipping a searchbar hint system that surfaces these operators contextually. You'll see suggestions as you type.

That's it for this release. Smaller, more focused changes. Better document reading. Faster commands. Tighter security. The kind of improvements that don't make headlines but make you want to use the app more.