=====================

Current Behavior:

=====================

Tool, model, and file/artifact settings within a chat do not reliably persist between sessions. For example, if Auto-Tool is enabled in a chat and the user navigates away and returns, the setting may revert to its previous state — or the inverse may occur. The same applies to other per-chat settings such as model selection and file/artifact configurations. Each return to a chat may require the user to re-verify and re-apply these settings before continuing work.

=====================

Desired Behavior:

=====================

Each chat should store its tool, model, and file/artifact settings as persistent variables tied to that specific chat. Whenever a setting is changed, the stored value is updated immediately. When a user returns to a chat, those settings are restored exactly as they were left — no manual re-application required. This should be consistent regardless of how much time has passed or how many other chats have been opened in between.

=====================

Use Case:

=====================

When working within a specific chat that has been configured with a particular model, tool set, or artifact context, it is disruptive to return to that chat and find those settings have reset. This creates unnecessary friction — especially for chats that are revisited frequently or are part of an ongoing workflow where the configuration is intentional and meaningful.

With persistent per-chat settings, a user could confidently leave and return to any chat knowing it will be in the exact state they left it, reducing setup overhead and preventing errors caused by working under the wrong model or toolset without realizing the settings changed.