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

未关闭
#97 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
30/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
ios

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
C++
星标
243
派生
21
平均合并
15 小时 6 分钟
30 天内合并 PR
57

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

callstackincubator/codex-mobile-dev-plugin 的其他 Issue

查看 callstackincubator/codex-mobile-dev-plugin 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。