Weird error message about Assistant plugin version mismatch after every update.

Problem

Over the last 2 or 3 updates, I’m getting this weird error message about the Assistant plugin version being mismatched or something. The actual text of the error is as follows:

19:05:13.352 Assistant plugin version changed from 09b2c7f to c9bc409. This may cause instability when using Assistant or the MCP server. Please restart Roblox Studio to fix. - Edit

Now I restart Studio to fix it as the message suggests, and it does fix it…until the next update.


Additional Information

Parameter Value
Problem Area Studio
Problem Component Builtin Plugins?
First Noticed 10 June 2026
Priority Normal
Impact Low
Annoyance Level Meh…
Platform Windows 10 Pro RTM 64-bit

The beta features that I have enabled are as follows:

  • 3D Importer in ACE
  • Assistant Mesh Generation
  • glTF Export
  • Multiline Command Bar
  • Texture Generator
  • Universal Importer

As for plugins, I have a bunch that are installed, but very few are enabled. The ones that are enabled are listed below with links to their details page on the Roblox store website:


Expectations

What I expect to happen is that there is no warning/error message after an update.


Visuals


Reproduction

To reproduce the issue, perform the following steps:

  1. Update Studio.
  2. Open Studio.
  3. Observe message in output window.

NOTE: I have a place open when I click on the blue Update button in the upper right area of the quick access bar.


Files

4 Likes

It’s happening to me as well, I’m getting a client and server warning with the same message:

This is what shows for me when opening the AI assistant:

As of writing this, after closing and reopening Roblox Studio it got fixed.

Try opening the AI assistant using this button


and then closing and reopening Roblox Studio, I believe that’s how I fixed it

I know that’s how the issue is fixed. What I’m reporting is that the issue is happening in the first place. It’s a minor annoyance, but it is happening which is why I reported it. And now we know it’s happening to more than one person.

Also, I don’t really use the AI Assistant so it’s not really a show stopper for me anyways.

1 Like

I’m also getting the same error.