Android app has no way to open the command palette, so "Triage an issue" cannot be started there

Ouverte
#39,678 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
68/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
android, react-native, typescript

Piste de recherche

Start with HardwareKeyboardCommandProvider.tsx, T3KeyboardCommandsModule.kt, and CommandPalette.tsx to trace how Android opens the palette and where “Triage an issue” is exposed. Consider the touch entry points suggested in the issue, then check that Android users can start triage without a hardware keyboard and that the existing keyboard path still works.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

via-triage
What happened

I wanted to triage a bug that happens on the Android app and attach a screen recording from the phone. In-app triage was added for mobile in #22753, but its only entry point is "Triage an issue" in the command palette. On Android I could not find any way to open the palette, so I had to start the triage on desktop, send the first message there, and then send the video from the phone as a second message.

Diagnosis

The mobile command palette opens only when the native keyboard module emits the commandPalette hardware keyboard command:

The code is the same on main (205400e7).

Mobile is often where the bug and its evidence (screen recordings, screenshots) are, so a touch entry point for triage would let users start the report and attach the media in one place. For example, put "Triage an issue" in Settings or in the new-task menu, or add a touch way to open the palette. Adding Ctrl+K on Android would help keyboard users too.

Steps to reproduce
  1. Install the Android app 2.3.0 and pair it with a server that supports triage.
  2. Look for a way to open the command palette or start "Triage an issue" by touch. There is none.
  3. With a hardware keyboard, no shortcut opens the palette either, because Android maps no key to commandPalette (found in the source, not tested on a device).
Version

Android app 2.3.0. Server and desktop app 0.1.11-nightly.20261119.4941.

Environment
  • Phone: Samsung Galaxy S24 Ultra (SM-S928U1), T3 Code 2.3.0 from Google Play (store update dated 9 Nov 2026)
  • Server: desktop app on macOS (arm64), 0.1.11-nightly.20261119.4941
Evidence

Source references above. The app version was set to 2.3.0 in d1909d68 (2026-11-10 03:54 UTC), after #22753 (2026-10-27). At that commit, the palette has "Triage an issue" and Android still maps no key to commandPalette.

Related issues

#22753 (adds in-app triage, including on mobile)

Fix applied or workaround

Start the triage on desktop, send a first message, then send the media from the phone as the next message in that thread.

Filed by

Claude Code (Opus 5.5, claude-opus-5-5) running in a T3 Code triage session.

Langage dominant
TypeScript
Étoiles
24.8k
Forks
6.4k
Merge moyen
4 h 29 min
PR mergées (30 j)
488

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de pingdotgg/t3code

Toutes les issues de pingdotgg/t3code

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.