T3 Code Claude thread shows performance comparison text without its chart

Aperta
#105 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

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
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
devtools, mobile

Direzione di ricerca

Start with the mobile_compare_performance_recordings tool and reproduce it in a T3 Claude thread with two completed recordings. Check whether Claude invokes the tool, whether T3 receives the MCP App resource and structuredContent, and whether the chart card mounts. Compare with the native Claude panel change in #96. Done means the comparison chart appears beside Claude's textual findings.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug

What happened

In a T3 Code Claude thread, the presenter asked Mobile Dev to record and compare Experimenta with and without a button animation. After both recordings finished, Claude reported CPU and memory numbers and referred to the comparison chart above its answer. The recording shows the completed wait command and final response with no comparison card visible between them.

Expected behavior

A successful mobile_compare_performance_recordings call in a T3 Claude thread displays the interactive chart beside the textual findings. Reproduce with two completed recordings and capture whether Claude actually invoked the comparison tool, whether T3 received the MCP App resource and structuredContent, and whether the card was mounted. The replay establishes the missing visible result. It does not show the tool payload.

The released Claude plugin registers comparison cards separately from the browser device panel. Verify this path with the native Claude panel change in #96 as well.

Lingua principale
C++
Stelle
243
Fork
21
Merge medio
15h 6m
PR unite (30g)
57

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di callstackincubator/codex-mobile-dev-plugin

Tutte le issue di callstackincubator/codex-mobile-dev-plugin

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.