LLM library upgrade breaks httpx-dependent plugin, developers fix llm-tools-datasette

In late October, the LLM community learned that a routine upgrade to the httpx HTTP client in the LLM framework had inadvertently disabled a popular plugin, llm-tools-datasette, until a patch was applied.

Key points

• LLM 0.33 switched to httpx2, breaking plugins that used httpx indirectly.
• The llm-tools-datasette plugin was among those affected.
• A new release, 0.1.1, restores compatibility.
• The fix was issued on Oct 18, 2026.
• The incident highlights dependency pitfalls in plugin ecosystems.

What happened

On 18 October 2026, Simon Willison announced that moving the LLM library to httpx2 had inadvertently broken any plugins that relied on httpx without declaring it as a direct dependency. The llm-tools-datasette plugin was one of those affected, and the fix was released as version 0.1.1.

The update to httpx2 introduced changes that altered the public API surface used by plugins. Because llm-tools-datasette did not list httpx as a direct dependency, it was not rebuilt against the new client, resulting in runtime errors when the plugin attempted to instantiate HTTP connections.

The backstory

LLM frameworks have grown to support a modular architecture where third‑party tools extend core functionality. Developers often import helper libraries like httpx for network requests, assuming that the framework will manage compatibility. Historically, LLM libraries have maintained backward compatibility by pinning specific dependency versions, but the recent shift to httpx2 broke that assumption.

The incident highlights a broader industry trend: as large language models become more customizable, the risk of hidden dependency conflicts rises. Projects that rely on a dense web of plugins must audit their dependency trees whenever a core library updates.

Causes and trade‑offs

The root cause was a semantic upgrade in httpx that altered its import paths and default configuration. Because llm-tools-datasette imported httpx indirectly, it failed to detect the new version and continued to use the old API.

Maintaining strict dependency declarations would have prevented the breakage but at the cost of reduced flexibility for plugin authors. The trade‑off between permissive imports and stability is a recurring theme in open‑source ecosystems.

Second‑order effects

The temporary outage forced users of llm-tools-datasette to seek alternative data‑access solutions or to downgrade their LLM framework. For businesses that rely on automated data ingestion pipelines, this could have introduced downtime and required rapid incident response. On the flip side, the incident prompted the LLM community to adopt more rigorous version‑pinning practices.

What builders and businesses should do

• Audit your plugin dependency graph after any core library upgrade.
• Pin critical third‑party libraries to specific versions.
• Test plugins in a staging environment before rolling out framework updates.
• Contribute to or monitor the issue trackers of both the core LLM library and major plugins.
• Consider adopting a contract that requires plugins to declare all external dependencies.

The bottom line

LLM developers should monitor httpx releases closely and verify that all dependent plugins remain compatible. The recent fix demonstrates that swift patches can restore stability, but proactive dependency management will reduce similar disruptions in the future.