0.5.0 splits llm4s into modules. llm4s-core is a provider-free spine; each provider, RAG, memory, MCP, speech, image,
observability, the agent runtime and the built-in tools are separate artifacts, and a provider is registered by adding
its dependency, so a build carries only what it uses.
What is new
- Modules: a provider-free
llm4s-core, and one artifact per provider and per concern (RAG, memory, MCP, speech, image, observability, the agent runtime, the built-in tools), with a BOM,llm4s-bom, that pins them all. - Agent runtime: rebuilt on a typed graph kernel with durable checkpoints, run claims, human review and a Deep Agents-style harness (permissions, todos, semantic memory, replay-safe effects).
- Integrations: Java, Kotlin, Spring Boot, cats-effect, ZIO and Pekko.
- Providers: Bedrock, watsonx, Jina, Cohere embeddings and a generic OpenAI-compatible provider.
- Workload identity, configurable timeouts and testkits.
Upgrading
0.5.0 is a breaking release: dependencies, configuration and API keys change. Start with Upgrading from 0.4.1 to 0.5.0, which groups everything to change by what you use. 0.5.0 sets no binary-compatibility (MiMa) baseline; that comes at a later pre-1.0 release once the designs are final (compatibility policy).
Install
libraryDependencies ++= Seq(
"org.llm4s" %% "llm4s-core" % "0.5.0",
"org.llm4s" %% "llm4s-openai" % "0.5.0" // or the provider module you use
)
Every artifact, with its tier: installation guide.
Known issue: org.llm4s:llm4s-kotlin-api:0.5.0 was never published (the release’s Kotlin publishing job stopped at
a version check, #1968). Every Scala and Java artifact is on Maven
Central. llm4s-kotlin-api is not on Maven Central yet: build it locally, as the
installation guide describes.
Full list of changes: CHANGELOG · GitHub release