Fixed. The dashboard's usage breakdown was reading the raw internal model name from LiteLLM's spend logs instead of our provider/model alias — so GreenPT and PublicAI models showed as bare upstream slugs (glm-5.3-flash, swiss-ai/apertus-v1.5-70b) and pre-rename Tinfoil rows didn't reflect the tinfoil/ prefix.
The portal now prefers the model_group field (which carries our provider/model naming), falling back to the raw name only for old rows that predate the alias convention. Verified against a live member's usage data: models now display as greenpt/green-r, publicai/apertus-v1.5-8b, tinfoil/gpt-oss-120b, etc.
Deployed to the portal (commit 2ff8193) — no dashboard-side change was needed, since it renders whatever the portal sends.
Fixed. The dashboard's usage breakdown was reading the raw internal model name from LiteLLM's spend logs instead of our `provider/model` alias — so GreenPT and PublicAI models showed as bare upstream slugs (`glm-5.3-flash`, `swiss-ai/apertus-v1.5-70b`) and pre-rename Tinfoil rows didn't reflect the `tinfoil/` prefix.
The portal now prefers the `model_group` field (which carries our `provider/model` naming), falling back to the raw name only for old rows that predate the alias convention. Verified against a live member's usage data: models now display as `greenpt/green-r`, `publicai/apertus-v1.5-8b`, `tinfoil/gpt-oss-120b`, etc.
Deployed to the portal (commit `2ff8193`) — no dashboard-side change was needed, since it renders whatever the portal sends.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The user dashboard needs to update the model list to the current naming convention.
Fixed. The dashboard's usage breakdown was reading the raw internal model name from LiteLLM's spend logs instead of our
provider/modelalias — so GreenPT and PublicAI models showed as bare upstream slugs (glm-5.3-flash,swiss-ai/apertus-v1.5-70b) and pre-rename Tinfoil rows didn't reflect thetinfoil/prefix.The portal now prefers the
model_groupfield (which carries ourprovider/modelnaming), falling back to the raw name only for old rows that predate the alias convention. Verified against a live member's usage data: models now display asgreenpt/green-r,publicai/apertus-v1.5-8b,tinfoil/gpt-oss-120b, etc.Deployed to the portal (commit
2ff8193) — no dashboard-side change was needed, since it renders whatever the portal sends.