How Mochi works
From messy folder to clear system.
Mochi’s workflow is deliberately small: authorize a location, describe where files belong, inspect anything uncertain, and keep control of every move.
1. Choose a folder
Add Downloads, Desktop, or another folder from inside Mochi. macOS asks you to approve access. Mochi watches only folders you select, and you can remove that access later.
Start with a folder whose contents you understand. Mochi stores the permission as a security-scoped bookmark on your Mac; choosing one folder does not grant access to unrelated locations. You remain free to organize different folders with different rules.
2. Start with a rule
Use a preset or make a rule that matches your workflow. For example, move .dmg and .pkg files into Installers, route documents containing “invoice” to Finance, or collect screenshots in one folder.
Good first rules have an obvious match and a single destination. Give each rule a clear name, keep it in review mode, and run it against a small set of files. When a rule is too broad, add another condition rather than depending on manual corrections later.
3. Preview the result
Mochi shows proposed moves before uncertain files change location. Local rules explain why they matched. Optional AI suggestions include a destination from the limited set you configured, but AI cannot move files on its own.
The review queue separates a suggestion from an operation. You can approve, reject, or revisit the rule. If two rules could apply or a destination is unavailable, Mochi favors a visible decision over an invisible guess.
4. Approve, review, and undo
Approve the queue when it looks right. Completed moves appear in history so you can trace what happened and undo eligible operations. Mochi never silently overwrites an existing file.
Undo checks the filesystem again before acting. If the original location is no longer safe, the app does not force the move. This makes history useful for recovery without pretending the surrounding filesystem has stayed frozen.
What happens when AI is enabled?
Ordinary rules still run first. Only an unplaced file is prepared for classification. Mochi builds a limited description, redacts common personal patterns locally, and asks the configured provider to choose from your allowed destinations. The response returns to the client for validation and review.
You can use provider credentials stored in macOS Keychain or keep classification local with Ollama. Complete files are not uploaded, and a provider does not receive absolute filesystem paths or the authority to perform a move. Read the privacy policy and evaluation methodology before enabling it.
A practical first setup
Create an Installers folder inside Downloads. Add Downloads to Mochi, make a rule for DMG and PKG extensions, and leave review on. Place a test file in Downloads, inspect the proposed destination, approve it, and then use History to undo the move. That single loop exercises permissions, matching, review, operation logging, and recovery.
After the result is predictable, add a second narrow rule such as screenshots by filename. Avoid enabling a large collection of overlapping presets at once. A small understandable system is easier to trust and maintain.
Start safely
Begin with one folder and a narrow rule. Run in review mode until the results match your expectations, then expand gradually. No account and no AI are required. The feature guide explains each control, and the help page covers installation and troubleshooting.
Keep the system understandable
Review rules when folder names or work habits change, and keep your important folders backed up. Mochi reduces repetitive sorting while leaving the filing policy visible and editable.