Chat settings are shared across sessions instead of being session-specific

[touch2be]

Description

Chat settings currently persist across different sessions instead of being stored per session. For example, if one session is set to use GPT-5.4 with Build mode, switching to another session keeps the same settings.

If the model or mode is then changed in the second session, the original session is also changed. This makes working across multiple chats cumbersome, because each session cannot keep its own configuration.

Observed Behavior

• Session A is configured with a specific model and mode, for example GPT-5.4 and Build
• After switching to Session B, the same settings are still active
• Changing the model or mode in Session B also changes it for Session A
• This affects settings such as AI model selection and modes like Build or Plan

Expected Behavior

• Each chat session should keep its own settings independently
• Switching between sessions should restore the settings that were previously used in that session
• Changing the model or mode in one session should not affect any other session

Impact

• Makes it harder to work with multiple chats that serve different purposes
• Forces users to repeatedly reconfigure chats when switching contexts
• Creates confusion because session-specific behavior is expected, but settings behave globally

Environment

• OpenGUI Desktop Interface
• OS: Linux

[akemmanuel]

Next version includes a fix, thanks for the issue