Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#5,200 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
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 分钟
30 天内合并 PR
928

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

loopx-project/loopx 的其他 Issue

查看 loopx-project/loopx 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。