A File Organizer With History: See and Undo Every Automatic Move
Most file organizers move your files silently. File Arbor keeps a searchable history of every move, rename, and delete — with undo. Here's why that matters.
Most file organizers move your files and say nothing. File Arbor keeps an Action History: a searchable record of every move, rename, delete, and command run, with the rule that did it, the file it touched, and the time it happened. Reversible actions can be undone from that history. It is the difference between trusting automation and hoping it behaved.
This is a feature people do not ask for until the first time a rule does something they did not expect. Then it is the only feature that matters.
The problem with silent automation
Automation runs when you are not looking. That is the point of it — and also the risk.
A rule with a slightly-too-broad match moves a folder of files you wanted to keep. An age filter set to 30 days when you meant 300 quietly clears out the wrong things. With most tools, you find out the way everyone finds out: something is missing, and you have no idea what moved it, where it went, or when.
A file organizer that acts on your files should be able to tell you what it did. Without that, you are trusting it blind, and the rational response to blind trust is to not automate the things that actually matter — which defeats the purpose.
What the Action History records
File Arbor logs every action a rule takes, grouped by type:
- Moved — the file, its source, its destination, and the rule
- Renamed — the old name and the new one
- Deleted — what was sent to the Recycle Bin or removed permanently
- Command runs — each Run command execution, with its exit code and full output
Every entry carries the file, the rule that acted, and the timestamp. You can scan it chronologically or by action type. When you want to know "what happened to my files," the answer is one panel away instead of a forensic dig through folders and timestamps.
Undo, for the things that can be undone
A log you can act on beats a log you can only read. Reversible actions — moves and renames — can be undone straight from the history, which puts the file back where it started.
File Arbor is also honest about what cannot be reversed. A file sent to the Recycle Bin is recoverable, but from the Recycle Bin itself, the normal way. A file removed with permanent delete is gone, and the app does not pretend otherwise — permanent deletions are not added to the undo history, because there is nothing to restore. Knowing the boundary is part of trusting the tool.
How to review what File Arbor did
- Open the Action History. It shows a chronological list of everything the app has done to your files.
- Filter by action type. Narrow to moved, renamed, deleted, or command runs to find what you care about.
- Inspect an action. Select an entry to see the rule, the file, the timestamp, and — for commands — the output.
- Undo if needed. Reverse a move or rename in place; restore a Recycle Bin deletion from the Recycle Bin.
Why this matters for command rules
The history earns its keep most with the Run command action. A command that runs unattended can fail quietly — a path changed, a tool was missing, an exit code nobody saw.
File Arbor records each command run in a Command runs panel with the exit code and the full output. When a scheduled command fails at 3 AM, you are not reconstructing what went wrong from nothing; the output is sitting there when you check. That record is what makes command-based automation safe to rely on instead of something you babysit.
The trust it buys
The honest reason an audit log matters: it lets you automate more.
When you can see and reverse what a rule did, you stop being cautious about which folders you let the tool manage. You point it at the Desktop, the Downloads folder, the project directories, the archive — because a mistake is visible and fixable, not a silent loss. The history is not a feature you use every day. It is the thing that lets you stop checking, which is the entire reason to automate in the first place.
For the rest of what shipped alongside it, see what's new in File Arbor 1.1.0.
FAQ
Does File Arbor keep a history of what it did?
Yes. File Arbor records every action in an Action History — each move, rename, delete, and command run, grouped by type. You can see which rule acted, which file it touched, and when. It is a searchable audit trail of everything the app has done to your files.
Can I undo an automatic file move?
Yes, for reversible actions. Moves and renames can be undone from the Action History, which puts the file back where it was. Permanent deletions cannot be undone — there is nothing to restore — but files sent to the Recycle Bin can be recovered from there by hand.
How do I see what my file organizer changed?
Open the Action History panel. It lists every action File Arbor has taken, grouped by type — moved, renamed, deleted, or command runs — with the file, the rule, and the timestamp. It answers "what just happened to my files" without you having to dig through folders.
Why does a file organizer need an audit log?
Because automation acts when you are not watching. Without a log, a misfiring rule silently moves files and you only notice when something is missing. An audit log shows exactly what every rule did, so you can trust automation, debug a bad rule, and reverse a mistake quickly.
Does the history record custom command runs too?
Yes. Run command actions are recorded in a Command runs panel with the exit code and full output of each run. When a scheduled command fails overnight, the details are waiting for you instead of being lost, which makes command-based rules far easier to trust.
See it for yourself
Set up a rule, let it run, and open the history to watch exactly what it did. Download File Arbor to try it, or compare the full rule engine on the features page. New here? Start with the getting started guide.
