📌 feat: Add Conversation Pin Feature with Drag & Drop Ordering (#2610)

[henricook]

Pin Conversations

Docs update: LibreChat-AI/docs#310

Summary

This feature was requested and was also something I'd personally really like. I'm sorry it's not on the roadmap but I took Danny's comment on the Issue as blessing enough and went ahead and did it.

• Option to pin chat conversations #2610

Please do let me know if I've done anything egregious and/or you'd like any changes!

Change Type

Please delete any irrelevant options.

• [ X ] New feature (non-breaking change which adds functionality)
• [ X ] This change requires a documentation update
• [ X ] Translation update

Testing

I've added unit tests and done a click test, here's a video of the original work:

Screencast.From.2025-05-25.11-06-19.mp4

After a helpful suggestion in comments by @rubentalstra I went back and added drag and drop reordering to pinned items too, here's a vid of that, there's a refresh in the middle to double-check persistence is fine (that's why the screen goes blank):

Screencast.From.2025-05-26.11-36-55.mp4

Test Configuration:

N/A

Checklist

Please delete any irrelevant options.

• [ X ] My code adheres to this project's style guidelines
• [ X ] I have performed a self-review of my own code
• [ X ] I have commented in any complex areas of my code
• [ X ] I have made pertinent documentation changes
• [ X ] My changes do not introduce new warnings
• [ X ] I have written tests demonstrating that my changes are effective or that my feature works
• [ X ] Local unit tests pass with my changes
• [ X ] Any changes dependent on mine have been merged and published in downstream modules.
• [ X ] A pull request for updating the documentation has been submitted.

[henricook]

Sorry I had some trouble reproducing the eslint failures locally, pushed now @danny-avila

[rubentalstra]

please have a look at the translation files. please only keep the en language keys.

[rubentalstra]

please have a look.

to make the code maybe less dependant on DateTime filtering. maybe using an int for PinnedOrder so it would be possible later maybe to re-order them if needed?

[rubentalstra]

@danny-avila or @berry-13 do we already use a different package for drag?

[danny-avila]

@rubentalstra yes we use react-dnd, it would be best to rely on this first rather than introduce another library

[henricook]

Apologies, i'd missed that, will draft and refactor!

[Copilot]

Pull Request Overview

This pull request adds a conversation‐pin feature with drag & drop reordering support. Key changes include updates to the data schemas and API endpoints for pinning conversations, modifications to the client-side conversation grouping to separate pinned items, and the introduction of new mutations and components to handle pin toggling and reordering.

Reviewed Changes

Copilot reviewed 16 out of 16 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/data-schemas/src/types/convo.ts	Added optional fields isPinned and pinnedOrder to the conversation type.
packages/data-schemas/src/schema/convo.ts	Updated the schema to include isPinned and pinnedOrder with appropriate defaults and indexes.
packages/data-provider/src/*	Extended types, API endpoints, and data service functions to support pin and reorder mutations.
client/src/utils/convos.ts	Modified conversation grouping to separate and sort pinned conversations.
client/src/components/Conversations/*	Introduced new components and mutations to support pin toggling and drag & drop reordering.
api/server/routes/convos.js and api/models/Conversation.js	Added routes and auto-assignment logic for pinnedOrder during pin/unpin operations.

Comments suppressed due to low confidence (2)

client/src/components/Conversations/PinnedConversations.tsx:108

• [nitpick] Consider renaming 'localPinnedOrder' to 'pinnedConversationsState' to more clearly indicate that it holds the local state for the order of pinned conversations.

const [localPinnedOrder, setLocalPinnedOrder] = useState<TConversation[]>([]);

api/models/Conversation.js:102

• Add a clarifying comment regarding the initialization logic for 'pinnedOrder', explaining that it assigns (maxOrder?.pinnedOrder ?? -1) + 1 to ensure new pins are ordered correctly even when no previous pinned conversations exist.

if (update.isPinned === true && update.pinnedOrder === undefined) {

[henricook]

@rubentalstra I've rebased and just assumed that this issue we noted is resolved, if you're able to trigger another build?

Note: This won't build on latest main due to the rollup build issue introduced in deb8a00e27251875d466c5a92b5d343b197fe0f5. I guess this'll get fixed upstream or by someone else, and then this PR can be rebased.

[henricook]

@danny-avila The only urgency I can assign to this is my excitement to use the feature myself in my production Librechat! Would you mind triggering the build please? 🤞🏻

[marwanasker]

Im someone looking into getting this merged?

[henricook]

I didn't want to keep @ing people to be honest, it was feeling like I was harassing. I'm not sure how to proceed. I'll take a look at the conflicts again by Friday night and push it in the hope someone gets the time.

Danny's probably busy being inducted at Clickhouse this week? :-D

[henricook]

Now rebased and ready for merge again

[henricook]

Thanks for triggering the rerun @rubentalstra - hopefully Clickhouse sponsorship leads to normal automatic pipelines, I feel bad putting you out asking you to run pipelines all the time. I think i've now fixed the unit tests 🙏🏻

[henricook]

Le sigh, these test failures look to be present on main. I can see that token split is approached in #10567 but I don't see anything for the Windows VirtualScrolling flake, maybe just retry after 10567 is in?

[henricook]

I'm afraid I'm being totally stonewalled on this everyone. No one with merge rights from Librechat is engaging and maintaining this PR through merge conflicts is becoming quite a chore.

I'm really disappointed but I'm going to close this PR. If anyone thinks they've got the ear of a Librechat merger please get in touch and i'll gladly reopen it, but I can't keep resolving conflicts and crossing my fingers that they'll get around to it with no communication.

[jmaddington]

@henricook Thank you for your work on this. We merged it into our forks (one public, one private) awhile ago and it's worked great.