Update AGENTS.md: fix proxy startup time estimate and add vitest note

- Proxy takes ~60-90s to start with default Neon DB (not 15-20s)
- Recommend /health/liveliness endpoint for readiness check
- Note that full vitest suite takes 10+ minutes; suggest file-specific runs

Co-authored-by: Krish Dholakia <krrishdholakia@gmail.com>
This commit is contained in:
Cursor Agent 2026-03-05 01:53:09 +00:00
parent e3810b4009
commit 76f73de3f0

View file

@ -242,7 +242,7 @@ Start the proxy with a config file:
poetry run litellm --config dev_config.yaml --port 4000
```
The proxy takes ~15-20 seconds to fully start (it runs Prisma migrations on boot). Wait for `/health` to return before sending requests. Without a PostgreSQL `DATABASE_URL`, the proxy connects to a default Neon dev database embedded in the `litellm-proxy-extras` package.
The proxy takes ~60-90 seconds to fully start when using the default Neon dev database (it runs Prisma migrations and a sanity-check diff on boot). Wait for `/health/liveliness` to return `"I'm alive!"` before sending requests. Without a PostgreSQL `DATABASE_URL`, the proxy connects to a default Neon dev database embedded in the `litellm-proxy-extras` package.
### Running tests
@ -267,4 +267,5 @@ Ruff is the primary fast linter. For the full lint suite (including mypy, black,
- The proxy at port 4000 serves a **pre-built** static UI from `litellm/proxy/_experimental/out/`. After making UI code changes, you must run `npm run build` in the dashboard directory and copy the output: `cp -r ui/litellm-dashboard/out/* litellm/proxy/_experimental/out/` for the proxy to serve the updated UI.
- SVGs used as provider logos (loaded via `<img>` tags) must NOT use `fill="currentColor"` — replace with an explicit color like `#000000` or use the `-color` variant from lobehub icons, since CSS color inheritance does not work inside `<img>` elements.
- Provider logos live in `ui/litellm-dashboard/public/assets/logos/` (source) and `litellm/proxy/_experimental/out/assets/logos/` (pre-built). Both locations must have the file for it to work in dev and proxy-served modes.
- UI Vitest tests: `cd ui/litellm-dashboard && npx vitest run`
- UI Vitest tests: `cd ui/litellm-dashboard && npx vitest run`
- The full vitest suite is large and can take 10+ minutes. To test specific files: `npx vitest run src/components/path/to/file.test.tsx`