Scope "Chat with groups" to library

[koppor]

Currently, the "Chat with groups" uses a "global" name of the group.

If two libraries share the group name, the wrong entries might be used.

Example

Steps to reproduce:

1. Create two libraries
2. Create entries in each library
3. Attach PDF files in each library
4. Enable AI https://docs.jabref.org/ai/preferences
5. Chat with a group
6. Switch to the other library
7. Start chat with a group with the same name

See that the chat from step 5 is shown.

---

NOTE: This issue shows that the contributor is willing to get familiar with JabRef from the pont of a user.

[SonarAkash]

Hi @koppor, I have successfully reproduced the issue locally. The chat history is indeed shared between libraries if the group name is identical. I am working on a fix now. Please assign this to me.

[jabref-machine]

👋 Hey @SonarAkash, looks like you’re eager to work on this issue — great! 🎉 It also looks like you don't know how to assign issues to yourself. Please read our CONTRIBUTING.md to find out how. It will also guide you in other aspects of contributing to JabRef.

[SonarAkash]

/assign-me

[jabref-machine]

👋 Hey @SonarAkash, thank you for your interest in this issue! 🎉

We're excited to have you on board. Start by exploring our Contributing guidelines, and set up your local development workspace by following the steps in our workspace setup guidelines to get started smoothly.

For questions on JabRef functionality, you can consult the JabRef Guru. For questions related to the codebase, please start using DeepWiki.

In case you encounter failing tests during development, please check our developer FAQs!

Still facing issues or having more questions? Feel free to ask here on GitHub or on JabRef's Gitter chat. Please don't hesitate to open a (draft) pull request early on to show the direction you are heading towards if unsure.

Happy coding! 🚀

[SonarAkash]

I am unassigning myself from this issue. Here is my investigation for the next person:

Root Cause: AiChatComponent.java initializes bibDatabaseContext and aiChatLogic as final fields in the constructor. Because the component persists when switching tabs, these fields never update, causing the chat to get stuck on the first library opened.

Attempted Fix: I tried refactoring the component to listen to stateManager.activeDatabaseProperty(). On change, it should update the local bibDatabaseContext, re-instantiate AiChatLogic, and cache the chat history.

Remaining Bug: I ran into collision issues where switching between two libraries with empty selections caused them to share the same chat history ID (e.g., both resolving to "NONE"). The getContextId method needs to include the library path/name to ensure uniqueness.

[koppor]

@SonarAkash Thank you for the investigation.

I think, the contextId is the id if a BibDatabaseContext? Then, this should be unique in a JabRef session; no need for a library path. Think of that saving a library to another path should keep the chats.