Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

session: interactive chat bypasses daily spending limit

未关闭
#1,546 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
76/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
go
领域
backend, cli

调研方向

Start in internal/session/taskcrew.go:211 and read internal/session/rail.go:58-82, then trace the callers for interactive chat and /task. Verify that the daily rail is applied consistently across interactive, task, standing-firing, and headless execution paths, using the $1.00 budget reproduction as the done check.

由索引模型根据 Issue 内容生成。

描述

area:provider area:session bug sev:critical
Summary

Interactive chat turns and /task delegations bypass the project-wide daily spending rail and only check the per-conversation limit.

Observed Behavior

When a session hits or exceeds the configured daily budget, interactive chat turns and tasks spawned from chat continue executing and consuming model spend without tripping the daily spending limit. Only headless codeaf do and standing firings enforce the daily rail.

Expected Behavior

Every execution path (interactive chat, task crew, standing firings, headless runs) must enforce the daily spend ceiling configured in the workspace/project rails.

Reproduction Steps
  1. Set daily budget rail to $1.00 via workspace config or /budget 1.
  2. Run interactive chat turns until spend exceeds $1.00.
  3. Submit a subsequent turn or /task. The session continues executing and incurring costs.
Root Cause / Location

In internal/session/taskcrew.go:211, crewSpendGuard is called with enforceDaily: false:

crewSpendGuard(..., false)

Rail checks in internal/session/rail.go:58-82 only validate per-session budgets when enforceDaily is disabled.

—
Drafted with CodeAF · reviewed and owned by the author

主要语言
Go
星标
115
派生
14
平均合并
9 小时 35 分钟
30 天内合并 PR
752

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Agent-Field/CodeAF 的其他 Issue

查看 Agent-Field/CodeAF 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。