Send Mobile Dev screen annotations to the active T3 Code Claude thread

Aberta
#99 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
22/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
android, ios, react-native

Direção de pesquisa

The payload names no files, so start from the Mobile Dev browser panel code and the mobile_read_panel_context hook it exposes, then find where T3 Code's active Claude thread accepts messages. Done means a panel action sends the screenshot and notes into that thread and shows a confirmation, verified end to end with the panel placement from #96. This needs knowledge of the plugin's panel and chat integration, and the issue is tied to #89, #94 and #96.

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

Descrição

enhancement

What happened

In T3 Code with Mobile Dev installed through Claude Code, the presenter marked two parts of the simulator screen and added notes. The notes appeared in the Mobile Dev browser panel. To get Claude to use them, the presenter had to switch to the chat and type a separate request to read the notes. The browser panel can share context for mobile_read_panel_context, but it has no chat message bridge.

Expected behavior

From the panel, hand the annotations off to the active thread with an explicit user action. The action should carry the screenshot and notes to Claude and give the user visible confirmation. Check the T3 Claude path end to end, including the panel placement in #96. #89 noted the missing browser-panel chat bridge. #94 addresses clearing notes after they have been read. The demo also shows the presenter asking to clear already-handled notes at 1:13:48.

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.