You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Linked-environment tool reports reachable after credential is lost #40635
The MCP t3_environment_links response marked a linked environment status: "reachable" while its lastError said The link to Desktop-Elliot lost its credential. Link it again. A subsequent read-only t3_thread_read against that environment failed with the same credential error.
Please expose an actionable unusable/auth-required state (or explicitly distinguish transport reachability from authorized tool access) so agents do not interpret reachable as usable. The endpoint can be transport-reachable while the link cannot perform even a read.
Observed sequence:
Call t3_environment_links: linked desktop has status: reachable and a credential-loss lastError.
Call t3_thread_read with the returned environmentId and a valid source threadId.
Attempt to relink using t3_environment_link: current auto-mode thread receives capability_denied explaining environment-setting changes need a live full-access/default calling thread or full-access client.
No credentials or environment identifiers are included in this report. Read-only SSH access worked, allowing the requested handoff review to continue. The relink permission restriction itself is not claimed to be a bug.
Activity