AI generated unread messages summaries

[marcoambrosini]

When we have a lot of unread messages in a conversation, it would be nice to have a short summary of them.

Expectation

A button that allows to generate summaries would appear next to the unread messages divider. Clicking it would start the action

An "info" badge would appear in the new message form, indicating that the task has started

And finally, when the summary is generated, it could look like this.

Warning

The summary box MUST contain a disclaimer that the summary is AI generated and can contain mistakes

[marcoambrosini]

Kickoff meeting happening on Monday 7/10

[nickvergessen]

• Takes in time range of 10+ seconds to multiple minutes
• Should be "prompted" but only done once the user requests it to save energy and time on AI
• Summary state should be shown near the chat (similar to OOO note?, or in topbar?)
• Once available the summary can be read in a popup and afterwards is deleted again

[nickvergessen]

Looks like a good place for the button and the summary.
Just have to keep in mind that we should generate the summary from the "button point" because the readmarker might have been updated already (we have visual vs another readmarker), so the UI needs to send the "since message" part to the API.

[nickvergessen]

• API ready in feat(chat): Add API to summarize chat messages #13661

[SystemKeeper]

When we have a lot of unread messages in a conversation, it would be nice to have a short summary of them.

Do we have a threshold or conditions for when to show the summary button or not?

It feels like a waste of resources having a summary for something like:

[nickvergessen]

It feels like a waste of resources having a summary for something like:

Yeah, definitely a threshhold. Not sure what we had discussed. I think 100+ floats around in my head.

[SystemKeeper]

This reminds me of nextcloud/talk-ios#1381, so might be more tricky than I thought ..

[marcoambrosini]

Could the threshold take into account the char count too? That way it would have a more accurate representation of the actual amount of text.

[nickvergessen]

If all messages have been loaded already, technically yes, but not sure what that does to client performance. If we want to avoid loading 2k or more messages in the future and show it on an "empty page" not anymore.

[SystemKeeper]

If all messages have been loaded already, technically yes, but not sure what that does to client performance

Would need to try it, if we stored the messages locally already on ios, it might work, but if we need to load all those messages first... But the unread message count is already available through the API endpoint, so that would be way easier.

[nickvergessen]

We could of course also do something like:

• Show if > 100 messages or
• if > 20 messages with more than 5.000 characters

[SystemKeeper]

Would that be checked on backend and exposed as an attributed or should we do it in clients?

[nickvergessen]

config => chat => summary-threshold (local) - Number of unread messages that should exist to show a "Generate summary" option

Added to capabilities for now

[SystemKeeper]

Some notes:

• The "Get task by id" is a "GET" instead of a "POST" as documented: Fix get task by id method documentation#12371
• Status seems to be a string instead of an int as documented: Fix get task by id method documentation#12371 (comment)
• Changing the provider might be inaccurate: [Bug]: Changing TaskProcessing selects wrong provider server#49335
• Make sure that cron is run to retrieve the results

[Antreesy]

Follow-ups:

• partially failing tasks
• store task status
• add copy to clipboard (instead of note to self)

[nickvergessen]

Overall done