Does FileMayor send my files anywhere?

No. The core engine runs entirely on your machine. The optional AI features (the Curative Triad) call out to a model only with file metadata — names, sizes, paths, extensions — never file contents. Disable AI entirely and the rest still works.

Every move is recorded in a journal kept inside the workspace. `filemayor undo` reverses the most recent operation; `undo --all` reverses the entire session. The journal persists across crashes and reboots, so you can roll back even after closing the laptop.

Yes. The CLI is the canonical surface. Every command accepts `--json`, so you can pipe to jq, integrate with shell scripts, or wire it into CI. The Desktop app and the PWA are visual layers over the same engine — anything you script with the CLI works identically in the others.

What if the AI proposes a bad plan?

The Curative Triad separates planning from execution by design. `cure` outputs a plan; nothing is touched until you run `apply`. The Guardrail layer additionally refuses destructive batches even when planned. And if a plan slips through that you regret, `undo --all` rolls it back.

v4.0.1 · AI-powered · fully reversible

Your AI can suggest. FileMayor can act — with one undo to roll it back.

Your folders, on command.

FileMayor v4 — a command bar for your filesystem. Diagnose folders, plan moves, apply with rollback. Local-only, on Mac, Windows, and Linux.

scan explain cure apply undo

Download FileMayor

Available onCLIDesktopPWAMac · Windows · Linux

⌘ K

›

enter ↵

local · offline-first · journaled · undo-anything

$ filemayor explain ~/Downloads

Scanned 1,248 files (4.2 GB) in 1.4s

────────────────────────────────────────────

Images482 files · 1.2 GB

Videos12 files · 2.1 GB

Documents634 files · 0.8 GB

────────────────────────────────────────────

Diagnosis: 22/100 · 1,242 dupes · 3.8 GB recoverable

→ filemayor cure ~/Downloads

v4.0.1 · what's new

Six things v4 does that v3 didn't.

Same engine. Same rollback. New ways to summon it — from the keyboard, from Claude, or from any MCP-aware client.

⌘K

Command bar

Press ⌘K from anywhere in the app. Type what you want done. FileMayor runs it.

HomeView

Active workspace at a glance

See your current folder, recent moves, files categorized, and security status on one screen.

MCP

@filemayor/mcp

Install one MCP server. Claude Desktop and other MCP clients can now diagnose folders and apply moves.

Skill

Claude Code Skill

Install the FileMayor skill once. Claude Code can run diagnose, cure, and undo on demand.

Plan cards

Review before apply

Proposed moves appear as cards. Accept, reject, or rewrite each one before anything touches disk.

Status bar

Always-on status

Operation count, undo depth, and security checks shown at the bottom of every view.

HomeView

The new home screen.

Active folder, recent activity, and security status on one screen. Diagnose, cure, apply, and undo are one keystroke each.

FileMayor

⌘K to summon

Active workspace

~/Projects/filemayor

Good morning, Chevza. The workspace looks healthy. 4 cures pending review.

Change workspaceDiagnose now

Reversible moves

all journaled · undo any

Files categorized

last 30 days

Security layers

Chevza Doctrine green

0 / 6

Diagnose

⌘D · explain folder

Cure

⌘E · plan + dry-run

Apply

⌘↵ · journaled

Undo

⌘Z · last operation

jailer · okvault · okguardrail · okundo depth · 42last cure · 2m ago

Works with Claude

Tell Claude to clean your folders. It already knows how.

One config entry and Claude Desktop, Claude Code, or Cursor can audit your folders, propose a plan, and apply it — while FileMayor keeps a full record of every move so you can take it all back.

Read the guide Learn more

Nothing leaves your machine
Every move is reversible
Ask in plain English
Works with Claude Code Skill

claude_desktop_config.json

{
  "mcpServers": {
    "filemayor": {
      "command": "npx",
      "args": ["filemayor", "mcp"]
    }
  }
}

Restart Claude. Ask: “clean up my Downloads”.

What happens when you run it?

Five verbs. Real output.

No screenshots. No mocks. The output below is what FileMayor prints today, in the order you would type the commands.

scanexplaincureapplyundo

01scan
filemayor scan ~/Downloads
$ filemayor scan ~/Downloads
Scanned 1,248 files (4.2 GB) in 1.4s
Images482 files · 1.2 GB
Videos12 files · 2.1 GB
Documents634 files · 0.8 GB
Archives18 files · 0.1 GB
Code102 files · 18 MB
1,242 duplicates · 11.2 GB potentially recoverable
Read the directory. No moves yet — no cloud, no permission prompts beyond reading. The CLI takes 1.4 seconds on 1,248 files.
02explain
filemayor explain ~/Downloads
$ filemayor explain ~/Downloads
FILEMAYOR DIAGNOSIS
Health: 22/100 (POOR)
Issues
• 63 screenshots clogging the root level
• 14 duplicate installers (.exe, .dmg) — 1.7 GB
• 27 archive files older than 12 months
• 8 stale browser downloads (.crdownload)
→ filemayor cure ~/Downloads
Diagnose the actual problem. A 0–100 health score plus a plain-English issue list. Still no moves, still no upload, still no risk.
03cure
filemayor cure ~/Downloads --prompt "organize by type"
$ filemayor cure ~/Downloads --prompt "organize by type"
CURATIVE PLAN
Gemini 2.0 Flash · 0.8s · metadata only, no file contents read
Strategy
→ Move 63 screenshots → ~/Downloads/Screenshots
→ Consolidate installers → ~/Downloads/Software
→ Archive .zip > 12mo → ~/Archive/2024
→ Trash 8 .crdownload artifacts
Plan covers 112 files · ETA 3.1s
→ filemayor apply
Plan, do not act. The AI proposes specific moves with rationale. Nothing happens to your filesystem until you type the next verb.
04apply
filemayor apply
$ filemayor apply
[1/4] Screenshots63 moved ✓
[2/4] Software14 moved ✓
[3/4] Archive27 moved ✓
[4/4] Trash8 removed ✓
Cure applied · 112 files · 3.1s
journaled at .filemayor/journal/2026-04-26-1442.json
Execute reversibly. Every move written to a session journal in your workspace. Sub-second per category. Six security layers between the plan and your filesystem.
05undo
filemayor undo --all
$ filemayor undo --all
Reverting 112 operations from session 2026-04-26-1442
[1/4] Trash8 restored ✓
[2/4] Archive27 restored ✓
[3/4] Software14 restored ✓
[4/4] Screenshots63 restored ✓
Session reverted · 112 files restored
journal sealed · downloads back to original state
Change your mind. One command reverses the whole session. The journal is the safety net — you can explore aggressively without losing data.

The same five verbs work on the desktop app and the PWA. Same engine, three skins.

25k+

npm installs

—

GitHub stars

tests passing

runtime vulns

what counts? →

Under the hood —Chevza DoctrinejailvaultguardrailhaltarchitectsecurityRead the architecture

Pricing

Free forever. Pro when ready.

Core features stay free. Pro unlocks the AI Curative Triad, watch mode, and unlimited bulk operations. USD pricing — local currency conversion shown automatically.

Free

For individuals getting started.

Directory scanning & analysis
File organization
Junk cleanup
Undo last operation
Config file support
Up to 50 files per operation
MCP server for personal use

Install free

Honest answers.

Does FileMayor send my files anywhere?
No. The core engine runs entirely on your machine. The optional AI features (the Curative Triad) call out to a model only with file metadata — names, sizes, paths, extensions — never file contents. Disable AI entirely and the rest still works.
How does Undo work?
Every move is recorded in a journal kept inside the workspace. `filemayor undo` reverses the most recent operation; `undo --all` reverses the entire session. The journal persists across crashes and reboots, so you can roll back even after closing the laptop.
Can I script it?
Yes. The CLI is the canonical surface. Every command accepts `--json`, so you can pipe to jq, integrate with shell scripts, or wire it into CI. The Desktop app and the PWA are visual layers over the same engine — anything you script with the CLI works identically in the others.
What if the AI proposes a bad plan?
The Curative Triad separates planning from execution by design. `cure` outputs a plan; nothing is touched until you run `apply`. The Guardrail layer additionally refuses destructive batches even when planned. And if a plan slips through that you regret, `undo --all` rolls it back.