How to reset Proofreader settings

Hi, I was fixing my open router issues and changed to gwen and things were good.
Then I wanted to try to make a custom persona or have the prompt be geared towards pali language diacritic marks. I somehow removed proof-read from the context menu of the composer. gpt is making me go in circles.

Can someone help me?

Will this reset all the ai stuff?
cd /var/discourse
./launcher enter app
rails console
PluginStoreRow.where(plugin_name: “discourse-ai”).destroy_all
exit
./launcher rebuild app

I’m a big fan of reset and start all over, but i’m not trusting gpt+ on this suggestion and the ai plugin is now built-in for discourse and might operate differently.

Unless you really know how to fix this for me.. I’d rather reset. I’m going in circles.
Then I’ll try again to fix.

Can I suggest a simple mode for ai settings.. it is too intense.

i forgot to mention.. everything works if you give it a custom prompt. However, it is missing from the dropdown ai menu.

So the custom prompt of the AI helper still works, but the other options like “proofread” do not?

How is your AI helper configured? What do you see on the feature tab of the AI plugin?

3 Likes

Something was broken. No matter what I changed in the trust levels, it did not change after save. I tried rebuilding in the console and the web console kept disconnecting leaving the discourse rebuild unfinished. Then I had my “SOS-helper” help me and after he rebuilt it, everything was working as it should. I’m not sure what happened, but it is working now.

I’m not sure, but I noticed a bug when I wanted to past instructions into the custom ai prompt on the composer. Then it would only correct the instructions. It might be related. It would be common to want to paste instructions into the custom prompt.
I don’t need that since i have a persona now.

I appreciate your help.. something was odd.
My discourse was down for 1 hour but we are a small 300 member group with ~10-15% active, so it did not affect a huge number of users.

The solution was that there was some type of bug, now it is resolved from a rebuild.