The Scripts menu () accesses auxiliary scripts. Each menu item represents a file (or folder) in the Scripts folder.

Scripts to go in the Scripts menu should live in ~/Library/Application Support/Script Debugger 4.5/Scripts/. Alternatively, they can live in the top-level /Library/Application Support/Script Debugger 4.5/Scripts/. (A third possibility is that they can live in a folder called Scripts in the same folder as the Script Debugger application, but this option is for historical reasons and is not recommended.)

A file will appear as a menu item. A folder will appear as a hierarchical menu, and the files inside it will be its menu items. The name of a file (or folder) is the name that will appear in the menu, except that certain names or part-names are hidden and used for determining the order of the menu, as follows:

• If a name starts with the prefix ##), where ## is a two-digit number (00-99), these digits are used to determine the position of this item in the menu and the prefix does not appear in the menu item’s name.

• A name ##)-*** will appear as a menu separator, again with its order determined by the two-digit number ##.

Here are the actions you can perform with the menu items in the Scripts menu:

• Choose a menu item to run that script.
• Hold down the Option key while choosing a menu item to open that script file for editing.
• Hold down the Shift key while choosing a menu item to reveal the script file in the Finder.

Scripts to go in the Scripts menu may be AppleScript scripts (or scripts in some other OSA language, if you have any); they may also be shell scripts, applications, or Automator workflows.

A script in the Scripts menu can drive Script Debugger itself. Such a script does not need to include a tell block targeting Script Debugger; Script Debugger is implicitly the tell target.

You can debug a script in the Scripts menu, if it is an AppleScript script, by opening it in Script Debugger and putting it into debug mode. Now when you choose the script from the Scripts menu to run it, it will pause at a breakpoint if there is one.

If a script initiated from the Scripts menu takes a long time to execute, a progress dialog appears. This dialog contains a Stop button that you can use to abort the script if you think something has gone wrong (or if you just don’t feel like waiting — you cannot do anything else in Script Debugger while a script is running from the Scripts menu).