mirror of
https://github.com/BerriAI/litellm.git
synced 2026-10-16 04:29:31 +00:00
e2276ac2b9
* feat(ui): announce decision model support in Models + Endpoints * feat(ui): make decision models findable, callable, and testable from the Admin UI Add Model provider search now matches decision model names and shows a note on where to call a decision model. The banner links to the docs and opens Add Model. The System One playground defaults to /v1/systemone with a picker of the proxy's decision models, and the model hub shows a /v1/systemone usage example for evaluation models. * fix(ui): keep the admin signed in when a typed virtual key cannot list decision models The System One playground looked up a typed virtual key's decision models through the dashboard's shared request client, so an expired key signed the admin out, and typing a key by hand sent one lookup per keystroke. The lookup now uses the same client as Send, against the same proxy, and waits for typing to stop * fix(ui): hide decision model Playground links from view-only sessions A proxy admin viewer cannot open the Playground, so the Models + Endpoints decision models banner and the AI Hub's Try it in the Playground link sent them to an Access Denied page. Hide both for view-only sessions. * fix(ui): send the AI Hub decision example's key in the proxy's configured header A proxy with litellm_key_header_name set reads keys only from that header, so the example's hardcoded Authorization header was rejected. Use the header name the dashboard already reads from the session. * fix(ui): stop the decision model notice from ruling out /chat/completions for dual-mode models * fix(ui): point only users who can add models at Add Model in the decision models banner --------- Co-authored-by: moyai-devin-berriai[bot] <336287033+moyai-devin-berriai[bot]@users.noreply.github.com> Co-authored-by: mateo-berri <277851410+mateo-berri@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| .agents/skills/url-state | ||
| public | ||
| scripts | ||
| src | ||
| tests | ||
| vendor | ||
| .env.development | ||
| .env.production | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| AGENTS.md | ||
| build_release_ui.sh | ||
| build_ui.sh | ||
| build_ui_custom_path.sh | ||
| components.json | ||
| eslint-budgets.json | ||
| eslint-suppressions.json | ||
| eslint.config.mjs | ||
| knip.json | ||
| next.config.mjs | ||
| package-lock.json | ||
| package.json | ||
| postcss.config.js | ||
| README.md | ||
| tsconfig.json | ||
| tsconfig.production.json | ||
| vitest.config.ts | ||
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Inter, a custom Google Font.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.