You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the release of the official client at https://github.com/openai/openai-go, it has become evident that feature development for OpenAI as an LLM provider will now be prioritized within their own official SDK. Given this shift, does there remain a compelling need for a community-maintained unofficial client if it merely replicates efforts to support OpenAI in Go?
Should the community-driven project pivot away from treating OpenAI as the sole de facto standard and instead actively champion broader compatibility with OpenAI-Compatible APIs—particularly those incorporating non-standard extensions, even when divergent from the original OpenAI API specification? Consider, for instance, Deepseek’s unique implementation of reasoning capabilities or the nuanced features of OpenRouter, which integrates a vast ecosystem of models each with distinct idiosyncrasies.
I observe several incomplete tasks within this project:
Could this already represent the project’s evolving trajectory—perhaps one I have yet to fully grasp from its current documentation? It would be highly beneficial if the project's long-term vision and goals were articulated with greater clarity. Are there any formal plans in place to accommodate non-standard API extensions, especially as they emerge across diverse model providers?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
With the release of the official client at https://github.com/openai/openai-go, it has become evident that feature development for OpenAI as an LLM provider will now be prioritized within their own official SDK. Given this shift, does there remain a compelling need for a community-maintained unofficial client if it merely replicates efforts to support OpenAI in Go?
Should the community-driven project pivot away from treating OpenAI as the sole de facto standard and instead actively champion broader compatibility with OpenAI-Compatible APIs—particularly those incorporating non-standard extensions, even when divergent from the original OpenAI API specification? Consider, for instance, Deepseek’s unique implementation of reasoning capabilities or the nuanced features of OpenRouter, which integrates a vast ecosystem of models each with distinct idiosyncrasies.
I observe several incomplete tasks within this project:
And many more along similar lines.
Could this already represent the project’s evolving trajectory—perhaps one I have yet to fully grasp from its current documentation? It would be highly beneficial if the project's long-term vision and goals were articulated with greater clarity. Are there any formal plans in place to accommodate non-standard API extensions, especially as they emerge across diverse model providers?
Beta Was this translation helpful? Give feedback.
All reactions