September 2026: Unified Views, Smarter File Parsing, and Security Hardening

The Changes That Matter This Month

We shipped three significant improvements this week. None of them are flashy. All of them fix real problems.

First: Document viewers now render in white-paper style regardless of your theme preference. If you've been squinting at dark-mode documents or dealing with contrast issues in light mode, that's gone.

Second: The knowledge view editor now uses a single mount point instead of three separate ones. This eliminates unnecessary re-renders, reduces memory overhead, and makes the codebase easier to maintain.

Third: We cleared four Supabase ERROR advisories from our security audit. These were edge cases in how we handled authentication state, but we fixed them.

Let's walk through what changed and why.

Document Viewers: White Paper, Every Time

Here's the problem: AiFiler lets you choose between light and dark themes. That's great for the rest of the app. But when you're reading a document—a PDF, a Word file, a spreadsheet—your theme preference shouldn't control how the document renders.

A dark background behind a document makes it harder to read. A light background behind a document is what you expect. So we made a choice: document viewers now always render with a white-paper background, regardless of whether you have dark mode enabled elsewhere in AiFiler.

This is a small change with a big impact. If you've been using dark mode and noticed that PDFs looked odd, or that you had to squint at spreadsheets, try opening a document now. The contrast should feel natural.

How to see it: Open any document in view mode (click the eye icon on a document row, or press V after selecting a document). Your theme setting no longer affects the document background.

Editor Consolidation: One Mount, Not Three

The knowledge view used to spin up three separate React mounts for the editor. This was a legacy pattern from when the knowledge system was being refactored. We've now collapsed it into one.

Why does this matter? Three mounts meant:

• Three separate state trees
• Three initialization cycles on every view switch
• Harder to debug editor state issues
• More memory consumption than necessary

Now there's one editor mount. One state tree. One initialization. The knowledge view loads faster, and the codebase is cleaner.

You won't see a UI change. The editor works exactly the same way. But if you've noticed the knowledge view occasionally felt sluggish when switching between documents, it should feel snappier now.

How to try it: Open the knowledge view (click any document to enter edit mode). Switch between documents. The transitions should feel smoother.

Security: Four Advisories Resolved

During our recent audit, Supabase flagged four ERROR-level advisories related to how we handle authentication state. Specifically:

• Stale session tokens in edge cases
• Missing error handling in auth middleware
• Insufficient validation of Supabase responses
• Race conditions in concurrent auth calls

We've patched all four. The fixes were surgical—we didn't change the auth flow or require any action from you. But if you're security-conscious (and you should be), you can rest easy knowing these edge cases are now handled.

What you need to do: Nothing. These were backend fixes. Your authentication experience doesn't change.

What's Coming Next

We're working on three things for October:

Smarter intent routing: The Universal Command currently handles 87 intents. We're building a heuristic system that learns which intents you use most and surfaces them first. This means fewer keystrokes to get what you need.

Offline-first file metadata: Right now, file metadata syncs from Supabase. We're moving to a local-first model with SWR and localStorage prefixing. This means faster loads and better performance on slow connections.

Batch document export: You'll be able to select multiple documents and export them as a single DOCX, PDF, or ZIP. This is particularly useful for client deliverables or archival.

The Bigger Picture

These three changes—white-paper viewers, editor consolidation, and security hardening—don't sound revolutionary. They're not. They're the kind of work that doesn't get headlines but makes the product feel more polished.

That's intentional. We're past the phase of adding new features. We're in the phase of making the features we have work better, faster, and more reliably.

If you've been using AiFiler for a while, you'll notice the product feels tighter. That's not an accident. It's the result of dozens of small improvements like these.

Try the white-paper viewer on your next document. Switch between knowledge view documents and feel the snappier transitions. And if you're an admin, you can rest knowing your authentication is more secure.

Questions? Hit us up in the community Slack or email [email protected].