AutoLauncher, developed by herm1t, is a sequential application launcher that opens multiple programs from a user-defined list. The tool processes valid entries in order and displays progress through a WPF interface, while application paths and settings are stored in a JSON configuration file. Individual entries can include command-line arguments, administrator privileges, custom icons, and wait behavior. It suits desktop users who want a repeatable startup routine without the complexity of a broader automation platform.

A launch list with rules for each app

The app reads a configured list of programs and starts each valid entry from top to bottom. Users manage the list through a JSON file rather than a visual editor, which gives experienced users direct control but makes setup less approachable for beginners. Available options include custom command-line arguments, administrator privileges, assigned icons, and wait-for-exit settings for individual applications.

The queue can pause until a task closes

AutoLauncher can wait for a selected process to exit before continuing, followed by a configurable delay before the next launch. Regular entries still open one after another without checking whether each application has finished initializing. This behavior supports workflows where one program must close before another begins, but it does not guarantee lower CPU or memory use. Users needing scheduled launch times or fixed pauses between every entry require a more advanced automation tool.

Focused controls keep the setup manageable

The utility includes progress tracking, diagnostic logs, theme options, an always-on-top mode, and the ability to cancel an active sequence with the Escape key. Invalid entries are skipped rather than stopping the entire queue, which helps users identify configuration problems without losing the rest of the launch routine. Its single-purpose design keeps operation straightforward, although it lacks remote management, detailed scheduling, and the wider controls found in full automation platforms.

A capable launcher that stays in its lane

AutoLauncher fits users who want applications opened in a consistent order and are comfortable editing a configuration file. Its per-app arguments, administrator controls, wait behavior, and error logging provide useful flexibility for personal desktop workflows. However, the JSON-based setup is less convenient than a graphical list editor, and its narrow feature set cannot replace a dedicated task scheduler. It remains a practical option for repeatable launches rather than a complete system automation solution.