nipunbatra8 bets the whole stack on OpenAI

This fork tears out its Claude and Gemini support and standardizes on a single AI provider - OpenAI - for everything.

infrastructureintegration

nipunbatra8 made a clean directional call: instead of letting the app talk to several AI vendors, it now speaks only to OpenAI. The old multi-provider plumbing - and the user-facing controls for picking between models - are gone, replaced by a short menu of current OpenAI models and a single API key for the whole server.

It's a commitment, not an experiment, touching twenty-odd files. Two things to watch if you're evaluating it: the work to let each user bring their own key looks half-finished, so every request currently runs on one shared key, and one of the higher-end reasoning models on offer appears misconfigured and may fail at runtime. Worth a look on GitHub if you're weighing whether to consolidate on one vendor - and a caution if you're not.

So what Relevant to any legal-tech team debating whether to standardize on a single AI vendor versus keeping providers swappable.

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 nipunbatra8/legalos, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
663c3130 migrate to openai nipunbatra8 2026-05-23 ↗ 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-563.md from inside the repo you want the changes in.

⬇ Download capture-thread-563.md