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

Aperta
#97 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
30/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
ios

Direzione di ricerca

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.

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

Descrizione

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.

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.