Studio automation: optional visible mode for agent-driven sessions (design)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 冷清
- 技术栈
- dart, flutter
- 领域
- testing-qa
调研方向
Start by reading the existing Studio automation endpoint and MCP tool implementations, then trace the current boundaries for loopback access, launch tokens, path confinement, and local device targets. The issue leaves visibility control, banner behavior, display handling, replay recording, and supported in-app actions undecided, so a first step is to resolve those design questions; implementation is done only after the scope and boundaries are agreed.
由索引模型根据 Issue 内容生成。
描述
Split out of #331 (its headed-mode addendum). This issue is for design only: nothing here is decided and nothing is assigned.
Context
The automation endpoint (PROBE_STUDIO_AUTOMATION=1, off by default) lets a script or an MCP client drive a running Studio without a window, cursor or focus. The browser suite covers the UI in headed or headless Chromium. Neither shows an agent-driven session in the real Studio window.
Idea under discussion
- An opt-in visible mode in which the real Studio window shows what an automation client is doing: the open file, the selected device, the live step highlight and the results update as the client works.
- A
visibleflag on the Studio MCP tools (studio_open_workspace,studio_run_fileand the others), with the default to be decided. - A small in-app banner while automation is driving the session, so a person at the machine can see it.
- Actions would go through the app (backend methods and in-page actions), not operating-system mouse or keyboard events, so the person's cursor and focus are not taken.
Open questions
- How visible mode fits the existing boundaries: loopback only, the per-launch token, the path confinement, and the local-target policy for device connections. Visible mode must not add a way around any of them.
- Who decides visibility: only the Studio process (for example through an environment variable), or can an automation client request it per call?
- The banner: its text, when it appears and clears, and whether the person can dismiss it.
- What happens with no second display attached, or with no display at all.
- Whether a visible session is also recorded for replay, and where that data would live.
- Which Studio actions can run inside the app without operating-system input (for example connect, run, cancel), and which would need a separate design.
Not in scope
Changing the current automation or MCP behaviour, the local-target policy, the token or the confinement rules. Any such change would need its own review.
- 主要语言
- Go
- 星标
- 6
- 派生
- 3
- 平均合并
- 6 小时 28 分钟
- 30 天内合并 PR
- 362
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
AlphaWaveSystems/flutter-probe 的其他 Issue
-
agent: is checked on a wrapper holding several checkables answers from the first one in tree order未关闭bug
难度 2/5 1-3 小时 新手友好度 76/100
AlphaWaveSystems/flutter-probe#865 ·
维护者通常 1 天内回复
-
area/cli bug
难度 2/5 1-3 小时 新手友好度 73/100
AlphaWaveSystems/flutter-probe#424 ·
维护者通常 1 天内回复
-
area/docs documentation
难度 2/5 1-3 小时 新手友好度 70/100
AlphaWaveSystems/flutter-probe#409 ·
维护者通常 1 天内回复
-
Dial timeout error should say how long it waited and name the timeout setting可能已有人在做 @jay23606 于 2 天前认领。 未关闭area/cli bug
难度 2/5 1-3 小时 新手友好度 78/100
AlphaWaveSystems/flutter-probe#408 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 45/100
AlphaWaveSystems/flutter-probe#888 ·
维护者通常 1 天内回复
查看 AlphaWaveSystems/flutter-probe 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
IBM-Cloud/terraform-provider-ibm#7115 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
fluxcd/notification-controller#1441 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
volcengine/volcengine-go-sdk#163 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 76/100
OneBusAway/maglev#2145 ·
维护者通常 2 天内回复
-
priority/medium status/ready type/chore
难度 2/5 1-3 小时 新手友好度 84/100
discobox-ai/discobox#1357 ·
维护者通常 1 天内回复