AI Signal 543
llm 0.33 upgrades OpenAI Python library to 3.x and replaces httpx with httpx2
Illustration only Photo by Vishnu Mohanan on Unsplash
The command-line tool llm 0.33 migrates to OpenAI Python library 3.x and switches its HTTP client from httpx to httpx2 while adding per-call API key support for embeddings
Engineers using llm for local or CI-based LLM workflows must update dependencies and may need to adjust embedding plugins. The HTTP client change could affect performance or compatibility with proxies and firewalls. Per-call key support simplifies multi-provider embedding pipelines without breaking existing plugins.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
OpenAI Python library upgraded to 3.x and HTTP client switched from httpx to httpx2
Embedding commands and methods now accept per-call API keys without altering shared model state
Template chaining and reasoning summary options added for OpenAI Responses API compatibility
THE READ
What the cluster adds up to.
The upgrade to OpenAI Python library 3.x and the switch from httpx to httpx2 are breaking changes for any downstream code that pins exact versions or relies on specific HTTP client behavior. Teams using llm in CI pipelines or automated workflows will need to test their scripts against the new dependencies, particularly if they interact with custom endpoints or proxies. The HTTP client change may also affect connection pooling, timeouts, or error handling, which could surface in edge cases like rate limiting or network interruptions.
Per-call API key support for embeddings introduces a more flexible way to route requests to different providers without modifying the global configuration. This is useful for multi-tenant setups or experiments where different keys are needed for different embedding models. Existing plugins that read `self.key` will continue to work due to a compatibility fallback, but new plugins should use the `key=` parameter to avoid future deprecation. The change does not affect regular LLM model calls, which already supported per-call keys.
Template chaining via repeated `-t/--template` flags allows combining model configurations and prompts from separate templates. This reduces duplication in workflows where the same model settings are reused across multiple prompts. The reasoning summary option for OpenAI Responses API models provides a way to control the verbosity of outputs, which is particularly useful when testing or comparing models that mimic the OpenAI API. These features are additive and do not require immediate adoption but may simplify complex workflows over time.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER