feat: MCP OAuth flow should open the original chat where you enabled the tool #6661

New Issue

2025-11-11T17:02:43-06:00

GiteaMirror commented

2025-11-11 17:02:43 -06:00

Originally created by @schveiguy on GitHub (Oct 12, 2025).

Check Existing Issues

I have searched the existing issues and discussions.

Problem Description

When enabling an MCP tool with OAuth 2.1 flow, the original chat window is replaced with the authentication url.

Once the auth url completes the authentication, the window is redirected back to the callback, which then just opens the default page without anything selected (including the tool). This also pops up the changelog for me.

Then I have to set up a new chat and enable the tool. This time the connection is authenticated, so the switch turns green.

Desired Solution you'd like

A better experience would be to pick up where the chat left off when the switch was clicked, but with the switch enabled. The fact that an OAuth occurred should be transparent to the chat flow.

Alternatives Considered

None

Additional Context

The code which initiates the oauth: https://github.com/open-webui/open-webui/blob/46ae3f4f5d7d4d706041bdae4ad2d802e568712b/src/lib/components/chat/MessageInput/IntegrationsMenu.svelte#L341

The code which handles the callback on the backend: https://github.com/open-webui/open-webui/blob/46ae3f4f5d7d4d706041bdae4ad2d802e568712b/backend/open_webui/utils/oauth.py#L636

I feel the right way to handle this is to use the state parameter in oauth flow to communicate the chat id being run, and return to that chat id. May also want to save any text that has been typed into the input field.

Originally created by @schveiguy on GitHub (Oct 12, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description When enabling an MCP tool with OAuth 2.1 flow, the original chat window is replaced with the authentication url. Once the auth url completes the authentication, the window is redirected back to the callback, which then just opens the default page without anything selected (including the tool). This also pops up the changelog for me. Then I have to set up a new chat and enable the tool. This time the connection is authenticated, so the switch turns green. ### Desired Solution you'd like A better experience would be to pick up where the chat left off when the switch was clicked, but with the switch enabled. The fact that an OAuth occurred should be transparent to the chat flow. ### Alternatives Considered None ### Additional Context The code which initiates the oauth: https://github.com/open-webui/open-webui/blob/46ae3f4f5d7d4d706041bdae4ad2d802e568712b/src/lib/components/chat/MessageInput/IntegrationsMenu.svelte#L341 The code which handles the callback on the backend: https://github.com/open-webui/open-webui/blob/46ae3f4f5d7d4d706041bdae4ad2d802e568712b/backend/open_webui/utils/oauth.py#L636 I feel the right way to handle this is to use the `state` parameter in oauth flow to communicate the chat id being run, and return to that chat id. May also want to save any text that has been typed into the input field.

GiteaMirror closed this issue

2025-11-11 17:02:43 -06:00

GiteaMirror referenced this issue

2025-11-11 18:04:16 -06:00

[PR #6661] [CLOSED] **feat**: ability to download answers in table format as an Excel or CSV file #8727

GiteaMirror referenced this issue

2026-04-20 03:48:59 -05:00

[PR #6661] [CLOSED] **feat**: ability to download answers in table format as an Excel or CSV file #21931

GiteaMirror referenced this issue

2026-04-25 10:58:39 -05:00

[PR #6661] [CLOSED] **feat**: ability to download answers in table format as an Excel or CSV file #37561

GiteaMirror referenced this issue