Sub-team manager naming its own team in team_post gets a misleading refusal
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start in internal/session/tools_team.go:185-201 and trace how teamTarget matches the requested team and builds its refusal. Reproduce the beta manager's team_post call from the issue using the documented dev build and isolated profile. Done means the e2e call identifies beta as the caller's own team and product as the correct target.
由索引模型根据 Issue 内容生成。
描述
Seen on: dev 837b2b0.
Behaviour
A sub-team manager (@betalead, manager of beta, member of product) called team_post {"to":"manager","team":"beta"} and was told There is no one team called "beta" here. Yours are: "product"., although beta exists and it runs it. The retry with team: "product" worked. The refusal should explain the rule, for example you manage "beta"; team_post is for the team above you, "product".
Replication
- Build dev 837b2b0 (
git checkout 837b2b0 && make build, binarybin/codeaf), or install the dev build withcurl -fsSL https://agentfield.ai/get/devaf | bash. - Use an isolated profile:
export HOME=$(mktemp -d), exportOPENROUTER_API_KEY, and keep the default model (~deepseek/deepseek-v4-flash-latest, crew on auto). - On a busy machine set
task.max_loadto0(/settings, Tasks) so the busy-machine gate does not hold tasks. cd $(mktemp -d) && git init -q && codeaf; make a teamproductwith a manager, and ask it to start a sub-teambetawith a manager.- Ask the beta manager:
Post to your manager with team_post, naming team beta.
Evidence
- Tool result:
There is no one team called "beta" here. Yours are: "product". internal/session/tools_team.go:185-201: the name is matched only againstfits(the member roles), and the refusal lists only those.
Guessed cause
A guess from reading the code, not a confirmed diagnosis. teamTarget filters to member roles before matching the name, so a team the caller manages reads as unknown.
Acceptance
- e2e: the call above returns a refusal that names
betaas the caller's own team andproductas the right target.
Found while writing the public docs; manual text differences are in #1545.
🤖 Generated with Claude Code
- 主要语言
- 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
-
难度 2/5 1-3 小时 新手友好度 88/100
gruntwork-io/boilerplate#329 ·
-
难度 2/5 1-3 小时 新手友好度 65/100
prime-radiant-inc/evener#3291 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
Netcracker/qubership-apihub-backend#582 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 1 天内回复