Inventory with sha256
Each .jsx, .vbs, .scpt, JSXBin and CEP panel, with versions that differ between workstations, hard-coded paths, dependencies and encoding.
Deliverable: inventario_scripts.csv for the team to decideOcto for JSX and UXP scripts in Illustrator
Illustrator runs scripts in JavaScript (ExtendScript), AppleScript and VBScript, and Adobe has put UXP plugins and the end of CEP panels on its roadmap. Octo inventories what exists, writes scripts that are read-only by default, simulate before changing and never save over the original, and delivers a report to whoever approves the artwork, the copy and the proof.
Six possible deliverables, taken from the survey. All of them log what they did, none writes over the original, and the decision on each script stays with whoever owns the automation.
Each .jsx, .vbs, .scpt, JSXBin and CEP panel, with versions that differ between workstations, hard-coded paths, dependencies and encoding.
Deliverable: inventario_scripts.csv for the team to decideExternal JSX warning turned off, passwords in the code, unguarded save() and dialogs silenced and never restored.
Only what is approved goes to the scripts folder; identical files are not copied, different ones become a conflict, and everything is logged.
Deliverable: instalar_scripts.sh and instalacao.csvColor mode, artboards, fonts, missing links and spot colors of each .ai, closed without saving.
Deliverable: auditoria_documento.jsx and auditoria.csvSimulation first, a report of longer text and missing translations, and one copy per language only when it is complete.
Deliverable: trocar_textos.jsx and relatorio_textos.csvEach panel's evalScript, window.cep and CSInterface calls, against the dates on Adobe's roadmap.
The same Octo cycle, applied to Illustrator scripts and panels. Each arm has a narrow role; the people approve the artwork, the copy and the delivery.
Scripts, panels, Illustrator versions, workstations and who wrote each thing.
Inventory with sha256, translation tables and audit summaries in versioned files.
JSX warning turned off, credentials in the code, a script that saves over the original, a forgotten Startup Script.
Action, script, variables or plugin, and what depends on the UXP roadmap dates.
Simulation before changing, a copy instead of saving over, dialogs restored at the end.
sha256 before and after, a line-by-line report, a file count. "It ran without errors" is not a check.
In each workstation's scripts folder, with simulation, a log and no overwriting.
What each script does, the minimum Illustrator version, who approved it and what changes with UXP.
Octo does not turn off the external script warning and does not save over the original. It does not approve artwork, translate legal copy without human review or decide what your team keeps.
The criteria Octo uses to choose between action, script and plugin, with each one's documented limit.
| Task | Path | Note |
|---|---|---|
| Repeat commands on a folder | Action and Batch | No code; see the actions and batch page |
| Read many files and log | JSX script | An action does not write a report |
| Decide by condition | JSX script | An action has no "if" |
| Replace copy from a spreadsheet | JSX script or variables | A script uses frame names; variables need a template |
| Drive Illustrator from outside | AppleScript or VBScript | macOS and Windows, respectively |
| Run something when the program opens | Startup Scripts (.jsx) | Also runs on every JavaScript run from the menu |
| Panel with buttons for the team | CEP today; UXP on the roadmap | UXP plugins in GA in Q4 2027 |
Three steps. Each one only makes sense after the previous one has shown results on your team.
A proposal, not a promise
Octo surveys what exists and points out what needs attention, without changing anything.
Read-only audit and copy replacement with simulation, installed with a log.
When the public beta comes out, Octo checks the Illustrator API against the panel map.
Each point below has a source published by the vendor, the project or the responsible body. The sources are in the next section.
4
points with a published source, each with its reference shown alongside.
Octo prepares everything, but it does not sign. The document of record stays with whoever is accountable for it.
Surveys, calculates, organizes and generates the documents: files, artboards, proofs and reports.
Deliverable: material ready to checkThe client or the art director checks what Octo delivered before approving. If something doesn't add up, it goes back to Octo with the correction.
Step: review by the approverOcto does not approve the artwork. Artwork carries no legal signature: approval of the artwork and the proof stays with the client or the art director.
Approval: client or art directorAdobe Help and developer pages and the scripting reference in the community guide that reproduces Adobe's content, consulted on Oct 31, 2026.
The assessment starts with an inventory of the script folders and panels that already exist. You get what differs, what carries risk, what depends on Adobe's roadmap and the questions only your team can answer, and you decide with that in hand.