-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Allow to set a token limit for a task #3012
Copy link
Copy link
Open
Labels
area:configurationConfig files, instruction files, settings, and environment variablesConfig files, instruction files, settings, and environment variablesarea:sessionsSession management, resume, history, session picker, and session stateSession management, resume, history, session picker, and session state
Description
Metadata
Metadata
Assignees
Labels
area:configurationConfig files, instruction files, settings, and environment variablesConfig files, instruction files, settings, and environment variablesarea:sessionsSession management, resume, history, session picker, and session stateSession management, resume, history, session picker, and session state
Type
Fields
Give feedbackNo fields configured for Feature.
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:
Example prompts or workflows
No response
Additional context
No response