Mouzi 0.1.6: it updates itself now, and a user caught a comma bug the same day

I pushed Mouzi 0.1.6 out yesterday. I am not going to write a launch post full of adjectives about it, because the release is mostly plumbing. The interesting part is not a new feature you can show in a screenshot. It is the stuff that keeps the app from annoying you later.

The updater actually works now

Mouzi checks for updates on its own and installs them with one click. It uses the signed Tauri updater, so each package is verified before it goes in. If you are on 0.1.5 or older, heads up: those builds never had the updater. So 0.1.6 is still a manual install for you. From 0.1.6 onward, future upgrades happen without you hunting GitHub for the installer.

I put this off for too long. A local-only app is easy to forget about once it is installed, and asking people to re-download every time was friction I should have removed earlier.

Deletions go to the bin

Two changes here, both about not losing your files by accident.

First, the button that said "Clean" now says "Organize." "Clean" implied deletion. Mouzi never deleted anything. It moves files between folders. The old label set the wrong expectation for a tool that touches real files, so I changed it.

Second, the remove action now sends files to the system Recycle Bin or Trash instead of erasing them. If a rule points at the wrong place, you get the files back. This should have been the default from the start.

Files without extensions

Mouzi now identifies a file by its contents, not just its name. A file with no extension gets sorted by what it actually is, then runs through your existing rules. Downloads from chat apps and some browsers often land without an extension, and until now they just sat there. That gap is closed.

Rules are easier to control

Each rule has its own on and off switch and a folder picker for the destination. No more editing a config file to move a rule somewhere. I also rebuilt the labels to be clearer and more accessible, because the old ones were vague even to me after a week away.

Two smaller things people will probably use:

• Per-rule extension normalization, so you can map jpeg to jpg and keep a photo folder consistent instead of letting it slowly rot into a pile of variants.
• Per-rule notifications with {file}, {rule}, and {destination} placeholders, so a toast can say "Moved report.pdf via Invoices to D:\Docs" instead of a generic "something moved."

In manual mode you can now select several files and organize them as a batch. Before this you went one at a time, which defeated the point the moment a folder had more than a couple of things in it.

The bug a user caught the same day

This is the part I wanted to write about, because it is a good example of why shipping in the open helps.

A few hours after 0.1.6 went out, someone opened issue #63 on GitHub. They were on Windows 11, in Settings > Rules, adding a rule. They left a trailing comma at the end of the extensions list, like exe, msi,. Mouzi then started matching files that had no extension at all.

The cause is what you would guess: the code splits the list on commas and treats each piece as an extension. The blank piece after the last comma becomes an "empty extension," and an extensionless file matches an empty extension. So the rule silently grabbed everything with no dot in its name.

The reporter suggested either showing a disclaimer or just ignoring the trailing comma. I will ignore it. Stripping empty entries when parsing the list is a one-line fix, and there is no reason to keep a blank token around. I will also make the parser drop whitespace-only entries, since exe, msi , with a space should behave the same as exe,msi.

What I liked about this report: it was specific. Exact menu path, exact input, exact behaviour. That is the difference between a bug I can fix in five minutes and a vague "rules are broken" message that takes an afternoon to reproduce. If you file a Mouzi issue, copy this one's format.

Windows signing, still pending

Same note as before for Windows users: the 0.1.6 builds are not Authenticode-signed yet. I am waiting on a production certificate from the SignPath Foundation. Until it lands, Windows shows a SmartScreen warning about an unknown publisher on first run. That is expected, not a sign the download is broken.

Get Mouzi only from mouzi.cc or the official GitHub repo. There is a SHA256SUMS.txt if you want to verify the files yourself. The in-app updater uses its own signature to check update packages, so updates stay protected even while the installer is not signed.

Where it goes next

Mouzi passed 800 stars on GitHub last week. For a tool that does something this ordinary, that still surprises me. The next few versions are less about new features and more about making the existing ones feel solid: fewer edge cases with weird filenames, better background reliability, and getting that certificate sorted so the Windows first run stops scaring people off.

If something breaks, the GitHub issue tracker is where I look first.

Download from mouzi.cc.