Somebody in the campaign channel is asked to resize six approved hero images for three placements before end of day. That chore is what Adobe's own research keeps surfacing. Deepti Pradeep, the company's senior director for agentic AI, told TechCrunch that people using Adobe tools inside other apps reach for repeatable work such as batch-editing images and resizing creatives without leaving the app [8], and that focus groups described the value as "saving time, getting to the outcome they want faster without having to micromanage every step" [9]. The launch material aims higher, with a Slackbot that reads a project brief out of a channel and returns a PDF, an image or a video [10]. Both can be true at once, though it is the batch work, not the brief-to-video demo, that is more likely to keep the app installed by month three.
The tool count reads better as a spec than as a boast. More than 70 tools cover nine named applications [1], which works out at fewer than eight per app (70 divided by 9 is about 7.8) [15]. In practice, that means roughly eight verbs per app rather than a full Photoshop session in a chat window, and the published examples name most of them: removing backgrounds and distractions, adjusting lighting and tone, cropping, and producing variations [12], plus asset search across Creative Cloud by subject, style or mood [11].
The plan gate and the no-account path interact in a way the announcement leaves open. Neither writeup says where a file created inside a channel ends up, or whether output from a person who never signed in gets the same brand review as work leaving Illustrator [17]. That is the question the person who rolls this out will be asked on Friday, and neither source addresses it.
Adobe is not alone in treating the chat box as a distribution channel. Canva and Figma are exposing capabilities in ChatGPT and Claude, while Anthropic is building tighter Slack integrations on the argument that team context is captured in those conversations [13]. TechCrunch reports Adobe's own ChatGPT integration arrived only last month [7]. Pradeep's differentiator is breadth, that Adobe carries both creative and productivity tools across modalities [14]. For a buyer, that matters less than the structural point: as more chat clients plug into the same server, the client list starts to look like a footnote next to the server itself, which is where the real product now sits.
The work that benefits splits along two axes, and it is worth sorting your own tasks against them before enabling anything. First, whether the task follows a fixed recipe or needs judgement on a canvas. Second, whether the output leaves the building. Recipe work that stays internal, such as comps, deck visuals and resizes of already-approved art, is what a chat surface is genuinely good at. Judgement work, and anything a client or a regulator sees, still wants the app, a named owner and a file path. The metric worth logging in the first month is the share of chat-initiated assets that shipped without a rework pass, not simply a count of how many Slackbot calls fired, and whether the same people are still calling the tools in week four.
