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 天內回覆