The live Performance panel blocks agent-started recordings of the same app

Abierto
#97 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
ios

Línea de trabajo

Start from the mobile_record_performance tool and the CPU session manager that the Performance panel and the recorder both use, since the issue says that manager allows one collector per target. Read #89 for the earlier notes on the same conflict. Done means a timed recording can start while the live panel is open, or the agent gets a clear, actionable handoff instead of a rejection.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug

What happened

In a T3 Code Claude thread on macOS, the Mobile Dev Performance panel was already showing live CPU and memory for Experimenta on an iOS simulator. Claude tried to record two timed runs for the same app. The first run was blocked by the panel's CPU monitor, and Claude asked the presenter to stop it manually and reply before it could continue.

Reproduce

  1. Run an app on an iOS simulator and open Mobile Dev's Performance panel. Wait for the live CPU chart.
  2. Ask the agent to make a timed performance recording of the same app using mobile_record_performance.
  3. The tool rejects the recording while the panel owns the monitor. The agent has no actionable handle for that session.

The panel and the recorder share the CPU session manager, which allows one collector per target. The same conflict was noted in #89. The demo used T3 Code, and the collector code is shared across hosts.

Expected behavior

The user and agent can move from live monitoring to a timed recording with a clear handoff and a single collector. If a user action is required, identify the exact control and let the agent recover from the conflict without guessing whether it can proceed.

Lenguaje dominante
C++
Estrellas
243
Forks
21
Merge medio
15 h 6 min
PR fusionados (30 d)
57

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de callstackincubator/codex-mobile-dev-plugin

Todos los issues de callstackincubator/codex-mobile-dev-plugin

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.