PluginInstaller Scripts Panel

A panel that lists your Adobe scripts in a collapsible tree and runs them, in the style of the built-in InDesign Scripts panel — but also available in Adobe Illustrator, Adobe Photoshop, Adobe After Effects and Adobe InCopy.

It ships as the free PluginInstaller Scripts Panel package. There is no licensing and no activation. Its menu entry may read “Scripts (managed by PluginInstaller)”.

  • CEP version — Illustrator, After Effects, InDesign, InCopy.

  • UXP version — Photoshop (separate package). Photoshop dropped support for CEP, so this is its replacement for that one host; feature-matched to the CEP panel.

Getting it

Install it with the PluginInstaller application:

  1. Launch PluginInstaller. First time you will need to create an account and register. Follow the instructions from the web page.

  2. Find PluginInstaller Scripts Panel in the “Featured” software list. There are two versions (Photoshop vs other apps). Install either or both.

  3. Install it, then open the panel from the host app’s Window › Extensions (CEP) or Plugins (UXP) menu.

  4. If you use the Photoshop version, you must enable and start the PluginInstaller Daemon from the PluginInstaller preferences screen.

The tree

The panel shows one or more root folders. Everything starts collapsed. Expanding a disclosure triangle re-reads that folder from disk, so the tree refreshes as you browse; folders you have open stay open across a refresh. Symlinks and classic macOS alias files are followed.

Root What it is
Application Scripts folder that ships with the host app.
Documents ~/Documents/Adobe Scripts/<AppName>/ — created automatically. Put your own scripts here.
Community Machine-wide shared scripts folder (InDesign / InCopy).
User The host app’s per-user Scripts Panel folder (InDesign / InCopy).
(your own) Any folders you add in Script Settings.

InDesign and InCopy always show Application / Community / User even when the folder does not exist yet. Other apps show Application + Documents plus anything you add. You cannot delete a root from the panel, only its contents.

Running a script

  • Double-click a script, or select it and press Return.

  • Runnable types: .jsx, .jsxbin, .js, and UXPScript .idjs / .psjs where the host supports it.

  • Any other file is listed too; double-clicking it opens it in the OS.

Progress shows in the message strip at the bottom of the panel: Running
<name>…, then Ran <name> (or Ran <name> → <result>) or Error: <message>. Cancelling a script’s own dialog reports <name> cancelled, not an error.

To return a value to the panel, end the script with the value as an expression, exactly like the native Scripts menu:

var count = doTheWork();
count              // shown after "Ran <name> → "

Do not use a top-level return — ExtendScript rejects it. return can ony be used inside functions.

Run model — Illustrator / After Effects run in the app’s default ExtendScript engine via BridgeTalk; InDesign / InCopy run via app.doScript with undo integration. The Photoshop UXP panel needs the Tightener daemon running (PluginInstaller starts it: see PluginInstaller preferences screen); a .jsx / .js then executes in Photoshop’s own process the way File › Scripts does — alert / confirm / prompt and ScriptUI all work, and the return value comes back. Without the daemon the panel cannot run scripts and says so. A .psjs UXPScript runs by being opened, daemon or not.

Right-click menu

Item Applies to Action
New… folders Create a file or folder here — type the name including its extension.
Run scripts Run the script.
Edit files Open in your text editor.
Delete non-root items Move to the Trash / Recycle Bin, via a native confirm dialog.
Edit Tags… anything Assign tags — one per line.
Reveal in Finder / Explorer anything Show the item in the OS file browser.

Filtering and tags

A bar at the bottom of the panel narrows the tree.

  • Filter field — type words separated by spaces; they combine with AND against the row name. A matching folder brings its contents with it.

  • Tags ▾ — a popup of every tag in use. Tick one or more to show only items carrying any ticked tag (a tag on a folder counts for its whole subtree). Clear all unticks them.

The filter text and ticked tags combine with AND and are saved, so the panel reopens with the same filter active. Tags are stored in the panel’s prefs keyed by path, not in the files, so moving or renaming an item leaves its tags behind.

Adding your own folders and editor

Flyout menu (▾) → Script Settings:

  • Add extra root folders (display name + folder on disk). They appear as extra roots, shown even if the path is missing so you can spot a stale entry.

  • Editor program — full path to your editor’s launcher; Edit and New… then use it directly. Left empty, they fall back to an editFile hook in your net.tightener SysConfig folder, and ultimately to the OS default text editor.

The flyout also has Refresh (re-scan every root) and Tightener Daemon Settings.

macOS and Windows security prompts

The panel drives the operating system on your behalf — it launches the Tightener daemon, reads script folders, and (in Photoshop) tells the host app to run a script. The OS guards each of those, so the first time each one happens you get a security dialog. These are expected. You must allow them, or the panel cannot do its job. They are one-off: once granted, the OS remembers.

macOS

  • “PluginInstaller” / Adobe app wants access to control “Photoshop” (or “System Events”) — click OK. This is what lets a .jsx run in Photoshop’s own process. Denying it breaks script execution; you can re-grant it later under Privacy & Security › Automation.

  • “PluginInstaller” would like to access files in your Documents folder — click Allow. The panel needs this to see ~/Documents/Adobe Scripts/. Fixable afterwards under Privacy & Security › Files and Folders.

Windows

  • Windows protected your PC (SmartScreen) on first launch of PluginInstaller — click More info › Run anyway.

  • User Account Control — the screen dims to the secure desktop and asks “Do you want to allow this app to make changes to your device?” when the daemon or the installer needs administrator rights. Click Yes.

  • Your antivirus may hold or quarantine the download — allow / whitelist PluginInstaller if it does.

If you clicked Don’t Allow / No by mistake, quit the host app and PluginInstaller, re-open PluginInstaller, and redo the step (macOS: toggle the entry back on in System Settings › Privacy & Security).

Troubleshooting

Symptom Likely cause
Edit opens the wrong editor Update the settings in the panel and set the correct path to the editor
A root is missing Expected for InDesign / InCopy folders that do not exist yet; for your own folders, check the path in Script Settings.
Script “still running (stopped watching)” The panel stops watching after ~60 s; the script may still be running in the host.
New file/folder: “already exists” An item with that name is already in the folder. Rename or cancel.
Daemon not running Start the daemon by way of the PluginInstaller preferences.
Scripts won’t run in Photoshop, no error An Automation permission (macOS) was denied — re-enable it under System Settings › Privacy & Security › Automation.
Panel shows no scripts under Documents Files and Folders / Documents access was denied on macOS — re-enable it in Privacy & Security.

License and disclaimer

Copyright © 2024–2026 Rorohiko Ltd. All rights reserved.

PluginInstaller and the PluginInstaller Scripts Panel is proprietary software, licensed for use, not sold. It is distributed free of charge and is fully functional; it may not be reverse-engineered, decompiled, redistributed, or resold except as separately agreed in writing with Rorohiko Ltd.

Use at your own risk. This software is provided “as is”, without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose, and noninfringement. In no event shall Rorohiko Ltd. be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the software or the use or other dealings in the software.

The panel runs scripts you point it at, in your host application, with your privileges — exactly as the native Scripts menu does. You are responsible for the scripts you run. Only run scripts you trust, and keep your work saved and backed up. Rorohiko Ltd. is not responsible for data loss or damage caused by a script executed through the panel.

Support: https://www.rorohiko.com — [email protected]