Yo, so Claude's getting integrated into Adobe and Blender now? Looks like creative software is about to start a plugin war.

Now that Claude can hook into Adobe and Blender, my first reaction wasn’t excitement but curiosity: who’s gonna define the standard for this plugin layer? Stuffing AI assistants into creative software isn’t new, but connecting to a big model means it can actually understand the scene you built in Blender, tweak things layer by layer in Photoshop—that’s a whole different level of interaction depth.

The thing is, Adobe has its own Firefly, Autodesk is cooking something too, so when third-party models come in, are they filling a gap or muscling in on turf?

What worries me more is the switching cost—once your workflow gets deeply tied to one company’s plugin ecosystem, switching is gonna hurt. Short-term it’s good, tools get smarter, but long-term evolution depends on whether these companies are willing to open up their APIs.

Who gets to set the plugin layer standard? That’s a good question. Right now everyone wants to call the shots themselves.

The part about switching costs hit me the hardest. Once your workflow is locked into one platform, migrating is a real pain.

Being able to edit down through PS layers like that, the interaction depth is really on another level. Way better than the previous assistants.

Short term, tools getting smarter is a good thing. Long term, it all depends on whether the companies are willing to open up their APIs.