Mobile Dev browser panel disconnects during an active T3 Code Claude thread

Aberta
#107 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
18/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
android, ios, react-native
Domínio
devtools, mobile-dev

Direção de pesquisa

The payload names no source files, so start by reproducing the disconnect: stop a simulator, then restart it from the docked Mobile Dev panel while a Claude Code thread is open. Find the browser bridge ping/transport and the Claude MCP server lifecycle code, and log which connection drops. Done means the panel stays attached through a restart, or shows a reconnect path that restores the panel and device. Related: #43.

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

Descrição

bug

What happened

During an App Flow retry in T3 Code with the Claude Code plugin, the presenter stopped the selected simulator, then tried to start it again from the docked Mobile Dev browser panel. The panel showed Mobile Dev disconnected from its chat session. Ask the agent to open Mobile Dev again. The T3 thread was still accepting messages. The presenter asked Claude to restart Mobile Dev, and the preview eventually returned.

Expected behavior

Stopping and restarting a simulator should keep the panel attached to its active thread. If the connection fails, show a clear reconnect path that restores the panel and selected device. Capture browser bridge ping/transport results and Claude MCP server lifecycle on repro. The recording does not establish which connection failed. #43 tracks polling after an already-closed Codex thread.

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.