Android app has no way to open the command palette, so "Triage an issue" cannot be started there
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
- Área
- developer-experience, mobile
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
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:
HardwareKeyboardCommandProvider.tsx#L135-L137is the onlysetPaletteOpen(true)call. No button or gesture opens the palette.- iOS maps ⌘K to
commandPalette(T3KeyboardCommandsModule.swift#L42), so iPhone and iPad users with a hardware keyboard can reach it. - Android's
commandFormaps only Ctrl+Shift+C and Ctrl+Shift+H (T3KeyboardCommandsModule.kt#L36-L47). Nothing maps tocommandPalette, so the palette cannot be opened on Android even with a keyboard. - "Triage an issue" exists only in the palette (
CommandPalette.tsx#L359-L372).useStartTriagehas no other caller.
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
- Install the Android app 2.3.0 and pair it with a server that supports triage.
- Look for a way to open the command palette or start "Triage an issue" by touch. There is none.
- 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
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de pingdotgg/t3code
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
needs more info
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
pingdotgg/t3code#39400 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[Bug]: Wrapped PR titles lose bottom padding in the thread details panelPosiblemente ocupada @iamdatvt94 la tomó hace 1 día. Abiertobug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
bug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
Los mantenedores suelen responder en 1 día
Todos los issues de pingdotgg/t3code
Issues similares
-
area:plugins kind:bug priority:p2 ready
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
Los mantenedores suelen responder en 1 día
-
Escaped `*` followed by `*` (`\**`) never matchesPosiblemente ocupada @bardrop la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 71/100
editorconfig/editorconfig-core-js#172 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
vega/vega-webgpu#40 ·
-
Adjust break point sizingAbiertotype: bug 🐛
Dificultad 2/5 1-3 horas Aptitud para principiantes 63/100
puckeditor/puck#1929 ·
Los mantenedores suelen responder en 1 día
-
compression() compresses every response at Brotli quality 11Posiblemente ocupada @staylor la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día