ranade-oss makes API-key setup stop losing providers

The fork fixes a quiet but frustrating problem: saved credentials could vanish from view after the page finished loading.

integrationsecurity

The API Keys page had been relying on a later model-catalogue update to decide which providers to show. When that catalogue arrived incomplete, an already-expanded provider could disappear, even though its credentials still mattered.

ranade-oss now keeps a stable list of credential providers for the page itself, while the separate catalogue still controls which AI models are available. xAI and Moonshot remain visible after loading, and future providers should follow the same rule. The change also adds a test for that future-provider case.

So what Legal teams testing several AI vendors should care because account setup stays legible when a provider's model listing changes.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from ranade-oss/ROSS-RanadeOSS, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
31f81e2f fix stable API key provider visibility ranade-oss 2026-07-30 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1089.md from inside the repo you want the changes in.

⬇ Download capture-thread-1089.md