# Bug Report: Switching Between BYOK Configurations Does Not Always Update th...

# Bug Report: Switching Between BYOK Configurations Does Not Always Update the Actual Request

## Description

There appears to be an issue with switching between different BYOK configurations in Copilot App.

When I use one BYOK configuration (BYOK A), execute some tasks, and then switch to another BYOK configuration (BYOK B), the UI correctly shows that BYOK B is selected. However, the subsequent request is sometimes still sent through BYOK A.

This happens most frequently when editing an already-sent message, but I have also occasionally reproduced it when simply switching between BYOK configurations without editing a previous message.

In some cases, the issue can also cause the Copilot App to become unresponsive or appear to hang.

## Steps to Reproduce

1. Configure at least two BYOK configurations, for example:

* BYOK A
* BYOK B
2. Select BYOK A.
3. Execute several tasks using BYOK A.
4. Switch the selected BYOK configuration to BYOK B.
5. Verify that the UI shows BYOK B as the currently selected configuration.
6. Send another request.
7. Check which BYOK configuration is actually used for the request.

### Affected Scenario

The issue occurs particularly often when:

1. A message has already been sent.
2. The message is edited.
3. The BYOK configuration is changed from A to B.
4. The edited message is submitted.

## Actual Result

Although BYOK B is selected in the UI, the actual request may still be sent using BYOK A.

The behavior is inconsistent:

* It happens frequently when editing an already-sent message.
* It can occasionally happen when simply switching BYOK configurations.
* In some cases, the application becomes unresponsive after the incorrect BYOK configuration is used.

## Expected Result

Once the user switches from BYOK A to BYOK B, all subsequent requests should consistently use BYOK B.

The currently selected BYOK configuration in the UI should always match the configuration actually used for the request.

## Workaround

In most cases, restarting the Copilot App resolves the issue.

After restarting the application, the newly selected BYOK configuration is generally used correctly.

## Additional Information

The fact that restarting the application usually resolves the issue may indicate that some previous BYOK, session, or request state is not being refreshed correctly when switching configurations.

However, I cannot confirm the exact cause. The main issue is that the UI can show BYOK B as selected while the actual request is still routed through BYOK A.

---
| Field | Value |
| --- | --- |
| App version | 1.1.10 |
| OS | macOS 15.7.9 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 11 |

Reproduce the configuration-switching flow on /chat using two BYOK configurations, especially after editing an existing message. Trace how the selected configuration and session or request state are carried into the subsequent request, then verify that switching configurations always routes requests through the newly selected option and does not hang the app.

Written by the indexing model from the issue text.