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
Android question cards do not open workspace file links #29119
On T3 mobile app 2.2.0 on Android 17, a workspace Markdown link in an agent question card did nothing when tapped. The same probe file opened successfully from a normal chat message and displayed Revision A.
Diagnosis
In the inspected local source, PendingUserInputCard.QuestionText sends links through useOpenPullRequest, whose fallback attempts an external URL. It does not use the workspace-file navigation used elsewhere. This is a candidate explanation, not a version-matched device reproduction.
Steps to reproduce
An agent includes a local workspace file link in a question card.
Tap that link in the question; the user observes no action.
Tap a link to the same file in a normal chat message; it opens.
Version
T3 mobile app 2.2.0; connected host server 0.1.6
Environment
Mobile T3 2.2.0, Android 17; host server 0.1.6 on macOS arm64. Phone: Pixel 10 XL; stock Gboard with latest available updates per user.
Evidence
The probe existed on disk as Revision A and was opened from normal chat. Source lead: apps/mobile/src/features/threads/PendingUserInputCard.tsx and native/useOpenPullRequest.ts at local checkout 7d9725a. The shipped mobile build has not been matched to that checkout.
Related issues
No confirmed duplicate identified yet. This concerns question-card local links, separately from file-content freshness and question-field typing.
Fix applied or workaround
Use the normal chat file link. The probe was not modified until the user confirmed Revision A had loaded.
Filed by
Codex, gpt-6.1-sol; T3 triage playbook followed in existing session.
Superseded by #29351. The identical report was recreated using the repository's Triage report template, which correctly applies via-triage. Please track the bug in #29351.
Activity
mayesidev commentedon Nov 2, 2026
Superseded by #29351. The identical report was recreated using the repository's Triage report template, which correctly applies via-triage. Please track the bug in #29351.