Model-Specific Spending Limits
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
Model-Specific Spending Limits
Provide the ability to set separate spending limits for individual models, alongside an overall account budget. For example, an organization could limit Opus to $100/month, Luna to $300/month, while maintaining a total budget cap of $500/month. This would provide better cost control while still allowing access to premium models when needed.
---
| Field | Value |
| --- | --- |
| App version | 1.1.8 |
| OS | Windows 10.0.26100 |
| Theme | Rainglow Codecourse |
| Path | /chat |
| Tenure | Week 9 |
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the existing account-budget and model-selection flows, then determine how usage is measured and where limits are enforced. Done should include independent monthly limits for each model while preserving an overall account cap, with tests covering both limits.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100