Back to browse
FileMayor – A zero-dependency, local-first file organization engine

FileMayor – A zero-dependency, local-first file organization engine

by Chevza·Mar 8, 2026·2 points·0 comments

AI Analysis

●●SolidSolve My ProblemDark Horse

Local file organizer with rollback journal, but competes with existing tools like Hazel and AutoSorter.

Strengths
  • Zero dependencies + deterministic fallbacks means instant categorization without network calls or heavy processes.
  • Full rollback journal via .filemayor-journal.json is genuinely useful safety net for destructive filesystem operations.
  • Cross-platform CLI with sensible defaults (scan, organize, clean, undo) works out of box.
Weaknesses
  • 12 hardcoded categories feel rigid; AI SOP parsing is Pro-only and requires Gemini API despite 'local-first' positioning.
  • 440 weekly downloads and zero dependencies are listed as stats, not proof of adoption—unclear if real users trust this for critical files.
Target Audience

Users with messy local filesystems who want privacy-first organization; developers managing build artifacts and logs.

Similar To

Hazel · AutoSorter · Belvedere

Post Description

Hi HN,

My documents folder recently became an absolute disaster—thousands of unsorted PDFs, raw images, scattered .csv files, and code snippets from the last three years.

I looked for automated categorization tools, but every modern solution seemed to require uploading my local file metadata to a cloud UI or running an overly heavy background service. I explicitly wanted an offline, privacy-first engine.

So I built FileMayor. It’s a 100% local-first data organization engine built on Node.

A few technical properties I focused on:

Zero Runtime Dependencies: The core Node engine is pure. No vulnerabilities, no bloat, and minimal memory footprint. Deterministic Fallbacks: By default, files are sorted instantly into 12 hardcoded extensions/mime-type categories (Documents, Media, Archives, Code, etc.) using offline pattern matching. The Rollback Journal: Every file mutation is logged to a local .filemayor-journal.json. If an organization run ruins your directory structure, a single undo command reverses the entire batch operation instantly. AI SOPs (Opt-in): If you need complex directory trees, it parses .md or .txt Standard Operating Procedures, securely queries the Gemini API to transpile the intent into a locked YAML schema, and executes the file moves. I packaged versions for Windows, macOS (arm64), and Linux (.deb).

I'd really appreciate any feedback on the rollback journal architecture or the regex pattern matching approach!

Similar Projects

OtherPass

32M lines of AI code – GED to AGI

208 projects listed, zero depth—rename your fork and call it a collection.

lordwilsonDev
203mo ago