feat: add share button

[celeriev]

Latest change:

Screen.Recording.2025-05-12.at.13.42.55.mov

History:
3ff1de9

Screen.Recording.Mar.25.2025.mov

[celeriev]

Hi @willydouhard, I started working on this idea of a sharing thread feature, but I'd love to get your guidance. I know you've been considering this feature for a while. I'm curious if you've already thought of the best way to handle this backend-wise.

[willydouhard]

Thank you for this contribution, it looks great! I added a few comments

[willydouhard]

i don't think we need this line

[celeriev]

I cannot make it work without actually. I may be missing something

[celeriev]

hello! I was in offline, but I'm taking this back this week

[sanchezedgar]

Excited about this!

Internally, we've implemented a basic approach for sharing threads using a ?thread_id query param in the start_chat handler. One feature we've appreciated is the ability to include a "header" and "footer" message for shared threads. The header thread includes the original author info. Would this solution support something similar? For instance, could we check if a thread is shared in an on_chat_resume handler and append/prepend header/footer messages accordingly? I reviewed the PR but am not yet familiar enough with the Chainlit source to determine if this is possible.

[celeriev]

Thanks for the feedback @sanchezedgar , I believe we could, yes, I like the header Idea. Let me start by tackling the first blocking points for the PR and we can work on this as well

[mkay1375]

Thanks for the PR! I have a couple of questions:

1. Do you have an estimate for when this will be completed?
2. Would it be possible to copy the shared chat to another (possibly temporary) table at the moment it’s shared, and then create a new thread from that when someone opens the share link? That way, any future updates by the original user wouldn’t be visible to others viewing the shared link.

[celeriev]

@willydouhard I wonder if it doesn't raise more complexity actually, since one user could share a thread using a specific profile and the end user loading this shared thread might not have permissions for that profile. I imagine this could lead to unexpected failures

[claude89757]

Hi, thanks for your PR ❤️

Really looking forward to this feature!

[hayescode]

@celeriev thanks for the work on this much needed PR. Is this good to go from your perspective? If so please mark it ready for review.

[github-actions]

This PR is stale because it has been open for 14 days with no activity.

[hayescode]

@celeriev if you're up for it I think we're ready for this. This is a highly desirable feature and you e done a great job with it. Do you plan on finishing this?

[celeriev]

hello @hayescode , unfortunately, I believe it is not yet fully tested, but I would welcome anyone to take it from there. My main concern would be the way this feature would act with active chat profiles, in case the receiver of the shared thread doesn't have access to the chat profile used by the user owning the shared thread.