Default per-team cap also caps All teams, so the whole org shares one pool
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Read internal/tui3/teamspage.go:532-545 and internal/tui3/teamspagedraw.go:417-424, then run the isolated-profile reproduction with a $2 daily cap per team. Done means each of three top-level teams has its own cap and the organization can spend up to $6, with the possessive rendered as "All teams' cap"; verify the stated e2e and unit acceptance.
由索引模型根据 Issue 内容生成。
描述
Seen on: dev 837b2b0.
Behaviour
With daily cap per team $2, every top-level team showed $0.18 of $2 today · All teams's cap, and the whole org stopped at $2.01. A per-team default should give each team its own $2, not one $2 pool for the company. The line also has a grammar slip: All teams's.
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./settings, setdaily cap per teamto$2.- Make three top-level teams, each with a manager, and give each a job.
- On
/teams, read each team's money line.
Evidence
- Screen:
$0.18 of $2 today · All teams's capon every top-level team; work stopped at $2.01 in total. internal/tui3/teamspage.go:532-545(teamsPool): when the cap is the profile default, the pool owner is "the top of the chain", which isAll teams.internal/tui3/teamspagedraw.go:417-424:name + "'s cap"withname = teamstore.RootName.
Guessed cause
A guess from reading the code, not a confirmed diagnosis. The root team inherits the profile default like any team, and the effective-cap resolver makes the default a pool owned by the top of the chain.
Acceptance
- e2e: with
daily cap per team $2and three top-level teams, each showsof $2 todayagainst its own spend, and the org can spend up to $6. - Unit: the possessive is rendered as
All teams' cap.
Found while writing the public docs; manual text differences are in #1545.
🤖 Generated with Claude Code
- 主要语言
- Go
- 星标
- 115
- 派生
- 14
- 平均合并
- 9 小时 35 分钟
- 30 天内合并 PR
- 752
环境准备
我们还没有检查这个项目的环境配置文件。先看它的 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 天内回复
-
area:chat bug sev:critical
难度 2/5 1-3 小时 新手友好度 82/100
Agent-Field/CodeAF#1548 · 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 天内回复
查看 Agent-Field/CodeAF 的全部 Issue
相似的 Issue
-
bug needs triage
难度 2/5 1-3 小时 新手友好度 78/100
netdata/netdata#24062 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
meshery/meshery#22119 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
automation documentation
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复