Thank you! Since a few mentioned Responses API: the reason why it wasn't implemented in 1.x is because RubyLLM 1.x effectively assumes a 1:1 mapping between pr

Thank you! Since a few mentioned Responses API: the reason why it wasn't implemented in 1.x is because RubyLLM 1.x effectively assumes a 1:1 mapping between provider and protocol. That assumption no longer holds since OpenAI has 2 protocols with different capabilities, and to access all VertexAI models we need to support a bunch under that single provider. Therefore, a major refactoring to split Protocols and from Providers was needed, as well as a way to route different models to different Protocols under the same Provider, transparently. That's one of the many things that's gonna ship with RubyLLM 2.0. If you're curious: https://github.com/crmne/ruby_llm/commit/d398354da493570b0509afe737e12b29e65907f4 https://github.com/crmne/ruby_llm/commit/d398354da493570b050... https://github.com/crmne/ruby_llm/commit/0875ce2dfeae9d28a3a37f8062ae93c227a597ec https://github.com/crmne/ruby_llm/commit/0875ce2dfeae9d28a3a...