Zach Grimaldi

> I also use [LibreChat](https://github.com/danny-avila/LibreChat) - A really great open source. In its configuration I also use Azure credentials with the same input as in Void: instanceName, version & apiKey...

@yuvalsmart - can you give my PR #595 a test see if it works for you?

bunx doesn't work either for me. notably just `bun add @radix-ui/react-switch` gets stuck

Added [PROVIDER_DEVELOPMENT_GUIDE.md](https://github.com/zpg6/void/blob/feat/model-provider/PROVIDER_DEVELOPMENT_GUIDE.md) to guide contributors into the pit of success. Includes a scaffolding script for new providers to make it even easier.

@andrewpareles / @vrtnis any feedback on this so far? See [PROVIDER_DEVELOPMENT_GUIDE.md](https://github.com/zpg6/void/blob/feat/model-provider/PROVIDER_DEVELOPMENT_GUIDE.md). All that's left is to hook up to the settings and onboarding ui

> looks neat! was yaml/json support ever intended for this pr? ( I think we are just including the TS-only path for v1 and potentially adding manifest loading later, right?......

> Any chance we can push for movement on this? This is blocking #596 I am waiting for feedback on this proposal from core maintainers before I implement the rest...

One shortcoming of this approach is that it assumes `modelName` and `deployment` are the same. The **Deployment Name** textbox on Azure Portal defaults to the name of the model, but...

> I think we can just not set deploymentName here, if we're just setting it to modelName, right? @andrewpareles you get a 404 if you don't specify the deployment name....

Also a fan of ```typescript type ModelProvider = { initialize: (config: ProviderConfig) => Promise; sendChat: (params: ChatRequestParams) => Promise; sendFIM?: (params: FIMRequestParams) => Promise; listModels?: () => Promise; abort: ()...