[Task][RFC]: Qualify attached and managed Agent session modes
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
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- python, typescript
Línea de trabajo
Start with the linked RFC and the current owners and PRs (#5051, #5039, #5130, #5188) to identify an unowned acceptance gap before making changes. Inspect loopx/control_plane/turn_driver, host_binding.py, and apps/desktop/loopx-control-plane, then verify the real host entrypoints and backend. Done means the accepted scope has supported-host lifecycle tests and reconciled evidence for the integrated revision, including passed, failed, untested, and remaining gates.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Outcome / 目标
验收 attached / managed 会话模式。One task tracks this RFC's delivery; keep implementation PRs and milestone evidence here instead of creating a parallel task tree.
Canonical design: RFC. Roadmap: S4/R2, under #4574. Design acceptance is distinct from implementation, live qualification and promotion.
Current boundary
Source audit: main at ce3862e33 (2026-09-28). This is source/PR inspection, not a new test or live-qualification claim.
Attached bindings, broker/fencing and managed process supervision exist. Merged #5144 adds a shared TS managed-host process owner. Registration or a successful segment does not prove cross-host lifecycle qualification.
Work remaining
- Complete the RFC M1–M4 admission and lifecycle matrix using existing host bindings: explicit persisted mode, one executor and typed unsupported-capability results.
- Carry mode and effective launch context through restart, attached-host parity and frontend readback without inferring or silently switching ownership.
Ownership and ongoing work
Reuse #5051/#5039 and PRs #5130/#5188 where relevant. Desktop owns onboarding/UX; this RFC owns session admission. Do not launch a second executor or duplicate the active supervision work.
Contribution route: implementation/integration overlaps active work. Start from the linked current owners/PRs and identify an unowned acceptance gap in a claim comment; do not begin a competing rewrite.
Acceptance
- Real supported-host tests cover bind/start/resume/interrupt/close, crash, stale binding and duplicate completion.
- Off-state preserves native host behavior; conversation text cannot substitute for canonical validation and settlement.
- CLI and packaged frontend report the same mode and availability; qualify each advertised host independently.
- Reconcile the RFC's current delivery checkpoint and this issue with the integrated revision, commands, passed/failed/untested evidence and remaining gates. Close the accepted scope only; no claim that a merged PR alone completes the RFC.
Starting points and delivery boundary
- loopx/control_plane/turn_driver
- loopx/control_plane/turn_driver/host_binding.py
- apps/desktop/loopx-control-plane
Base: latest main. Reuse the existing typed owner and provider boundaries. Include affected CLI/frontend/Lark companions; verify real entrypoints and backend where changed. Preserve existing first-screen review and maintainer merge gates. Public artifacts contain only synthetic/public-safe evidence, no private operational state. This task does not authorize provider promotion, benchmark launches, release/deployment or unrelated protected effects.
- Lenguaje dominante
- Python
- Estrellas
- 6.2k
- Forks
- 596
- Merge medio
- 7 h 47 min
- PR fusionados (30 d)
- 904
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 loopx-project/loopx
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
loopx-project/loopx#6842 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
loopx-project/loopx#6108 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
loopx-project/loopx#5688 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 60/100
loopx-project/loopx#5632 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
loopx-project/loopx#5443 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de loopx-project/loopx
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
zach-blumenfeld/aip#13 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
nathanmarlor/foxess_modbus#1287 ·
Los mantenedores suelen responder en 4 días
-
bug good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
OpenLakeForge/openlakeforge#498 ·
Los mantenedores suelen responder en 1 día
-
good first issue hacktoberfest help wanted python
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
Los mantenedores suelen responder en 1 día
-
Exact onnxruntime==1.27.0 core pin makes Pipecat-based apps uninstallable from the dashboardAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 69/100
pollen-robotics/reachy_mini#1493 ·
Los mantenedores suelen responder en 1 día