Discourse AI Topic Summary 🤖

Sorry, last question on this: so if I want to deliver a better, more nuanced prompt to the LLM, I’m using “system.tagging” and not “prompt.tag”, correct?

You are best to change prompt.tag imho, but feel free to experiment.

Results with these prompts were so good from the get-go (with GPT 4) I’ve not really focussed or experimented much.

system.tagging might help you modify the “style” or “character” of the response (e.g. humorous or theatrical)

1 Like

I’ve been meaning to add this for a while, but the results from the Completions-based auto-tagging system were just too good to make it a priority.

But this morning I added auto-tagging based on Embeddings classification as an option:

There are various new settings, have a good look :eye:

Enjoy

Heads up, about 5 hours ago my site became inoperable due to a 500 error again. I had made no changes, using GPT 4. Could be that @RGJ pushed an update (but unlikely, since I didn’t see a note). Turned off the plugin, and the error resolved.

I’m not seeing any issues at present.

Could you please share the corresponding logged error and confirm the version of the plugin you have installed?

Only AI-related 500 error what I get, started yesterday, is (or was, I have not examined further yet) automatic alt. Why I didn’t start digging it deeper? Because error 500 comes really often from OpenAI.

It seems like the plugin on your site regressed to an older version somehow.:sob:

@ncaming215 My apologies, this is most likely our fault. I’ve put it back on 0.2.2 now and going to find out what went wrong. For now @merefield no need to worry.

2 Likes

Delighted to pass on this announcement from Open AI and confirm that AI Topic Summary options have been updated:

https://openai.com/index/gpt-4o-mini-advancing-cost-efficient-intelligence/

This is a big deal for AI Topic Summary, because this new model has:

  • 128k context (so can summarise lots of Posts!)
  • is 60% cheaper than the cost of GPT 3.5 Turbo!

Enjoy!

1 Like

Whoooops … there was some missing code I had forgotten to check in.

This is now resolved and I’ve improved logging at the same time:

thanks to @Jagster for raising the alarm.

1 Like

When I do the above-told, I get this error:

Those are instructions for the standard install.

Looks like you are trying to enter the database in the “web only” container? :thinking:

You may need to enter the data container instead in your case

The good news is that judging by this this may now be unnecessary (at least for tests-passed) as I believe core has finally upgraded the vector extension via their standard scripting, so you may only have to fully rebuild.

2 Likes

Yes. Thanks.
(Yes, I’m no 2 container setup. Yes I’m on Tests-Passed).

1 Like

Have added a thumbnail generation feature to this plugin.

Optionally it will depict the summary in an image it will automatically add to the top of the OP.

  • You must enable it in plugin settings
  • You can optionally elect to automatically delete the last top image each time
  • You can edit the prompt via the link in the plugin settings so you can influence the style and content (but this will be applied to all subsequently generated images)

Enjoy :framed_picture:

2 Likes

My locally hosted Chatbot is replacing the name of any topic in a link with the term slug

eg, an expected link is

https://localhost/t/title-of-the-topic-concerned/2341/5

but Chatbot is hyperlinking references with a URL such as:

https://localhost/t/slug/2341/5

I tried searching using the term slug but couldn’t glean anything except for a mention of slug in the settings: slug generation method which is set to the default, ascii

Thanks in advance for any insights!

Mine is using form as [Jagster](/t/-/11078/1). I don’t think that localhost changes that behaviour, but I don’t know it for sure.

But by Chatbot are you referring to the summary functionality of Discourse AI?

I’m sorry if I’m not using the right terminology. I have the Ai plugin enabled in a localhost instance and converse with it as @chatbot. Whether in a chat or in a topic reply, the responses are often linked to sources in topics elsewhere on the Discourse instance. Like this in a topic:
image
or this in a chat session:
image

In each case, the hyperlinked url is malformed as it replaces the topic name with slug

I asked only because out there is this too:

With that we can change prompts. But when using Discourse AI we can’t change the prompt of summary (at the monent).

The summary of DAI creates links right here, though. That’s why you need some more pro than I am ever. Because your issues may come from outdated plugin or localhost install, and someone who really knows what is going on is needed.

Hello! :wave:

Neither Chatbot nor this plugin are really designed to provide accurate links when running in local dev.

The target for functionality is always Production though of course it’s a bonus when you can test in dev.

I absolutely would accept a good PR if you were to submit one that improved support for localhost links.

1 Like

Doesn’t the link work like this? I would expect it to work the same way as the one with the topic title, because Discourse relies on the topic id.

2 Likes

Might not work as missing the port number.

2 Likes