Allow to set a token limit for a task
- 主要语言
- Shell
- 星标
- 11.2k
- 派生
- 1.9k
- 平均合并
- 14 小时 16 分钟
- 30 天内合并 PR
- 6
描述
### Describe the feature or problem you'd like to solve
Currently each request consumes a certain predicable amount of premium requests - this will change soon and make it completely unpredictable, a task might accidently eat up thwo whole budget for a month.
### Proposed solution
With the upcoming https://github.blog/news-insights/company-news/github-copilot-is-moving-to-usage-based-billing/ it becomes completely unpredictable how much costs a request possibly consumes.
It would therefore be good to set a limit per session / request. If the limit is approached, copilot should ask for confirmation what to do that could be:
1. Complete as soon as possible with what was already accomplished
2. Continue with an increased budget
3. ....
### Example prompts or workflows
_No response_
### Additional context
_No response_
贡献指南
调研方向
未指定任何文件、测试或入口点。首先定位 CLI 中的任务和会话请求处理,然后明确 token 限制和确认选项应如何工作。完成的标准是:对请求或会话实施了该限制,并且测试覆盖了提议的预算响应。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- shell
- 领域
- cli
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 冷清
- 描述清晰度
- 需要澄清
- 新手友好度
- 35/100