Prismatic Software Editorial Team
Adobe used its MAX 2026 conference in Miami Beach on November 10 to roll two new AI-driven adjustments out of beta in Photoshop — Relight and Generative Restyle — alongside updates to Lightroom, the Remove tool, and text-layer recovery (DPReview). In the same announcement, Adobe said it is previewing local Model Context Protocol (MCP) integrations that would let third-party AI agents work directly inside native Creative Cloud project files (9to5Mac).
Letting an outside AI tool reach into a professional application's native project structure without flattening layers into static output is exactly the kind of narrow, high-risk integration a vendor validates as a standalone prototype first — the sort of scoped build an ISV typically runs past a GenAI integration team like YuSMP Group's before committing engineering months to a full agent-access layer.
What Adobe shipped at MAX 2026
The headline Photoshop additions are Relight, which lets a user add up to three virtual lights to a composition after the fact with controls over position, color and intensity, and Generative Restyle, a prompt-driven full-image transformation with sliders to move between variations — both live on editable layers rather than baking changes into the pixels (DPReview). Adobe also shipped a simplified, prompt-based AI Assisted Editor, a Remove tool update that now clears reflections, water ripples, dust and fog alongside selected objects, and a Convert to Text Layers feature that turns flattened text back into editable layers. Lightroom picks up a Glow effect ported from Camera Raw, one-tap Blemish Removal, and improved camera tethering for studio workflows.
None of that is unusual for an annual Creative Cloud update cycle — it's the kind of incremental AI feature set most desktop imaging vendors are shipping this year. The part worth watching is what Adobe previewed alongside it.
MCP: letting outside agents into native project files
Adobe confirmed it is building local MCP support into Photoshop, Illustrator, Premiere, and After Effects, with a private beta planned for early 2027 (9to5Mac). The pitch: a user could connect an outside AI agent — Adobe's own example was ChatGPT — to Photoshop, ask it to make an edit, generate assets, post an update to a team's Slack channel, or file results to Google Drive, while the layers, vectors, bins, and sequences inside the native project file stay fully editable the whole time (DPReview).
That last detail is the actual news. Most AI edit integrations today round-trip through a flattened export: an agent gets a rendered image, works on it, and hands back a new static file that has to be re-imported and rebuilt into layers by hand. Adobe is describing something narrower and harder — an agent that reads and writes the project's internal structure directly, because the whole workflow runs locally on the user's machine rather than through a cloud render step.
Why native-file agent access is the harder build
A chat-based AI feature that edits a flattened copy of an image is a contained problem: take pixels in, return pixels out. An agent that has to understand and safely modify a live project file — which layer is a mask, which group is locked, which vector path an edit shouldn't touch — is an entirely different scope of integration work, closer to building a structured API into an application's internal document model than to adding a filter.
That's also why Adobe is calling this a preview with a private beta still months out rather than a shipping feature: getting agent-to-file access right on a document format as layered and stateful as a .psd or a Premiere project is the kind of integration most software teams prototype narrowly first, with a defined scope and a small set of agent actions, before opening it up to arbitrary third-party tools. Shipping that access prematurely risks an agent silently corrupting layer state in ways that only surface after a user has already saved over their working file.
The bottom line
The Photoshop 2027 feature list is a normal annual AI refresh; the MCP preview is the part that changes the shape of the product. If Adobe ships local agent access to native project files in 2027, it sets a precedent other desktop imaging vendors will be asked to match — and the hard part won't be the AI model doing the edit, it'll be the integration layer that lets an outside agent touch a project file safely.
