On 24 September Adobe widened the way its applications can be reached from outside their own windows. Photoshop, Lightroom, Express and Firefly can now be called from a conversation in Gemini, and the Adobe plugin for Claude added Acrobat to the creative tools it already carried, more than 80 of them across Acrobat, Express, Photoshop, Illustrator, Premiere and Lightroom. Connectors for ChatGPT, Slack and Copilot were already in place. For anyone who prepares artwork and documents for a workshop the question is not whether this is clever, but which half of the week it can touch and which half it must not.
What actually changed
The Gemini side is raster and layout: retouching and colour on photographs, resizing one design into several formats while the branding stays put, filling in a template from a description. Illustrator is not on that list, so vector work sits outside it for now, and Adobe describes the Gemini integration as a first step.
The Claude side is broader and, for my kind of work, more interesting, because Acrobat is in it. You can also put your hands on the file inside the conversation now, editing a PDF or an Express layout directly instead of only describing the change and hoping the description was precise.
The useful half: documents and presentation material
Signage and fit-out run on PDFs: tender packs, drawing sets, product data, approvals, handover files. A good share of the unpaid hours in a project go on moving pages around, pulling the few sheets that concern my package out of a large set, merging a revision in, stripping a document down to what a fabricator needs to read. That is the sort of chore where describing the outcome is faster than clicking it and where a mistake shows up immediately and costs nothing to redo. The same holds for photographs that never reach a machine: site pictures cropped and levelled for a proposal, a visual set resized for three formats. Presentation material, in other words.
The half that stays in the application
Production artwork is not presentation material. A cut file is closer to a contract: brand colours named and broken down, letters as outlines, closed paths, cut lines separated from print lines, everything at 1:1. An assistant that re-renders a logo, resamples it, or nudges a colour because the result looks better on screen destroys precisely the properties the plotter and the router read. The rule I would apply is simple: anything that leaves for a machine is produced in the application, checked at full size against the drawing, and assistants only ever touch copies.
Accuracy is not the only reason. A prompt is not a record: six months later, when a panel is wrong and somebody asks why, what you can defend is the job file and the approved drawing, not a conversation.
Before a client's file goes into a chat window
Uploading a file means it leaves your machine for somebody else's service. An unbuilt shopfront, a floorplan with tenant names, a price list inside a tender PDF: none of that is yours to pass around because a tool makes it easy. That belongs in the contract and should be settled once, in writing.
Three things worth doing with this news: try it where an error is cheap and obvious, keep the production chain inside the application, and settle the confidentiality rule before the first upload. Artwork a sign shop can actually cut still comes out of the same careful pass, which is the work I describe under graphics and DTP.
