Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[Task][RFC]: Qualify attached and managed Agent session modes

オープン
  • 何か問題がありますか？
#5,200 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
python, typescript
領域
api, backend, desktop

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

direction/architecture-evolution

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

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.

主要言語
Python
スター
6.2k
フォーク
596
平均マージ
7時間 35分
マージ済み PR（30日）
928

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

loopx-project/loopx のほかの issue

loopx-project/loopx の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。