Top
Best
New

Posted by doener 4 hours ago

RubyLLM: A Ruby framework for all major AI providers(rubyllm.com)
251 points | 36 comments
mogox 4 minutes ago|
RubyLLM is awesome! I use it on side projects. So interesting how questions and comments from last year SF Ruby conf, https://youtu.be/y535u1EWqAg?si=rbyv52T035apKwQk are already features shipped in the ecosystem.
swe_dima 4 hours ago||
I found Ruby LLM to be surprisingly good - in terms of usability it's close to Vercel's AI framework.

It tries to strike a balance between working out of the box and being flexible... which has its challenges, still nice overall.

One big real-life pain I experienced is that caches don't always work, e.g. for xAI, since it only supports completions API and thought signatures are returned wrong.

earcar 3 hours ago||
Thank you!

Responses API is now implemented and it's coming in RubyLLM 2.0

https://github.com/crmne/ruby_llm/blob/main/lib/ruby_llm/pro...

techscruggs 3 hours ago||
Do you have any details published around 2.0? Would love to learn more.
earcar 3 hours ago||
Not yet. I'll do a series of blog posts and tweets in the next weeks.
curtisboortz 45 minutes ago||
[flagged]
obiefernandez 2 hours ago||
I have an open source gem called Raix that builds on top of RubyLLM's abstractions and is quite popular. https://github.com/OlympiaAI/raix
Finbarr 3 hours ago||
RubyLLM is very easy to use. Made extensive use of it for a project last year. Drawbacks are it was difficult to instrument for true trace observability and it has a pattern where retries will delete the underlying models so the history you see is clean but not necessarily great for seeing exactly what the sequence of API calls was.
earcar 3 hours ago|
Glad you like it.

Rails-style instrumentation landed in 1.16.0.

https://rubyllm.com/instrumentation/

MitziMoto 57 minutes ago||
We use and love RubyLLM! A wonderful and easy to use framework.

Agreed with another commenter on the frustration with the responses API not being naively supported; that seems like a huge miss. There is a connector from another dev, but it's buggy and not as high quality as the main gem.

Really looking forward to future development and especially 2.0!

Edit: Just saw that responses API is now native? I will definitely check that out.

earcar 36 minutes ago|
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/d398354da493570b050... https://github.com/crmne/ruby_llm/commit/0875ce2dfeae9d28a3a...

rohitpaulk 1 hour ago||
We use RubyLLM in production too, the most elegant library in this space I've seen so far.

I also liked how they run the issue tracker. If you select "Feature Request", it makes you explain how you explored workarounds, why you believe it belongs in RubyLLM etc to prevent scope creep.

digitaltrees 2 hours ago||
We use this in production for a few apps. Great project.
zhisme 3 hours ago||
thank you for bringing ruby into AI community and your open-source work. Great language must be explored and get more attention :)
earcar 3 hours ago|
Thank you!

I love how MINASWAN Hacker News is when talking about Ruby!

themcgruff 3 hours ago||
I built a similar Ruby based agent development kit that has a different focus and feature set:

https://github.com/tweibley/legate

aniokono 1 hour ago|
I haven't tried it but it looks promising.
More comments...