FileMayor vs Hazel.

The decision matrix.

Mac-only and rules-first.

If you are on macOS exclusively, prefer writing explicit IF/THEN rules over describing intent in natural language, and want a one-time-purchase tool with a long maintenance history, Hazel is excellent. The rules engine is mature, and AppleScript integration unlocks anything macOS exposes.

Cross-platform, AI-planned, reversible.

FileMayor exists for the cases Hazel does not cover well: Windows and Linux machines, teams that want a shared CLI workflow, anyone who would rather describe what they want in plain English than write rules, and anyone who wants the safety net of a full-session undo on every operation.

The Curative Triad — explain → cure → apply — separates planning from execution by design. The Chevza Doctrine ensures that even when an AI proposes a destructive plan, six layers of safety architecture sit between the proposal and your filesystem.

Rules are great. Until you have to maintain them.

Hazel users come to FileMayor when the rules library grows unwieldy, when a new machine is Windows or Linux, or when they want AI to handle the decisions rather than pre-specifying every condition. The two tools complement each other well for power users who want both.

• →No per-folder rule configuration — describe the goal once, FileMayor generates the plan.
• →Works identically on macOS, Windows, and Linux — one CLI, one workflow, any machine.
• →Every operation is logged and reversible — Hazel has no equivalent undo for batched moves.

Continuous watching — no rules to write.

FileMayor watches a folder and applies a consistent policy to every new file that arrives — with a full audit log.

$ filemayor watch ~/Downloads --policy "sort by type, archive if older than 90 days"

  ◆ Watch mode active on ~/Downloads
    Policy: sort by type · archive after 90 days
    Journal: ~/.filemayor/journal/downloads.log

  [10:14:02] NEW   report-q4.pdf      → PDFs/
  [10:14:02] NEW   photo-2026-05.heic → Images/
  [10:15:30] NEW   setup.dmg          → Installers/
  [10:41:00] AGED  brief-jan.docx     → _archive/2026-01/  (92 days old)

  All operations logged. Run `filemayor undo --session latest` to reverse.

FileMayor vs Hazel — FAQ.

Is FileMayor better than Hazel?

They have different philosophies. Hazel is a mature Mac rules engine — you define explicit IF/THEN conditions per folder and it acts automatically. FileMayor takes a different approach: describe your intent in plain English, receive an AI-generated plan, approve it, and apply it with full rollback. Neither is universally better; the right choice depends on whether you want rules or intent, and whether you need cross-platform support.

Does FileMayor work on Windows and Linux?

Yes. FileMayor runs on macOS, Windows, Linux, and as a PWA. Hazel is macOS-only. If your team spans operating systems or you manage files across machines, FileMayor provides a consistent CLI and MCP interface everywhere.

Can FileMayor replace Hazel for folder watching?

Yes, for most use cases. FileMayor includes watch mode — it monitors specified folders and applies configured rules whenever new files arrive. Unlike Hazel's rules engine, FileMayor's watch mode logs every action and supports undo. For complex, condition-heavy automation on macOS with AppleScript integration, Hazel's rules engine is more powerful.

What is the main difference between FileMayor and Hazel?

Intent model. Hazel requires you to write explicit IF/THEN rules for each folder and condition. FileMayor lets you describe what you want ("archive files older than 6 months, deduplicate the rest") and generates a plan from that intent. FileMayor also adds a review step before applying anything, and logs every operation for rollback — safety guarantees Hazel does not provide.

Can I use FileMayor and Hazel together?

Yes. They do not conflict. A common pattern: Hazel governs a watched inbox folder with precise rules (rename downloads by date, move invoices to Dropbox), while FileMayor handles the larger periodic organisation sessions — quarterly cleanup, project archiving, deduplication across drives. Many users run both side by side.