docs: refactor budgets - #332
Conversation
PR Preview Ready!Your preview documentation is ready! Visit it here: Preview URL: http://codemie-docs-pr-previews.s3-website.eu-central-1.amazonaws.com/pr-332/ This preview will be automatically updated when you push new commits to this PR. |
|
|
||
| :::info | ||
| Only one budget is charged per request: | ||
| Only one budget is charged per request. The category is resolved automatically by request type: |
There was a problem hiding this comment.
by model in request? guess request type is the same for prem/non-prem
| - Non-premium model + CLI request → CLI budget | ||
| - Non-premium model + UI request → Platform budget | ||
| ::: | ||
| - Premium model → **Premium Models** (regardless of source: UI or CLI) |
There was a problem hiding this comment.
Premium models are charged to prem budget only for CLI. Opus in UI will be charged via regular platform budget
| - Non-premium model + UI request → **Platform** | ||
|
|
||
| Category is resolved automatically per request. If a project budget exists for the resolved category, it takes precedence over the user's global budget. | ||
| For details on how project membership affects category resolution, see [Budget Priority](#budget-priority). |
There was a problem hiding this comment.
I would leave initial phrase as is just add a link
| │ CLI │ Web UI | ||
| ▼ ▼ | ||
| CLI budget Platform budget | ||
| <div |
There was a problem hiding this comment.
Why do we need this inline js script if we already have zoom capability for regular images? Especially when it's opens image as blob instead of zooming (and user cannot get back) – blob:http://codemie-docs-pr-previews.s3-website.eu-central-1.amazonaws.com/d7847ba8-0011-4fe7-b91b-378907f0d301
| > | ||
|
|
||
| ```mermaid | ||
| flowchart LR |
There was a problem hiding this comment.
I would replace it as SVG diagram to keep consistency across docs
|
|
||
| ```mermaid | ||
| flowchart LR | ||
| A([User request]) --> B{"Premium model?<br/>LITELLM_PREMIUM_MODELS_ALIASES"} |
There was a problem hiding this comment.
is model name in LITELLM_PREMIUM_MODELS_ALIASES backend parameter?
| | 8 | All three defaults + personal Premium | ✅ Default Platform | ✅ Default CLI | ✅ Personal Premium | | ||
| | # | Budget | Platform request | CLI request | Premium model request | | ||
| | --- | ---------------------------------------------------- | --------------------------------------------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------- | | ||
| | 1 | Default: Platform only | ✅ Default Platform (individual counter per user) | ❌ Blocked — no CLI budget | ❌ Blocked — no Premium budget | |
There was a problem hiding this comment.
I'm not sure that this works in this way
| | Getting started | Create default budgets for all three categories (Platform, CLI, Premium) — otherwise users without a personal budget will be blocked in uncovered categories | | ||
| | Team cost control without blocking individual members | Create a project budget with **Enforce member spend limits = Disabled** — the overall limit is controlled at the team level without blocking individual members | | ||
| | Strict per-user control within a project | Enable **Enforce member spend limits** — each member receives a fixed quota with blocking on overspend | | ||
| | VIP users / team leads | Use Override with **Enforce member spend limits** enabled to individually increase a specific member's quota | |
2 participants
Summary
Update Budget management docs
Testing
npm startQuality Checks
npm run checkpasses (typecheck + lint + commitlint)<text>must be`<text>`)static/img/)