Illustrator automation scripts: 2023 GPU Performance default creates headless compatibility boundary

Illustrator automation scripts: 2023 GPU Performance default creates headless compatibility boundary

Scripts that execute in a local Illustrator desktop session may fail when the same automation is moved to production build agents that run without an attached display or user session. Running ExtendScript automation for batch PDF and SVG exports inside a CI/CD pipeline requires a supported headless execution path.

Illustrator requires an active user session with a display server or interactive window station to initialize its UI subsystem, even when driven solely by scripts. Adobe does not provide a supported headless mode, server-side API, or Docker image for Illustrator as of the 2024 release cycle; InDesign Server is the official server-side vector alternative. The 2023 release enables GPU Performance by default, adding a compatibility boundary in virtualized environments lacking GPU passthrough. Workarounds such as Xvfb on Linux or Windows interactive services remain unsupported and break across OS and Illustrator upgrades.

Practical verification involves running a minimal ExtendScript on clean CI agents without a virtual display to characterize the failure, though symptoms vary by OS and version. Font licensing and activation state also differ between local and production machines, causing substitution that changes layout and export output.

The unresolved question is whether Adobe will ever provide a supported headless execution mode for Illustrator, or whether automation teams must permanently maintain fragile virtual-display configurations or migrate vector processing to alternative libraries such as Paper.js or Skia.

Is there any documented configuration for running Illustrator automation scripts in a headless CI/CD environment as of the 2024 release cycle? How should the 2023 GPU Performance default be handled on build agents without GPU passthrough? What migration boundary is appropriate when the interactive session requirement makes server-side Illustrator automation unsupported?