Adobe will let AI agents edit native project files in early 2027

At Adobe MAX in Miami Beach on November 10, 2026, Adobe’s Creative Cloud announcement previewed local MCP integrations for Photoshop, Illustrator, Premiere and After Effects, with a private beta planned for early 2027. The proposed connections would let an outside AI agent change a native project file on the creator’s computer while keeping layers, vectors, bins and sequences editable.

Adobe’s own Creative Agent is already available through beta assistants inside several Creative Cloud products. The local connections for outside agents have a different timetable: Fast Company’s account names ChatGPT, Claude and Gemini as potential users of the integrations and quotes Adobe’s assurance that creators could “step in at any moment” to refine the work. The desktop applications would need to be installed and licensed for that local workflow.

Which features are available now?

The distinction is between tools creators can access in an Adobe app and a preview of access from an external agent. Adobe’s product rundown describes the in-app assistants as beta features and says the local MCP integrations are coming to Creative Cloud customers in early 2027. The announced release states break down as follows:

• Local MCP integrations — preview; private beta planned for early 2027. Photoshop, Illustrator, Premiere and After Effects are the named applications. This is the planned route for an external agent to work in local, native project files.
• Creative Agent AI Assistants — beta. The assistants are available in Premiere, Illustrator, InDesign, After Effects and Frame.io. Photoshop’s AI Assistant is available in the Photoshop beta app. They take instructions within Adobe’s products; their availability does not give outside agents the planned local access.
• Firefly Design and Firefly Graph — beta. Design brings raster, vector, motion, 3D and print work into one editing space. Graph connects AI models and Adobe tools in repeatable creative workflows.
• Firefly Builder — private beta. Builder turns a natural-language request into an interactive prototype, such as a website or app, whose elements can then be edited directly. Its private beta is already under way and is separate from the future MCP beta.
• Selected editing tools — general release or beta, depending on the feature. Premiere’s Color Mode is generally available, while Generative Remove remains in beta. InDesign Co-editing and Lightroom Open Eyes are also beta features.

That mix of labels matters for a production schedule. An available beta assistant can help with work inside its host application now, while the announced MCP preview describes how a preferred outside agent is expected to reach those desktop tools later. Firefly’s design and prototyping betas serve different tasks and do not move the local integration’s release date forward.

What can Adobe’s in-app agents handle?

Creative Agent’s beta assistants take natural-language requests in the context of the project already open in an Adobe product. In Premiere, announced examples include applying an effect across clips in a sequence, tracking a masked subject through a frame, and adjusting color or exposure across an entire sequence. The editor can then refine the result with Premiere’s usual controls. These are examples of the in-app assistant’s work, rather than a published command list for the future external-agent connection.

Illustrator, InDesign, After Effects and Frame.io extend that approach to their own kinds of creative work. A request has to operate on the objects and controls of its host product: a Premiere sequence, an Illustrator vector drawing and an InDesign layout are different project structures. The shared idea is delegation within an editable project, with the creator retaining the ability to make direct changes after an assistant acts.

Firefly Graph addresses repetition at a broader workflow level by combining models and production tools into a process that can be adjusted and reused. Firefly Design instead gathers different media types on one canvas for creation and review. Neither product’s beta label means that an external agent can already open and alter a local Photoshop or Premiere project through the previewed MCP integrations.

What stays editable after an outside agent acts?

The planned local connection changes where a task begins. A creator could give an instruction to an external agent, which would call on installed Adobe applications to make changes in the native files on that computer. The promise is consequential because a creator could continue editing the project’s constituent parts after the agent finishes, rather than receiving only a flattened image or rendered clip.

• Photoshop: Layers are among the project elements described as remaining editable, allowing image work to be refined within the file.
• Illustrator: Vector elements remain available for direct adjustment rather than being reduced to a finished image.
• Premiere: Bins and sequences remain editable, preserving the organization of source material and the structure of the cut.
• After Effects: The application is named for local MCP access, although the detailed announcement does not assign it a separate item in its list of layers, vectors, bins and sequences.

For example, the proposed workflow could carry a change to one campaign asset across related assets, then leave each result open to manual refinement. An external agent connected to other MCP-capable services could also retrieve a brief from Google Docs and share completed work through Slack. Those extra steps depend on the agent having access to those separate services; the Creative Cloud integration concerns the local editing of Adobe project files.

What the private beta will establish

Existing connections can already bring some Adobe functions into outside assistants, but the newly previewed local integration is aimed at deeper work in installed desktop applications and their native files. Its practical value will depend on the operations exposed in each app and how reliably the resulting project structures remain editable. A general list of every command available to an external agent has not been published.

The planned private beta in early 2027 is the next checkpoint. It should show which changes an outside agent can actually make across the named applications, and how much of a layered design or video edit a creator can still adjust directly afterward.

Also read:

• Canva AI or Adobe Firefly? The Finished-Asset Workflow Decides
• Airtable vs Smartsheet: Database Flexibility or Project Control?
• Microsoft Treats AI Agents as Insiders—Guardian Agents Watch Their Actions