Studio automation: optional visible mode for agent-driven sessions (design)

オープン
#389 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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 の本文から書いたものです。

説明

area/studio enhancement

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 visible flag on the Studio MCP tools (studio_open_workspace, studio_run_file and 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

  1. 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.
  2. Who decides visibility: only the Studio process (for example through an environment variable), or can an automation client request it per call?
  3. The banner: its text, when it appears and clears, and whether the person can dismiss it.
  4. What happens with no second display attached, or with no display at all.
  5. Whether a visible session is also recorded for replay, and where that data would live.
  6. 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分
マージ済み PR(30日)
362

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

AlphaWaveSystems/flutter-probe のほかの issue

AlphaWaveSystems/flutter-probe の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。