Filer AI logoFiler AI

Filer Usecase

Know What Changed, Without Reading It Twice

A Filer folder agent notices the moment a new contract or policy version lands, diffs it against the one it replaces, and sends you what actually changed.

  • File event
  • Chat

What you get

A new version of a contract or policy document arrives, and nobody has time to line it up against the old one paragraph by paragraph. Most of the time it slides by unread — until a clause that quietly changed turns into a problem weeks later.

Point a Filer folder at where these documents land instead. The moment a new version file shows up, its agent wakes on its own, reads both versions in full, and sends you a plain-language summary of what's different — before you've even opened the folder.

How to do it

Screenshots below are from an actual run against a live Filer instance, using a synthetic two-version policy document in place of a real contract.

What it needs

  • A Filer folder with a trust level that allows file-triggered runs and outbound messages
  • A messenger plugin connected — Telegram here, Slack works the same way
  • An inference endpoint — Local AI, Frontier AI (API key), or a local LLM server
  • New versions arrive as separate files (e.g. a "v2" alongside "v1") rather than overwriting the original in place

  1. Start with the version everyone has

    A folder holds the current policy document, with a short instructions file already in place: when a new version shows up, find the one it replaces, read both in full, and send a summary of the differences over Telegram.

  2. Drop in the new version

    A revised version of the same document arrives as a new file next to the old one — exactly how a contract or policy revision actually shows up in practice. Nobody has to open Filer or ask it anything; the file landing is the trigger.

  3. It reads, compares, and tells you

    The new file's arrival wakes the folder's agent on its own. It finds the prior version, reads both start to finish, works out what changed, and sends the summary to Telegram — no one has to ask. Filer's own activity log shows exactly which steps ran and how long each took.

    What the change summary actually said
    "Key Changes: Eligibility — probationers excluded until 3 months completed. Application — notice period reduced to 1 day, submission via internal system. Hours — core hours extended to 10:00-16:00, flexible scheduling allowed. Equipment — added monitor (was laptop only). Security — mandatory VPN connection required for all remote employees. Review recommended."

Verified

This isn't a mockup — the screenshots above are from a live run: the new file's arrival really triggered the folder's agent, it really read both document versions in full, and a real Telegram message was delivered and confirmed through the plugin's own delivery record. This run used a fully local model, no cloud endpoint required — comparing and summarizing is regular language-model reasoning; what's actually being verified here is that the folder notices a new file and reaches an outside channel on its own.

Where else this applies

Anywhere a revised document quietly replaces an old one fits the same watch-diff-notify shape:

  • Vendor contracts — a renewal comes back with terms nudged, not just a date change.
  • Insurance or benefits documents — an annual renewal that changed a deductible or a covered category.
  • Vendor terms of service — a SaaS provider's updated terms landing as a PDF nobody reads end to end.

Other ways in

The walkthrough shows a new file's arrival as the trigger. You can get the same comparison without waiting for a new version to land — the agent runs the identical read-both-and-compare step on demand.

Right-click
Select both versions and the bundled Compare Files action (from the multi-file-tools plugin — install it from Connect first) diffs them immediately. It stops at showing the differences, though; it won't send the summary out for you the way this folder's own configured skill does.
Chat
No trigger or setup needed to ask right now: "What changed between policy_v1.md and policy_v2.md?"
Other automation triggers
If new versions don't reliably land as their own file, a schedule can check for one instead of waiting on a file event — the same shape scheduled-report shows.
Other integrations
Telegram is one delivery channel — Slack works the same way (swap the plugin, the comparing doesn't change).

More usecases

Filer Explorer showing a scheduled digest run

Come Back To an Answer, Not a Backlog

A Filer folder agent wakes up on its own schedule, reads what piled up while you were away, and sends you the digest — before you've even opened the app.

  • Schedule
  • Chat
Read more
See all usecases

Try it in your own folder

Download Filer