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

Abierto
#39,678 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
68/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
android, react-native, typescript

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
24.8k
Forks
6.4k
Merge medio
4 h 29 min
PR fusionados (30 d)
488

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de pingdotgg/t3code

Todos los issues de pingdotgg/t3code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.