Skip to content
All AutoHotkey scripts under one process.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


Latest tested working version: AHK_L v1.1.29.01, DLL:

AutoHotkey Forum Thread

Are you tired of having to see tons of AHK scripts running in the processes list? I was. So, I made this: ScriptUp!


Easily add as many AHK scripts as you'd like, from any folder on your PC, and ScriptUp will house them all under its own process name. You can even compile it to have it run under a readable, separated process name!


  • When adding a script, you can choose between using the standard, full-featured DLL, and the mini version.
  • You can reload each script individually or all at once.
  • Drag and drop files to add multiple scripts at once.
  • When it starts up, all scripts in the list immediately run.
  • When a file is added, it immediately runs.
  • When a file is removed, it immediately stops the script.
  • As a setting, it can start up at user login.
  • Scripts may be paused and suspended.
  • Each script state is listed and actively updated.

Limitations and other notes

  • Scripts must be compliant with AutoHotkey_H (usually no or very few issues if it was written for AHK v1.1).
  • If you have "Start on User Login" active and move ScriptUp, it will automatically fix the registry entry (restart ScriptUp from the new path to do so).
  • When running as a compiled script, you must have a shortcut (.lnk) to "Lib" in the same folder as ScriptUp to allow access to the Standard Library.
  • If using an onExit sub/function in one of the added scripts, it must not exceed 30s of process time. If something requires more than that amount of time, set the value here.
  • Do NOT use any variation of #If except for #If. #IfWinActive, #IfWinExist, etc., will make the thread crash on exit. This is due to deprication in _H.
  • SetWorkingDir will be overridden. They will take on the working directory of the worker script, which is in the library. Full paths will need to be used in scripts.
  • With the release of v1, paths to scripts/DLLs may be relative to workerH. You can modify the path while adding a new script or change it in Lib\config.ini.

Dependencies (included)


If you'd like to contribute, fork, or make any personal edits, feel free to add your own name and link to the About section.

My only request is to keep my name and link in the About section. Other than that, have fun!



You can’t perform that action at this time.