You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
The live Performance panel blocks agent-started recordings of the same app #97
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.
Run an app on an iOS simulator and open Mobile Dev's Performance panel. Wait for the live CPU chart.
Ask the agent to make a timed performance recording of the same app using mobile_record_performance.
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.
Activity