An AI conversation can become a place to work, not just a place to ask questions. But opening an app inside a chat and allowing an agent to edit a native project are different changes. For a creative team, the useful question is where the finished work can be checked, revised and handed over.
The Breakdown
Claude’s interactive connectors can display apps inside a conversation. Its newer side-panel, full-site and pinning experience is rolling out on the web and Desktop to accounts with the new experience, not yet on mobile. That is narrower than the availability of existing interactive connectors.
The connector developer determines which views and actions are available. Users authenticate the connection; it uses the permissions already granted, and the normal action-approval process still applies. Seeing a familiar app in the interface does not mean every feature or action is supported.
Adobe’s November 10 announcement describes a different route. It previewed local MCP integrations through which third-party agents could work in Photoshop, Illustrator, Premiere and After Effects while keeping native project files editable. MCP is a protocol for connecting AI systems to tools. The local integrations are planned for a private beta in early 2027, not general use today.
That preview is separate from Adobe’s own Creative Agent assistants, announced in beta across its flagship desktop applications. The Photoshop assistant is in the Photoshop beta app. A beta available in one product should not be mistaken for availability of the entire proposed workflow.
Why This Matters
Consider an Indian agency preparing a campaign for a retail client. This is an illustrative workflow, not a reported customer case. A designer may need to change a price, produce several language versions and pass the artwork to another person for final approval. A polished preview is only part of that job.
The handover needs the correct wording, usable files, agreed dimensions and a clear version history. If the next designer cannot revise the result without starting again, the apparent convenience of the first step may simply shift work downstream. Conversely, a familiar interface is valuable only if the required action actually works in that account.
The Big Picture
Teams evaluating these tools should separate four checks: whether access is available now; what the connection is allowed to do; where the output is saved; and who approves it before a client or customer sees it. Those checks are more useful than treating every announcement as a complete replacement for the existing production process.
Start with a copy of a non-sensitive project, define an acceptable result and test the handover as well as the edit. Measure the time spent correcting and reviewing, not just the time taken to generate the first version. Neither announcement establishes a productivity gain for Indian teams, a staffing outcome or a guarantee that the finished work will meet a client’s requirements.
The Crunch
The practical test is not whether AI can display a creative tool. It is whether the team can safely complete, inspect and continue the work it actually needs to deliver.
Related categories: People & Work; Business & Brands
Leave your thoughts