[Task][RFC]: Qualify attached and managed Agent session modes
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
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- python, typescript
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- Python
- Stelle
- 6.2k
- Fork
- 596
- Merge medio
- 7h 47m
- PR unite (30g)
- 904
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di loopx-project/loopx
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
loopx-project/loopx#6842 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
loopx-project/loopx#6108 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
loopx-project/loopx#5688 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 60/100
loopx-project/loopx#5632 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
loopx-project/loopx#5443 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di loopx-project/loopx
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
-
[Bug]: Queen's own Ollama model loses num_ctx when a running session switches to itForse già presa @anasamin26 l’ha presa oggi. Apertabug enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
aden-hive/hive#7508 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
llm translation
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
BerriAI/litellm#47884 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
bug 🐛
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
netalertx/NetAlertX#1856 · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno