ranade-oss fixes the front door to multi-provider AI

A pair of UI fixes makes sure firms can actually see and enter the credentials needed to use their approved AI providers.

integrationworkflow

The fork had a frustrating failure mode: key settings for major AI providers could disappear when the provider catalogue had not fully loaded. A separate mismatch also made one available OpenAI model appear unavailable.

ranade-oss fixed that gating problem in two parts of the settings experience, then added regression coverage. The practical result is more reliable setup for organisations using several model providers, rather than an admin being told a service is missing when the issue is only the interface.

The follow-up matters because it closes the same loophole in a second view, suggesting the team is checking the whole setup journey rather than treating the first report as isolated.

So what Legal-tech teams offering a choice of AI models should care because reliable credential setup is a prerequisite for governance, testing and day-to-day use.

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

Commits in this thread

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

SHA	Subject	Author	Date
`e8a23dbe`	Fix provider API-key visibility and GPT-5.6 discovery (#63)	ranade-oss	2026-07-29	↗ GitHub
* Keep core provider API key fields visible * Add API key field visibility regression test * Recognize GPT-5.6 API alias during discovery * Test GPT-5.6 alias-aware model discovery * Test GPT-5.6 alias-aware model discovery
`31f81e2f`	fix stable API key provider visibility	ranade-oss	2026-07-30	↗ GitHub
`0ed4082c`	Fix stable API key provider visibility (#68)	ranade-oss	2026-07-30	↗ GitHub
Keep API-key provider rows stable across asynchronous catalogue hydration and cover future providers with a regression test.

SHA

Subject

Author

Date

e8a23dbe

Fix provider API-key visibility and GPT-5.6 discovery (#63)

ranade-oss

2026-07-29

↗ GitHub

* Keep core provider API key fields visible

* Add API key field visibility regression test

* Recognize GPT-5.6 API alias during discovery

* Test GPT-5.6 alias-aware model discovery

* Test GPT-5.6 alias-aware model discovery

31f81e2f

fix stable API key provider visibility

ranade-oss

2026-07-30

↗ GitHub

0ed4082c

Fix stable API key provider visibility (#68)

ranade-oss

2026-07-30

↗ GitHub

Keep API-key provider rows stable across asynchronous catalogue hydration and cover future providers with a regression test.

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-902.md from inside the repo you want the changes in.