It seems this library came out before OpenAI released their official Ruby library, but that's been out for awhile now. Unfortunately these two libraries directly conflict with one another.

If you add both "openai" and "ruby-openai" to your Gemfile, whichever one gets loaded first will predominate. Both libraries use require "openai" as their convention making them incompatible. I would have expected that this one would use require "ruby-openai" which would have enabled some possibility of using both. And that's the desired solution here: change the require path for this to match its own gem name.

The trouble is that I'm in a codebase which is using this library and I'm trying to cut over to the official client library instead. However it's impossible to do any sort of phased rollout because of this compatibility issue. As things stand, I have to do a hard cutover or nothing.