[Task][RFC]: Complete App conversations and reusable asynchronous work delivery
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- python, typescript
调研方向
Read the linked RFC and coordinate with the existing owners of #4339 and #3786; the issue says implementation and integration overlap active work. Start by inspecting loopx/chat_server.py, loopx/control_plane/collaboration, and the personal-workspace dashboard entry point to identify an unowned acceptance gap before claiming work. Done means the agreed scope passes the listed journey checks and its integrated revision, commands, and test evidence are recorded here.
由索引模型根据 Issue 内容生成。
描述
Outcome / 目标
让 App 会话完整承接异步工作。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: S1/S3/S5 · R1–R3, 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.
Conversation ingress and result-return work are partially shipped, including #5170. #5139, #5130 and #5106 are open at this audit for recovery and GoalRef integration; their changes are not assumed merged.
Work remaining
- Deliver the RFC’s nearest exit: an ordinary App request reaches a qualified existing owner, accepts correction, survives interruption and returns a checked artifact to the original conversation.
- Converge reusable inbox pending/replay/disposition rules in the existing TS owner while provider authentication, addressing and formatting stay in the adapter.
Ownership and ongoing work
Implementation is already active. Coordinate on the existing PRs instead of opening a competing inbox/session store. #4339 owns semantic handoff; #3786 owns shared presentation. This issue is the RFC-level delivery record.
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
- Test managed and attached entrypoints, reconnect, stop, duplicate delivery and a late return after the active session changes.
- Distinguish accepted, deferred, failed, running and delivered from actual receipts; no manual owner lookup or manual result relay in the qualified journey.
- Packaged frontend and CLI independently read back the same request, owner, revision, disposition and result.
- 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/chat_server.py
- loopx/control_plane/collaboration
- apps/presentation/dashboard/src/features/personal-workspace
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
- 平均合并
- 6 小时 33 分钟
- 30 天内合并 PR
- 905
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
loopx-project/loopx 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 84/100
loopx-project/loopx#6842 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
loopx-project/loopx#6108 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
loopx-project/loopx#5688 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 60/100
loopx-project/loopx#5632 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
loopx-project/loopx#5443 · 1 条评论 ·
维护者通常 1 天内回复
查看 loopx-project/loopx 的全部 Issue
相似的 Issue
-
wr.dynamodb.read_items returns [{}] for a single partition value that does not exist可能已有人在做 @auraseb 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 84/100
aws/aws-sdk-pandas#3520 ·
维护者通常 2 天内回复
-
requires triage typing
难度 2/5 1-3 小时 新手友好度 78/100
sqlalchemy/sqlalchemy#13704 ·
维护者通常 1 天内回复
-
Edit tool converts CRLF files to LF可能已有人在做 @RaphaelFakhri 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 68/100
huggingface/tau#774 ·
维护者通常 1 天内回复
-
show ignores the row limit when a column or table name contains "limit"可能已有人在做 @RaphaelFakhri 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
linebender/resvg#1179 · 1 条评论 ·
维护者通常 2 天内回复