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

オープン
#39,678 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
68/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
android, react-native, typescript

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
TypeScript
スター
24.8k
フォーク
6.4k
平均マージ
4時間 29分
マージ済み PR(30日)
488

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

pingdotgg/t3code のほかの issue

pingdotgg/t3code の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。