Studio automation: optional visible mode for agent-driven sessions (design)
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
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.
- Lenguaje dominante
- Go
- Estrellas
- 6
- Forks
- 3
- Merge medio
- 6 h 28 min
- PR fusionados (30 d)
- 362
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de AlphaWaveSystems/flutter-probe
-
agent: is checked on a wrapper holding several checkables answers from the first one in tree orderAbiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
AlphaWaveSystems/flutter-probe#865 ·
Los mantenedores suelen responder en 1 día
-
area/cli bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
AlphaWaveSystems/flutter-probe#424 ·
Los mantenedores suelen responder en 1 día
-
area/docs documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
AlphaWaveSystems/flutter-probe#409 ·
Los mantenedores suelen responder en 1 día
-
Dial timeout error should say how long it waited and name the timeout settingPosiblemente ocupada @jay23606 la tomó hace 2 días. Abiertoarea/cli bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
AlphaWaveSystems/flutter-probe#408 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
AlphaWaveSystems/flutter-probe#888 ·
Los mantenedores suelen responder en 1 día
Todos los issues de AlphaWaveSystems/flutter-probe
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
IBM-Cloud/terraform-provider-ibm#7115 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
fluxcd/notification-controller#1441 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
volcengine/volcengine-go-sdk#163 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
OneBusAway/maglev#2145 ·
Los mantenedores suelen responder en 2 días
-
priority/medium status/ready type/chore
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
discobox-ai/discobox#1357 ·
Los mantenedores suelen responder en 1 día