Send Mobile Dev screen annotations to the active T3 Code Claude thread
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 22/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- android, ios, react-native
调研方向
The payload names no files, so start from the Mobile Dev browser panel code and the mobile_read_panel_context hook it exposes, then find where T3 Code's active Claude thread accepts messages. Done means a panel action sends the screenshot and notes into that thread and shows a confirmation, verified end to end with the panel placement from #96. This needs knowledge of the plugin's panel and chat integration, and the issue is tied to #89, #94 and #96.
由索引模型根据 Issue 内容生成。
描述
What happened
In T3 Code with Mobile Dev installed through Claude Code, the presenter marked two parts of the simulator screen and added notes. The notes appeared in the Mobile Dev browser panel. To get Claude to use them, the presenter had to switch to the chat and type a separate request to read the notes. The browser panel can share context for mobile_read_panel_context, but it has no chat message bridge.
- Adding annotations in the Mobile Dev panel at 1:02:18
- Presenter explains the browser-panel limitation at 1:02:44
- Manual prompt to read the notes at 1:03:20
Expected behavior
From the panel, hand the annotations off to the active thread with an explicit user action. The action should carry the screenshot and notes to Claude and give the user visible confirmation. Check the T3 Claude path end to end, including the panel placement in #96. #89 noted the missing browser-panel chat bridge. #94 addresses clearing notes after they have been read. The demo also shows the presenter asking to clear already-handled notes at 1:13:48.
- 主要语言
- C++
- 星标
- 243
- 派生
- 21
- 平均合并
- 15 小时 6 分钟
- 30 天内合并 PR
- 57
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
callstackincubator/codex-mobile-dev-plugin 的其他 Issue
-
enhancement
难度 4/5 3-5 天 新手友好度 35/100
callstackincubator/codex-mobile-dev-plugin#119 ·
维护者通常 1 天内回复
-
documentation
难度 3/5 1-2 天 新手友好度 45/100
callstackincubator/codex-mobile-dev-plugin#117 ·
维护者通常 1 天内回复
-
enhancement
难度 3/5 1-2 天 新手友好度 45/100
callstackincubator/codex-mobile-dev-plugin#116 ·
维护者通常 1 天内回复
-
enhancement
难度 3/5 1-2 天 新手友好度 55/100
callstackincubator/codex-mobile-dev-plugin#115 ·
维护者通常 1 天内回复
-
bug
难度 3/5 1-2 天 新手友好度 45/100
callstackincubator/codex-mobile-dev-plugin#114 ·
维护者通常 1 天内回复
查看 callstackincubator/codex-mobile-dev-plugin 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
CachyOS/packageinstaller#144 ·
维护者通常 1 天内回复
-
documentation
难度 1/5 1 小时以内 新手友好度 82/100
TomerAberbach/profiler-md#951 ·
维护者通常 1 天内回复
-
[Bug] Default key routing (JavaStringHash) picks a different partition than the Java client for about half of keys可能已有人在做 @0z5a 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
apache/pulsar-client-go#1575 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
pocoproject/poco#5764 ·
维护者通常 2 天内回复
-
bug cpp-core-guidelines low-priority
难度 2/5 1-3 小时 新手友好度 62/100
NatronGitHub/openfx-supportext#164 ·
维护者通常 1 天内回复