Mats Linder 

Indeed, we have added a bit of confusion as we were very quick to provide a solution as a plugin (AI Professional) and then as we realised there was a better solution to ensuring we could make AI a longer term and well integrated solution it became two things:

• Trados Copilot - AI Assistant
• AI providers (similar to an MT provider) that would be able to work with the Trados Copilot - AI Assistant

If you have Trados Studio 2024, which is the version you need to be able to take advantage of this, you should note that Trados Copilot AI Assistant and the first AI provider (OpenAI Provider for Trados) are actually pre-installed. 

You are half right in that one requires the other, but you have it the wrong way around.  The idea is that Trados Copilot - AI Assistant will be part of the Trados Studio core product.  On its own it's useless as it will need an AI provider to be able to provide results.  So on the appstore you will be able to find AI providers of your choice (in time) that will deliver the AI to use within the AI Assistant and also as an alternative to an MT provider like Language Weaver or DeepL... or even alongside these MT providers so you can take advantage of your own terminology in MultiTerm for example.

I thought I'd just ramble a little for 5 mins and it might be helpful for you:

Let me know if you still have some questions after that?

Thanks! I knew most of this but am grateful for the suggestions as to find even more documentation texts than I had discovered (I think).

What confused me was that the plugin was provided with the new Studio 2024 installation. In order to write the manual about the "clean" version, I uninstalled the plugin (all plugins) that I had installed, so that the user interface would represent what a new user sees. And then, as you say, the AI Assistant also disappeared. Which is why I thought that I had to first install the plugin in order to see the Assistant.

So do you mean that a user of the pristine Studio 2024 will find, upon opening the list of installed plugins, that the OpenAI provider for Trados is there (and I suppose, no others)?

Am I correct in understanding it thus: 

- The AI Assistant is part of Studio.

- For it to work, you need an LLM provider. So far only OpenAI Provider for Trados is available, providing OpenAI and Azure. In future, more will come.

Because the Assistant is useless without an LLM provider, it is disabled if OpenAI Provider for Trados is not installed. 

But why? Why not keep it, always, and provide it with a text saying it requires an LLM provider (and suggesting available plugin[s])?

BTW, why not just call the plugins OpenAI/Azure LLM provider, X LLM provider, Y LLM provider, etc. The "for Trados" seems superfluous in the context.

Mats Linder 

Mats Linder said:

- The AI Assistant is part of Studio.

It will be.  Right now it's part of the plugin as I explained.

Mats Linder said:

- For it to work, you need an LLM provider. So far only OpenAI Provider for Trados is available, providing OpenAI and Azure. In future, more will come.

Correct.

Mats Linder said:

Because the Assistant is useless without an LLM provider, it is disabled if OpenAI Provider for Trados is not installed. 

It's not disabled... right now it'll be completely missing!  As I explained, right now it's part of the plugin.  We have separated it, but we need the Core Studio Team to adopt it into a future release.  Once that happens it will always be there, just not usable without an AI provider (a source for the LLM).

Mats Linder said:

But why? Why not keep it, always, and provide it with a text saying it requires an LLM provider (and suggesting available plugin[s])?

Exactly.

Mats Linder said:

BTW, why not just call the plugins OpenAI/Azure LLM provider, X LLM provider, Y LLM provider, etc. The "for Trados" seems superfluous in the context.

Many discussions about that one and this is the name that was agreed amongst a wide range of stakeholders.

Mats Linder 

Mats Linder said:

So do you mean that a user of the pristine Studio 2024 will find, upon opening the list of installed plugins, that the OpenAI provider for Trados is there (and I suppose, no others)?

Correct.

Also Language Weaver... that plugin is also pre-installed.

Thanks a lot for all this information!

But what is somewhat confusing is that, now that I have re-installed OpenAI provider for Trados, I can see that when I open the RWS AppStore window in Studio. However, when I open the Plug-ins window, the same plugin (I assume) is called Trados Copilot -- AI Assistant. What I would like to know is what this looked like in Studio from the start, before I tampered with it. Were they both included as system plugins and thus not present in the RWS AppStore window?

Also, the pre-installed Language Weaver plugin is called Language Weaver Machine Translation plugin which is not available in the AppStore. Evidently this is just one of the many system plugins which simply are there and nothing for the user to think about.

Mats Linder 

Mats Linder said:

However, when I open the Plug-ins window

I have never used that window for anything and wonder how many users go in there... but nonetheless....

Mats Linder said:

the same plugin (I assume) is called Trados Copilot -- AI Assistant.

In much the same way as you will see other plugins in that list that you have not installed yourself, this feature has been delivered with the installation of Trados Studio using the plugin framework.  For example, did you install the Bilingual Workbench Filter, the ITD Filter, the Tradostag Filter?  No you didn't.  So in this case we have delivered Trados Copilot - AI Assistant in the same way.  But because we have not yet don't this as part of the product we have one plugin for that and the OpenAI Provider for Trados... as I have explained several times now (clearly very badly!!).

So, let me try this:

• we have confused the hell out of everyone already with AI Professional, OpenAI Provider for Trados, Trados Copilot - AI Assistant
• we don't want to add to that confusion any more.  So we settled on the concept that we will only have OpenAI Provider for Trados (and in the future other AI providers for Trados) and the Trados Copilot - AI Assistant
• that is fairly simple to understand as a concept I hope?  But, as we have not yet separated these two within the product itself we are still delivering them both within one product.  That product is actually the OpenAI Provider for Trados plugin.  We don't want to call this the "OpenAI Provider for Trados AND Trados Copilot - AI Assistant plugin" so we named it in the plugins view you are looking at as "Trados Copilot - AI Assistant" since this is what users will see once we have separated it later... so no future confusion either.
• in the appstore we only have the "OpenAI Provider for Trados" because this is all users will see in the future as well.
• So whilst these are one and the same, they actually appear like two separate features as they will be going forward.  You only notice this fact when you look into a view such as the Plug-ins window.

Now I know some users may have used this view to deactivate plugins they didn't want to use, but that was a feature users could use if they really wanted to prior to the integrated appstore.  It's now so simple to remove plugins you don't want and put them back again later that there is probably no need to do that any more.

Mats Linder said:

Were they both included as system plugins and thus not present in the RWS AppStore window?

No, because there is only one plugin right now.  This may change in the future depending on how the AI Assistant part is delivered in the new world of AI Providers and a built in AI Assistant in the future.  It will either be only some "AI Provider for Trados" or some "AI Provider for Trados" AND "Trados Copilot - AI Assistant".  But we'll only know that when we deliver it.

Mats Linder said:

Also, the pre-installed Language Weaver plugin is called Language Weaver Machine Translation plugin which is not available in the AppStore. Evidently this is just one of the many system plugins which simply are there and nothing for the user to think about.

No, it is delivered as this:

You are looking at the system plugin because Language Weaver has always been there (since we had Language Weaver anyway) but accessed through Cloud-based Resources.  This was also another way we like to torture our users so they could never find the Language Weaver (that was available under cloud-based resources) until we added the link in the UI that just pointed them to the appstore and made them think even more they needed that app!

So now we deliver the app with the installer.  This means you now have the app, AND cloud-based resources so you have two ways to work with Language Weaver.

Sometimes I think our conversations would make a good episode of "Soap"... if you ever watched that TV series.  "Confused... you will be"!

Dear Paul, 

Do I detect a bit of frustration in your reply...? Anyway (and as you can see, I do not master the art of quoting the text part that I refer to):

- You did not explain the matter of OpenAI and Trados Copilot badly; I was just confused by the fact that the one is listed in Studio's RWS AppStore window while the other is listed in the Plug-ins window. I think I just have to accept this fact while certainly understanding the difference between them. (I understood that already after reading your first reply.)

- Am I correct in assuming that the Trados Copilot plugin originally appeared in the Plug-ins window as a system plugin? And the reason that it now appears (in my installation) as an added plugin is because I first uninstalled the OpenAI plugin (and thereby also the Copilot) and then re-installed it?

- As for the (less important) issue of the name of the Language Weaver plugin: thank you for this tounge-in-cheek explanation, which I could never have figured out myself.
(AIthough had already figured out the reason for a number of features being installed as system plugins even without your explanation.)

I did watch "Soap" when quite young, but since that was eons ago, I don't remember your quotation. But I do appreciate it! And now I shall hold my peace, with thanks.

Hi, 
I upgraded to Studio 2024 for the AI integration, but I am unable to get it to work, even after reading this. Could you please simplify it? Here are my questions:

Do I need to install the plugin? Or does it come pre-installed?

I have a subscription to ChatGPT 40, and can get an API key, but when I try to enter the information, I get stuck testing the connection. See screenshot:


I am not sure what I am doing wrong. The only reason I upgraded was for this functionality.

Tess Whitty 

Hi Tess, I think your problem is you don't have the right tier for billing.

Tess Whitty said:

I have a subscription to ChatGPT 40

This is irrelevant.  ChatGPT and the OpenAI platform you use for any CAT tool, or application working with the API, are different.

Tess Whitty said:

and can get an API key

Indeed... but it may not be an API key based on a Tier suitable for your requirements.  Check this link:

https://platform.openai.com/docs/guides/rate-limits?context=tier-free

Note that the Free Tier, which will get you an API key, doesn't support the use of the model you have tried to use.  You need at least Tier 1.  Perhaps this is the problem?