[Bug Bash 4/16] Linear MCP authorization not recognized after successful OAuth setup

[joe-rlo]

Bug Report — QA Bug Bash 4/16

Environment: Staging (hosted-staging / crab shack) — https://agent-stg.near.ai/

Description:
After completing Linear MCP OAuth setup, the dashboard shows the integration as "connected." However, when the agent attempts to use the Linear tool, it still prompts the user for an access token — as if the OAuth flow never happened.

Steps to Reproduce:

1. Connect Linear MCP integration via OAuth on staging
2. 2. Verify the dashboard shows "Connected" status
3. 3. Ask the agent to perform a Linear operation (e.g., list issues)
      Actual Result:
      Agent does not recognize the authorized connection and requests a manual access token from the user, despite the dashboard confirming the integration is connected.

Expected Result:
Once the OAuth flow completes and the dashboard shows "Connected," the agent should use the stored credentials automatically without prompting for manual token entry.

Severity: High — MCP integration is non-functional despite appearing connected
Frequency: Reproducible during bug bash testing

Related: #2229 (Google Sheets OAuth blocked — similar pattern of OAuth integration failure)

[serrrfirat]

This looks likely covered by #2515, which merged to staging on 2026-04-16 after this bug was filed.

Why it matches this symptom:

• unified chat/settings extension setup paths
• OAuth continuation from setup is treated as auth_required, not failure
• OAuth-only auth cards no longer render a manual token textbox
• gate-backed auth resolution now uses scoped structured submissions instead of routing credentials through normal chat
• tool_install now follows the real readiness path so LLM-visible tool state matches UI readiness

I also checked nearby auth/MCP PRs:

• [codex] Stabilize auth readiness and gate flows #2050 and fix(v2): tool naming, auth gates, schema flatten, WASM traps, workspace race #2209 fixed broader MCP/OAuth readiness issues, but both merged before this bug was filed, so they probably did not fully cover the staging regression.
• [codex] Add full auth ops canary coverage #2376 mentions Linear auth, but it was canary coverage and closed unmerged.
• fix: use gateway owner_id for relay OAuth nonce storage #2473 was OAuth nonce scoping, but specifically for Slack relay OAuth.

Recommendation: retest Linear MCP OAuth on staging with #2515 deployed. If Linear no longer prompts for a manual token after dashboard shows connected, we can close this as fixed by #2515.