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

Aperta
#389 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
dart, flutter
Ambito
testing-qa

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Go
Stelle
6
Fork
3
Merge medio
6h 28m
PR unite (30g)
362

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di AlphaWaveSystems/flutter-probe

Tutte le issue di AlphaWaveSystems/flutter-probe

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.