App Version: Adobe Illustrator 2026 (v30.x) OS: macOS Sequoia (15.x) Hardware: MacBook Pro (Apple Silicon)The Issue: Legacy CEP-based script launchers (specifically ScripshonTrees and LAScripts) have stopped functioning correctly. The panel frames and basic UI (search bars, buttons) render, but the actual list of scripts is entirely blank. Occasionally, the panels will gray out or fail to load entirely after a relaunch.What I have already tried (No success): Permissions: Granted Full Disk Access to Illustrator and toggled it off/on to refresh the TCC database. Rosetta: Forced Illustrator to run in Rosetta mode; panels remained blank. Caches: Nuked ~/Library/Caches/CSXS and ~/Library/Application Support/Adobe/CEP/CEF/ (including Local Storage). Developer Setup: Enabled PlayerDebugMode (1) for CSXS versions 11 through 16 via terminal. File Location: Relocated scripts from the root /Applications/ folder to a local /Documents/ folder to bypass Sequoia’s folder sandboxing. TCC Reset: Ran tccutil reset All "com.adobe.illustrator" to force a fresh permission handshake. Reinstallation: Completely uninstalled the extensions and reinstalled via ZXP/manual extraction. Diagnostic Observations: A very basic script launcher panel works, but full-featured CEP panels (which likely use Node.js to scan directories) fail to return any file list. The panels "partially" function (UI loads), suggesting the CEP engine is running but being blocked from host file system access despite Full Disk Access being granted. Is anyone else seeing this "Blank List" behavior on Sequoia? Is there a specific CEPHtmlEngine flag or a new macOS security prompt I’m missing that specifically blocks Node.js file system calls within CEP?

Inspiring

Question

Illustrator 2026 / macOS Sequoia: CEP Panels (ScripshonTrees/LAScripts) show UI but blank lists

Forum|Forum|1 month ago
February 19, 2026
3 replies
129 views

App Version: Adobe Illustrator 2026 (v30.x) OS: macOS Sequoia (15.x) Hardware: MacBook Pro (Apple Silicon)

The Issue: Legacy CEP-based script launchers (specifically ScripshonTrees and LAScripts) have stopped functioning correctly. The panel frames and basic UI (search bars, buttons) render, but the actual list of scripts is entirely blank. Occasionally, the panels will gray out or fail to load entirely after a relaunch.

What I have already tried (No success):

Permissions: Granted Full Disk Access to Illustrator and toggled it off/on to refresh the TCC database.
Rosetta: Forced Illustrator to run in Rosetta mode; panels remained blank.
Caches: Nuked ~/Library/Caches/CSXS and ~/Library/Application Support/Adobe/CEP/CEF/ (including Local Storage).
Developer Setup: Enabled PlayerDebugMode (1) for CSXS versions 11 through 16 via terminal.
File Location: Relocated scripts from the root /Applications/ folder to a local /Documents/ folder to bypass Sequoia’s folder sandboxing.
TCC Reset: Ran tccutil reset All "com.adobe.illustrator" to force a fresh permission handshake.
Reinstallation: Completely uninstalled the extensions and reinstalled via ZXP/manual extraction.

Diagnostic Observations:

A very basic script launcher panel works, but full-featured CEP panels (which likely use Node.js to scan directories) fail to return any file list.
The panels "partially" function (UI loads), suggesting the CEP engine is running but being blocked from host file system access despite Full Disk Access being granted.

Is anyone else seeing this "Blank List" behavior on Sequoia? Is there a specific CEPHtmlEngine flag or a new macOS security prompt I’m missing that specifically blocks Node.js file system calls within CEP?

cep

roseanglina221

Participant

This is likely a macOS Sequoia security restriction, not a panel bug. Sequoia is blocking CEP Node.js file system access, so the UI loads but the script list stays blank.

Full Disk Access isn’t enough anymore.

Quick fix to try:
Move your scripts into Illustrator’s default Scripts folder inside the app directory and relaunch.

Otherwise, it’s probably a CEP deprecation + macOS sandbox issue, meaning older panels may not fully work on Sequoia.

Max MugenAuthor

Inspiring

Yeah, I already tried all that.
Whenever the scripts are in Adobe directory or in my documents or something very simple, such as the desktop makes no difference.
What I don't understand is if it is the case that it is a macOS Secoya security, I don't understand why this has been auto resolved solved since then.I opened my full disk access and was not able to work with it for two days and then on day 3 it magically works.
So yeah, it's quite mysterious and I would like to know what's going on.

thx for the response tho :)

-- maxmugen.com

G

ge_dev33461420966j

Participant

Check this out I use it on macOS and I highly recommend it; it works perfectly.

https://exchange.adobe.com/apps/cc/200797?pluginId=200797&mv=product&mv2=accc

Habitual Media

Participant

He tenido el mismo problema y han sido las 48 horas más complejas al no encontrar solución de lectura en el arranque de la última actualización de Illustrator con macOS Tahoma 26.3 en M4 Apple Silicon. No sé qué hacer y espero ayuda pronto.

Max MugenAuthor

Inspiring

For me, it has magically fixed itself without me changing anything specific to it.
So I don't really know what's going on, but this has been very complex to work during the crash

As a coder enthusiast, I would like to understand what was the problem.

Was it coming from macOS and auth/file systems?
Was it coming from the backend / CEP of Adobe that changed things without noticing anyone?
Was it coming from the plugin itself ? (doubt it)
Or was it coming from the Chromium engine ?

If anyone has the technical expertise to know what's going on, please explain :)

-- maxmugen.com

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded