Android: a thread with many subagent rows takes 8–13 s to show its messages, and its forks inherit the delay
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 52/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- android, react-native, typescript
- Ambito
- mobile, performance
Direzione di ricerca
Start with apps/mobile/src/features/threads/thread-subagent-group.tsx at the reported subscription point, then trace how thread feed rows are rendered and whether full history or many subagent rows affect that path. Reproduce with the described Android thread and profile JavaScript rendering; compare against a thread with few subagent rows. Done means the messages appear promptly on repeated opens and forks, with profiling evidence identifying the delay.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
What happened
On the Android app, one thread takes 8–13 seconds to show its messages each time I open it. The screen stays blank under the header until then. A fork of that thread has the same delay. Other threads open at once, including a much larger one (1,752 items, about 23 MB) and a fork that inherits 2.2 MB of history.
Diagnosis
- The server is not the cause. Each open sends
orchestration.subscribeThreadwith a resume sequence. The server replays in about 1 ms, and nogetThreadSnapshotWindowruns. All other RPCs in the window finished in under 15 ms. - The delay is in the app, between receiving the data and drawing the rows. On one open of the fork, the app subscribed to the parent thread 8 s after the fork. That subscribe comes from
ThreadSubagentGroup(apps/mobile/src/features/threads/thread-subagent-group.tsx:120), which mounts only when the feed draws a subagent group row. So no rows were mounted for 8 s. - The phone's
vcs.listRefscall came within 1 s of the content appearing on every open. It seems to follow the render; it does not cause the wait. - Settled state is not the cause. Unsettling the parent made no difference.
- Size alone is not the cause:
- Slow: 118 items, 1.1 MB, 24 subagent, 14 dynamic_tool, 23 command_execution, 2 compaction.
- Fast: 412 items, 2.2 MB, 2 subagent, 43 dynamic_tool, 117 command_execution.
- Fast: 1,752 items, 23 MB, 5 subagent. This one probably loads as a bounded window.
- Unproven guess: the cost is in drawing many subagent rows, or in drawing the full history of a thread that is small enough to skip the bounded window. A JS profile from the device would confirm it.
Steps to reproduce
- On desktop, use a thread with about 24 subagent items and some large dynamic tool results, small enough to load in full (about 120 items).
- Open it in the Android app 2.3.0 over T3 Connect. The messages appear after 8–13 s.
- Fork it at a later run and open the fork. It has the same delay.
- Open a thread with few subagent rows but more data. It opens at once.
I have no minimal repro yet. The steps above describe the thread I have.
Version
Android app 2.3.0 (Play Store); server 0.1.11-nightly.20261119.4941
Environment
Samsung SM-S928U1 (Android), connected through T3 Connect; server on macOS arm64
Evidence
# open fork (parent settled)
10:32:00.433 subscribeThread fork (resume, server work ~1 ms)
10:32:00.73-01.05 getThreadLinkMetadata x50, each <15 ms
(no RPCs from the app for 7 s)
10:32:08.519 subscribeThread parent <- subagent group row mounts; content visible
# open parent alone, unsettle, open fork, open parent again
11:46:19.891 subscribeThread parent
11:46:27.071 vcs.listRefs <- content visible (~8 s)
11:46:30.582 dispatchCommand thread.unsettle parent
11:46:37.301 subscribeThread fork
11:46:37.601 subscribeThread parent
11:46:48.021 vcs.listRefs <- content visible (~11 s)
11:46:51.901 subscribeThread parent
11:47:04.161 vcs.listRefs <- content visible (~12 s)
Related issues
#34240 "Mobile sync is slow" (closed, no details). That issue is about sync in general. This one is one thread that is slow to draw while the server answers at once.
Fix applied or workaround
None found. Nothing was changed on the machine. The parent was unsettled for the test and then settled again.
Filed by
Claude Code (Claude Opus 5.5, claude-opus-5-5) inside T3 Code, following the t3 triage playbook
- Lingua principale
- TypeScript
- Stelle
- 24.8k
- Fork
- 6.4k
- Merge medio
- 4h 29m
- PR unite (30g)
- 488
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di pingdotgg/t3code
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
needs more info
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
pingdotgg/t3code#39400 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: Wrapped PR titles lose bottom padding in the thread details panelForse già presa @iamdatvt94 l’ha presa 1 giorno fa. Apertabug needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
bug needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di pingdotgg/t3code
Issue simili
-
area:plugins kind:bug priority:p2 ready
Difficoltà 2/5 1-3 ore Idoneità per principianti 90/100
I maintainer di solito rispondono entro 1 giorno
-
Escaped `*` followed by `*` (`\**`) never matchesForse già presa @bardrop l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 71/100
editorconfig/editorconfig-core-js#172 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
vega/vega-webgpu#40 ·
-
Adjust break point sizingApertatype: bug 🐛
Difficoltà 2/5 1-3 ore Idoneità per principianti 63/100
puckeditor/puck#1929 ·
I maintainer di solito rispondono entro 1 giorno
-
compression() compresses every response at Brotli quality 11Forse già presa @staylor l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno