teams: manager conversation initialization, handle fallback, and approval posture inheritance
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Read the manager initialization and registration paths under internal/session, then inspect internal/session/team_start.go and internal/session/consent.go. Trace how handles, approval posture, and consentRule formatting are passed during team_start. Done means fallback handles are registered, child meta.json inherits approval posture, and the consent card shows the full cost and lifecycle wording.
由索引模型根据 Issue 内容生成。
描述
Summary
Team manager initialization fails to generate handles on untitled new conversations, omits approval posture inheritance during team_start, and renders incorrect consent card wording.
Items & Observed Behavior
- Empty handle on new top-level manager conversation: Creating a new top-level manager conversation via
Mleaves the conversation without a title until the first turn runs. Handle derivation falls back to empty, preventing global managers from routing messages to it viateam_send. - Approval posture not inherited in
team_start: When a manager creates a sub-team withteam_start, the new team manager'smeta.jsondoes not inherit the parent manager's"approval"posture, reverting instead to the profile default (e.g.ask). - Consent card wording mismatch: The
team_startconsent card renders the literal rule word"default"instead of the cost warning clause ("a new conversation; it spends until it stops").
Expected Behavior
- Untitled manager conversations should receive a deterministic fallback handle derived from role and creation timestamp.
- Sub-teams spawned via
team_startmust inherit the initiating manager's approval posture unless explicitly overridden. - The consent card must display the full cost and lifecycle description rather than internal configuration keywords.
Root Cause / Location
internal/session: Manager handle derivation andteams.jsonregistration.internal/session/team_start.go: Missing posture propagation from caller session to childmeta.json.internal/session/consent.go:consentRulefallback formatting.
—
Drafted with CodeAF · reviewed and owned by the author
- 主要语言
- Go
- 星标
- 115
- 派生
- 14
- 平均合并
- 9 小时 44 分钟
- 30 天内合并 PR
- 766
环境准备
我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Agent-Field/CodeAF 的其他 Issue
-
area:chat bug sev:papercut
难度 2/5 1-3 小时 新手友好度 86/100
Agent-Field/CodeAF#1592 ·
维护者通常 1 天内回复
-
area:headless bug sev:critical
难度 2/5 1-3 小时 新手友好度 88/100
Agent-Field/CodeAF#1566 · 已指派 1 人 ·
维护者通常 1 天内回复
-
area:chat feature
难度 2/5 1-3 小时 新手友好度 88/100
Agent-Field/CodeAF#1510 ·
维护者通常 1 天内回复
-
area:tests bug
难度 2/5 1-3 小时 新手友好度 82/100
Agent-Field/CodeAF#1489 ·
维护者通常 1 天内回复
-
area:chat bug good first issue sev:papercut
难度 2/5 1-3 小时 新手友好度 78/100
Agent-Field/CodeAF#1470 ·
维护者通常 1 天内回复
查看 Agent-Field/CodeAF 的全部 Issue
相似的 Issue
-
automation models
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
txn2/mcp-data-platform#1984 ·
维护者通常 1 天内回复
-
agentic-workflows
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
kind/docs prio/P2
难度 1/5 1 小时以内 新手友好度 95/100
agent-substrate/substrate#1986 ·
维护者通常 1 天内回复