DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to file incoming documents from a folder automatically with Bloks

Point an agent at a folder with a rule, so new files are handled the moment they land.

Who it is forA freelancer or small business owner whose invoices and receipts arrive as files in one folder and need filing by hand each week.

The problemEvery new invoice or receipt has to be found and moved manually, which is easy to forget.

The outcomeA watcher on the folder runs your rule when a file lands, and the first look only sets a baseline so existing files are not handled.

What you need first

  • The Bloks desktop app installed on your machine
  • At least one provider you can use: a Claude Code, Codex or Gemini CLI you already signed in to, or an API key for a chat engine
  • A project folder or files the agent is allowed to work in
  • For the iPhone steps: the Bloks iPhone app and a six digit pairing code from your Mac

Steps

  1. Open the agent you want to handle the files and tell it in plain words what to do, for example: when an invoice lands in this folder, file it.
  2. Or ask the agent to keep an eye on the folder, and let it file the watcher itself.
  3. Choose whether the watcher should rehearse on a copy first, so you can check its first actions.
  4. Check the first runs in the conversation and the change card under each reply.
  5. Adjust or remove the watcher in the agent's settings if the rule needs changing.

Prompt for your agent

Using the Bloks repo at hamedgitty/bloks, set up a watcher on the folder <incoming-folder> that files new invoices into <filing-folder>. Expected output: a watcher entry plus a change card for each filed file. Verify that the first look only created a baseline and that the first real file was filed as your rule says.

Caveat. The README says a folder is seen within seconds and a watcher fires at most six times an hour, so bursts of files will be handled over time rather than all at once.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page