T3 Code Claude thread shows performance comparison text without its chart

Aberta
#105 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
25/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Domínio
devtools, mobile

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
C++
Estrelas
243
Forks
21
Merge médio
15h 6min
PRs com merge (30d)
57

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de callstackincubator/codex-mobile-dev-plugin

Todas as issues de callstackincubator/codex-mobile-dev-plugin

Issues semelhantes

Mais issues de C++

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.