[Bugs] **Short (in-app "Report a problem"):**
- 主要言語
- 言語のデータがありません
- スター
- 2.1k
- フォーク
- 153
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
**Mood:** 😊
**Category:** Bugs
**Short (in-app "Report a problem"):**
**OAuth MCP servers broke after a recent app update.** All MCP servers configured with OAuth stopped authenticating — the "Sign in" button no longer appears in MCP settings, so the OAuth flow never starts. Bearer-token MCP servers still work fine.
This is a regression: it worked a few days ago (sign-in buttons were visible, OAuth servers authenticated fine), it broke right after an update, and my entire team is affected identically — so it's not a local cache/credential issue. The same OAuth servers still work via CLI (e.g. Claude CLI), confirming the servers are healthy and the bug is in the desktop app's OAuth flow specifically.
Expected: sign-in button appears → browser OAuth flow → server authenticates.
Actual: no button, no prompt, servers unusable.
**App version:** 1.0.69-0
OS: Windows. Impact: all OAuth MCP integrations unusable app-wide for the whole team.
---
| Field | Value |
| --- | --- |
| App version | 1.0.15 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 2 |
コントリビューションガイド
調査の方向性
No source files or tests are mentioned. Reproduce the regression in MCP settings on Windows using app version 1.0.69-0, comparing an OAuth server with a bearer-token server and checking the browser flow. Done means OAuth MCP servers show a Sign in button, launch authentication, and authenticate successfully.
索引モデルが issue の本文から書いたものです。
評価
- 領域
- authentication, desktop
- issue の種類
- バグ
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 静か
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 55/100