OAuth approval fails with “Sign-in cannot continue” for Muse MCP connector despite reachable T3 Connect environment

オープン
#39,242 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
45/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
typescript

調査の方向性

Start by tracing the hosted OAuth approval flow from the authorization request through retrieval of approval details, then identify which service or endpoint can return “Sign-in cannot continue” at that stage. Compare the flow with the session-validation fix in PR #33645, which addresses a later failure. Done means identifying the failing stage and a verified fix or diagnostic path; the issue does not name relevant files or tests, so this will require familiarity with the authentication system.

索引モデルが issue の本文から書いたものです。

説明

needs more info

Summary

I am experiencing an OAuth approval failure when connecting Muse Desktop 10.1 to an isolated T3 Code Beta 0.1.10 environment through the official T3 Connect managed HTTPS relay.

Muse successfully completes dynamic client registration and reaches the T3-hosted OAuth authorization flow.

However, the hosted approval page displays:

“Sign-in cannot continue”

The failure occurs before the approval details are displayed and before I can review or approve the requested read-only access.

During the failure window, the isolated T3 environment remains registered and responds to independent anonymous MCP requests.

The underlying cause remains unknown.

Environment

  • Operating system: macOS (Apple Silicon)
  • Muse Desktop: 10.1
  • T3 Code: Beta 0.1.10
  • Relay client: Official cloudflared 2026.10.4
  • Relay transport: HTTP/2
  • Remote access: Official T3 Connect managed HTTPS endpoint
  • Test environment: Isolated T3 instance containing one synthetic project
  • Test data: Zero threads and zero AI executions

No production projects or real user data were included in the isolated environment.

Steps to Reproduce

  1. Complete the official T3 CLI device authorization flow for the isolated environment.
  2. Verify that the CLI successfully receives and stores its temporary authentication credentials.
  3. Send a separate authenticated HTTP request to the official T3 Connect environment registry using the credential obtained through CLI device sign-in, and verify that it returns HTTP 200.
  4. Link the isolated T3 environment through the official T3 Connect workflow.
  5. Verify that the registered environment matches the HTTPS endpoint configured in the dedicated Muse connector.
  6. Confirm that anonymous MCP initialization returns HTTP 401 and both OAuth discovery endpoints return HTTP 200.
  7. Select Connect in the existing Muse MCP connector.
  8. Allow Muse to initiate OAuth client registration and authorization.
  9. Open the T3-hosted authorization page while keeping the isolated server and relay operational.
  10. Observe the authorization page before the read-only approval details appear.

Expected Behavior

The hosted authorization page should retrieve the approval details for the registered isolated environment.

The user should be able to review the requesting application, inspect the requested OAuth permissions, and approve or deny access, including selecting read-only access without granting execution permissions.

If approved, the OAuth flow should continue to the authorization-code exchange and authenticated MCP connection.

Actual Behavior

The hosted approval page displays:

“Sign-in cannot continue”

The approval details do not appear, and the user cannot complete the approval.

No successful approval decision, Muse OAuth token exchange, authenticated MCP initialization, or project-reading operation was observed.

The isolated environment remained registered and reachable through an independent anonymous MCP probe during the reported failure window.

Verified OAuth and Network Evidence

Operation Observed Result
CLI device sign-in Completed successfully; temporary credential obtained
Separate authenticated HTTP request to the official T3 Connect environment registry HTTP 200 using the credential obtained through CLI device sign-in
Anonymous MCP initialization HTTP 401
OAuth protected-resource discovery HTTP 200
OAuth authorization-server discovery HTTP 200
Dynamic client registration HTTP 201
OAuth authorization request HTTP 302
Requested OAuth scope orchestration:read
Approval details request No matching request observed in the retained isolated-server trace
Approval decision No matching request observed
Muse OAuth token exchange Not observed
Authenticated Muse MCP initialization Not observed
Project and thread tool responses Not observed

The successful anonymous MCP probe confirms that the isolated endpoint was reachable from the probing client.

It does not establish that the hosted approval page successfully resolved the environment, obtained the necessary authorization credentials, or reached the protected approval endpoint.

The retained trace also includes successful T3 Connect credential requests and a successful request to a separate /oauth/token endpoint.

These operations are distinct from the Muse MCP OAuth token exchange and should not be interpreted as proof that Muse authorization succeeded.

Relevant Timeline

All timestamps are from November 19, 2026, in UTC.

Time (UTC) Observation
16:36:56 Official CLI device authorization completed successfully.
Approximately 16:37 A separate authenticated HTTP request to the official T3 Connect environment registry returned HTTP 200 using the credential obtained through CLI device sign-in.
16:44:21–16:44:24 Official HTTP/2 relay connections registered.
16:44:34 Anonymous MCP initialization returned HTTP 401.
16:45:38–16:45:40 OAuth discovery endpoints returned HTTP 200.
16:46:31 Muse dynamic client registration returned HTTP 201.
16:46:45 OAuth authorization returned HTTP 302.
16:47:18–16:47:30 T3 Connect credential requests returned HTTP 200.
Approximately 16:48–16:49 Hosted approval page displayed “Sign-in cannot continue.”
16:48:12 Independent anonymous MCP probe returned HTTP 401.
After 16:49 Cleanup began following the reported error.

The timestamps are based on retained sanitized logs and the observed browser error window.

Troubleshooting Already Performed

1. Verified CLI Authentication

The official device authorization completed successfully, and the CLI obtained and stored usable credentials.

An authenticated request to the official T3 Connect environment registry returned HTTP 200 using the credential obtained through CLI device sign-in.

The registry query was a separate HTTP operation, not a registry query performed directly by the CLI.

2. Verified Environment Registration

The isolated environment appeared in the official account registry.

The registered HTTPS endpoint matched the endpoint configured in the Muse connector.

3. Verified Relay Availability

The official cloudflared relay established HTTP/2 connections.

An independent MCP request reached the isolated server during the reported authorization failure.

4. Verified OAuth Registration and Redirect

Muse successfully registered its OAuth client.

The authorization request passed server-side validation and returned HTTP 302.

The requested scope was limited to orchestration:read.

This was the requested scope, not a verified granted scope.

5. Ruled Out Premature Relay Shutdown for This Attempt

An earlier test included a possible race between OAuth approval and relay cleanup.

In the controlled reproduction, the relay remained operational throughout the observed failure.

Cleanup began only after the authorization error was reported.

Therefore, premature relay shutdown does not explain this particular reproduction.

6. Reviewed Related Upstream Changes

I reviewed PR #33645, which addresses an approval-decision failure involving session validation after approval details have already loaded.

That fix is included in T3 Code 0.1.10.

The current failure occurs before approval details are successfully retrieved, so I cannot establish that it is the same issue.

Questions for Maintainers

I would appreciate guidance on the following:

  1. Which component or service path can produce “Sign-in cannot continue” before the hosted approval details are displayed?
  2. Is there a supported way to distinguish between environment lookup failure, browser account-session failure, T3 Connect credential issuance failure, protected approval-endpoint failure, and an internal hosted approval-service error?
  3. Is this behavior a known issue affecting T3 Code Beta 0.1.10?
  4. Is there a verified fix or recommended supported release specifically addressing this failure stage?
  5. Can the hosted approval flow provide a non-sensitive diagnostic identifier or error category that users can safely include in bug reports?
  6. Is there an officially supported read-only workaround that avoids the failing hosted approval step?
  7. Would additional sanitized timestamps or route-level diagnostic information help with triage?

Security and Privacy

The test used an isolated environment containing only synthetic data.

Temporary authorization sessions and the remote environment registration were removed after testing.

No AI execution or paid API calls occurred.

This report intentionally excludes access tokens, refresh tokens, authorization codes, device codes, session cookies, sensitive OAuth URLs, private account identifiers, environment identifiers, local filesystem paths, and unredacted authentication screenshots.

I can provide additional sanitized diagnostic information if the maintainers identify a safe and supported collection procedure.

Thank you for your assistance.

主要言語
TypeScript
スター
24.8k
フォーク
6.4k
平均マージ
4時間 29分
マージ済み PR(30日)
488

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

pingdotgg/t3code のほかの issue

pingdotgg/t3code の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。