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

Abierto
#389 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
dart, flutter
Área
testing-qa

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Go
Estrellas
6
Forks
3
Merge medio
6 h 28 min
PR fusionados (30 d)
362

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de AlphaWaveSystems/flutter-probe

Todos los issues de AlphaWaveSystems/flutter-probe

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.