Inside AutoShelf: preview one local rule before expanding the automation
A 29 October Product Hunt launch and current maintainer pages show a small local file-automation boundary built around one rule, preview and explicit paid expansion.
AutoShelf 2.6 appeared #17 on Product Hunt's 29 October 2026 daily leaderboard with 81 points when checked 30 October. That dated signal is not market share, a final lifetime total or evidence of reliability.
Documented components, not a complete production inventory.
- Native sandboxed macOS menu-bar app
- Confirmed local application and distribution boundary
- Folder watcher + readable conditions and actions
- Confirmed rule engine; safety and performance not independently tested
- Live match preview
- Confirmed review step before activation; not a backup guarantee
- CLI + local MCP server
- Confirmed companion interfaces; write access is documented as off by default
A recent launch with a bounded popularity signal
Product Hunt's 29 October board lists AutoShelf 2.6 seventeenth with 81 points. The launch describes rules for filing, renaming, tagging, archiving and converting files on a Mac. FreeStack reviewed the dated launch, current product pages and App Store listing. We have not installed the app, watched a folder, inspected its binary, measured performance or verified a real file operation.
What the maintainer confirms
AutoShelf is a macOS menu-bar application distributed through the Mac App Store. The maintainer describes it as native and sandboxed, says rules execute on the Mac, and states there are no analytics, tracking or network calls. The current official site requires macOS 14 Sonoma or later and says the universal binary supports Apple Silicon and Intel. The App Store listing currently says macOS 13 or later, so FreeStack keeps the stricter site requirement rather than hiding the mismatch.
The documented product components
The app watches chosen folders, evaluates conditions and chains actions. Official pages name file type, extension, name, source URL, size, age, text and EXIF conditions, plus move, copy, rename, tag, trash, archive, image optimisation and media conversion actions. Live preview shows matches before activation. A companion CLI and local MCP server can manage rules; write access is off by default in the launch description. The maintainer does not disclose the programming language, storage format or internal renderer, so this study does not invent them.
The free boundary is part of the design
The provider's ongoing Free tier includes one fully functional rule, one watched folder and built-in templates. Pro adds unlimited rules and controls such as configuration import/export, confirmation, delayed execution and more complex conditions. A single-rule allowance can still teach whether the automation is safe and useful; it should not be described as unlimited free workflow software.
Try the smaller learning workflow
FreeStack suggestion, not AutoShelf's production stack: use the linked guide to write one rule card in VS Code, prepare twelve fictional files, preview and approve one AutoShelf rule, and keep text checkpoints in Git. Save the three-tool starter stack privately. The exercise teaches the decision boundary without claiming a tested customer result or reproducing the app.
Where payment becomes justified
Pay when a second active rule, multiple watched folders, import/export, confirmation gates, compound conditions or supported team policy solves a named repeated cost. Local automation still needs backups, permissions and recovery planning. A launch ranking and a long action list do not establish that the app is safe for a particular folder.
Sources & further reading
Follow the source for current details. Product Hunt is used for discovery and launch history; technical claims use provider documentation or the project repository.