RubyLLM 1.16: Concurrent Tool Execution, Rails-Style Instrumentation, and api_base for Every Provider

When you first reach for an LLM library, the only question is whether it works. Can it call the model, parse the response, run a tool. Once your app is actually in production, the questions change. Is it fast? Can I see what it’s doing when something goes wrong? Can I send its traffic through my own infrastructure instead of straight out to the provider? I released RubyLLM 1.16 today. It answers these production questions. The three headline features are about speed, visibility, and control: tools that run concurrently, structured events for everything RubyLLM does, and a configurable base URL for every native provider. None of them change how you write your app. All of them matter the moment real traffic shows up. Tools That Run Concurrently When a model returns several tool calls in one response, it’s telling you those calls are independent. Get the weather, look up the stock price, fetch the exchange rate. The model didn’t ask for them in order. It asked for all of them. RubyLLM…