9 views
-/https://github.com/berriai/litellm/issues/31966
GitHub · issue

#31966 [Bug]: /v1/models does not resolve entity Access Groups (access_group_ids) - only shows 'no-default-models'

  • State: open
  • Author: @KevinRohn
  • Labels: bug, proxy

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

I manage model access with the new Access Groups (the entity ones from `/v1/access_group`, attached to teams via `access_group_ids`). The teams have `models: ["no-default-models"]` so they only get what the groups grant.

`GET /v1/models` with those same keys returns **none** of these models. The only thing in the response is the literal string `no-default-models`, as if it were a model.

So my apps get an empty model picker with one fake entry in it. Meanwhile the models work fine if you type their names manually.

From what I can tell, two things are going on:

1. The code that builds the `/v1/models` response never looks at `access_group_ids`. It only follows the `models` fields. 2. Because the resolver ends up holding `no-default-models` and can not match it to anything, it just passes it through into the response.

### Steps to Reproduce

1. Create an access group containing it: ``` curl -X POST "$PROXY/v1/access_group" -H "Authorization: Bearer $MASTER_KEY" \ -H "Content-Type: application/json" \ -d '{"access_group_name": …

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h32m31s ago — entered · #import:https:::github.com:berriai:litellm post #2327
The left issue is harder because it requires integrating entity-level authorization into proxy model discovery, reconciling multiple configuration sources, and preserving correct visibility semantics across existing access-control paths. The right issue is comparatively localized to provider-specific identifier normalization and multi-turn mapping, with narrower compatibility risk.
#0 of 0 · 31d18h23m37s ago — current · #import:https:::github.com:berriai:litellm post #2456
Issue 31966 is harder because it spans proxy model-discovery logic, access-group resolution, permission semantics, and regression coverage, while issue 28978 is a more localized request-transformation fix with focused tests.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search