standing: place scoping mismatch for project orders, stale budget on consent card, and activity label
维护者通常 1 天内回复
@santoshkumarradha 已经在做这个了。
开始于 2026年9月27日。
评估
调研方向
Start by reading the three named files: internal/tui3/place_standing.go, internal/tui3/standmark.go, and internal/tui3/standing_history.go. Trace project scoping, budget retrieval, and action-kind formatting from their current entry points. Done means project-scoped orders appear in the active project sections, consent cards show the live daily ceiling, and task activity rows use task:.
由索引模型根据 Issue 内容生成。
描述
Summary
Standing order management suffers from project directory scoping mismatches in /standing, displays stale daily budget allocations, and mislabels task execution activity rows.
Items & Observed Behavior
- Project standing orders categorized as external: Standing orders created with "for this project" scope are listed under
in other projectson/standing, and the chat side column omits the active project standing section. - Stale budget figures in standing consent cards: After updating the daily allowance via
/budget <amount>, the standing consent card continues quoting the startup default ("shares the day's $50.00 allowance"). - Mislabeled activity row for task actions: When a standing firing triggers a task execution (
does.kind == "task"), the activity history row displayssaid:instead oftask:.
Expected Behavior
- Standing orders scoped to the active project must appear under the current project heading and in the side column.
- Consent cards must read the live rail configuration for daily budget ceilings.
- Activity rows must display the correct verb matching the action type (
task:for delegated tasks).
Root Cause / Location
internal/tui3/place_standing.go: Project path normalization and scoping filter.internal/tui3/standmark.go: Static budget caching in consent card rendering.internal/tui3/standing_history.go: Action kind formatting switch.
—
Drafted with CodeAF · reviewed and owned by the author
- 主要语言
- Go
- 星标
- 115
- 派生
- 14
- 平均合并
- 13 小时 12 分钟
- 30 天内合并 PR
- 321
环境准备
我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Agent-Field/CodeAF 的其他 Issue
-
area:chat bug sev:papercut
难度 2/5 1-3 小时 新手友好度 68/100
Agent-Field/CodeAF#1805 ·
维护者通常 1 天内回复
-
area:session bug sev:papercut
难度 2/5 1-3 小时 新手友好度 82/100
Agent-Field/CodeAF#1779 ·
维护者通常 1 天内回复
-
area:session bug sev:papercut
难度 2/5 1-3 小时 新手友好度 78/100
Agent-Field/CodeAF#1768 ·
维护者通常 1 天内回复
-
area:chat bug sev:papercut
难度 2/5 1-3 小时 新手友好度 78/100
Agent-Field/CodeAF#1742 ·
维护者通常 1 天内回复
-
area:build bug sev:papercut
难度 2/5 1-3 小时 新手友好度 88/100
Agent-Field/CodeAF#1679 ·
维护者通常 1 天内回复
查看 Agent-Field/CodeAF 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
QuantumNous/new-api#7839 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
puppe1990/amarra-cais#355 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 72/100
Gentleman-Programming/engram#1899 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复