Switching user creates irrecoverable error

Describe the bug

If I accidentally do a few turns of a conversation with the wrong user account and try to switch it, I get unending Execution failed: 400 input item ID does not belong to this connection (Request ID: 00000-782d3778-5111-4f61-b546-ce63a4f73223) errors. I try restarting the session and it won't work. I think if I resume a session with wrong user and notice, I can rewind the conversation to before the "poisoned" message and it will stop giving the error. My guess is the issue stems from how messages are cached or something and it is user specific? Unfortunately, you make the user setup a huge pain and it's always using last user so I'm constantly running into this. You need to make it easier to control users (e.g. let me set default user or resolve user before blazing a new trail ahead or allow command line to specify user) and to recover if I accidentally use the wrong one for a bit.

Affected version

1.0.84-3

Steps to reproduce the behavior

1. Start a conversation as one user (e.g. personal) and send a message
2. Switch to another user (e.g. enterprise) and send another message

This consistently causes issues for me.

Expected behavior

• I should be given more control over how user is selected for a session especially through /config and --user options
• If I do use incorrect user for a bit, I should be able to switch the user and keeps working without any error. I'm ok if you have to do everything uncached whatever, just let me continue the conversation!

Additional context

No response

Start by reproducing the two-step account switch using the affected version, then inspect the session behavior around /config and the --user option. Done means switching users no longer produces repeated input-item ID errors and the conversation can continue or recover without restarting.