Files & Folders
Tell It to Tidy Up,And It Does the Moving
Sorting a folder by hand is dragging and dropping until it looks right. Describe the end state instead and Plexon works out which files match and moves them, in one ordered batch that stops at the first problem. It reports what is eating the space before you decide, and anything it clears out lands in the recycle bin.
What happens in this clip
- The System Monitor board reads this computer live: gauges, running processes, and the space you could reclaim.
- Ask what is slow and a plain answer comes back, not a dump of counters.
- Ask it to tidy a folder and it moves and renames the files itself.
- Four screenshots land in a dated folder, renamed.
- It reports what it moved. The same chores can be put on a schedule, off by default.
Related features
Say What You Want Tidied
Point Plexon at a folder and describe the end state. It works out which files match, does the moving itself, and tells you what it did. You are describing an outcome, not dictating a sequence of commands.
- "Move everything over 100 MB in Downloads into a folder called big"
- "Put every invoice PDF into Documents/invoices, by year"
- "Rename these photos to the date they were taken"
- "Clear out the installers I already ran"
It Tells You What Is Taking the Space
Before anything moves you can ask what is in a folder and how big it is. Plexon reports every entry with its own size and the total underneath it, without opening a single file, so the decision is made on the real numbers rather than a guess about which folder got fat.
- "What is using 40 GB on this drive?"
- "Which folder in my project is the biggest?"
- "When did anything in here last change?"
- Sizes come from the filesystem, not from reading the files
Deleting Means the Recycle Bin
Anything Plexon clears out goes to the Recycle Bin on Windows, the Trash on macOS, and the desktop trash on Linux. You restore it the way you restore anything else, with no Plexon involved. On a network share or any volume where a delete could not be undone, it refuses rather than removing the file for real.
- Restore from Explorer or Finder
- Refuses outright where the delete could not be undone
- Space comes back when you empty the bin
- The same rule whether it is one file or four hundred
A Batch Stops at the First Problem
Several moves in one instruction run in the order you gave them, because the order usually matters: make the folder, then move things into it. If one step fails, the rest are reported as skipped instead of running against a state that never came about, and the whole batch is checked for obvious mistakes before the first file is touched.
- Checked as a whole before anything is touched
- A typo in the last step cannot half-apply the first
- An existing destination is left alone unless you said to overwrite
- Missing parent folders are created for you
Inside a Repository It Uses Git
Moving a file inside a git repository is recorded with git mv, so the history follows the file instead of showing a deletion and an unrelated new file. Outside a repository it is an ordinary move, and either way the file ends up where you asked.
- History follows the file through a rename
- Falls back to a plain move outside a repository
- Works the same in a worktree or a submodule
- Nothing is committed for you
How It Works
Move, Rename, Copy
Files and folders alike, one at a time or several in one instruction, with the parent folders created as needed.
Nothing Deleted for Good
Every removal goes to your real recycle bin. On a volume that has none, Plexon refuses instead of deleting permanently.
Answers About Space
A folder total, every entry with its own size, and when each last changed, read from the filesystem without opening anything.
Ordered Batches
Steps run in the order you gave them and stop at the first failure, so a half-finished reorganisation is not a thing that can happen.
Git-Aware Moves
Inside a repository a move is recorded with git mv, so a rename does not read as a deletion plus an unrelated file.
Finds Them First
Pointed at a folder outside your project, Plexon lists what is actually there: installers, archives, logs, all of it.
Inside Your Boundaries
Every path goes through the same File access setting as the rest of Plexon. In safe mode, anything outside your trusted locations asks first.
Planning Stays Read-Only
In Plan mode Plexon will describe the reorganisation it intends and cost it out, but it cannot move anything until you approve.