llm-tools-datasette 0.1.1 fixes break from LLM 0.33's httpx2 switch

Simon Willison published a short post on 18 October 2026 announcing llm-tools-datasette 0.1.1, a new release of his plugin that exposes Datasette instances to LLM as a tool.

The release is a repair. Willison writes that he forgot something about LLM 0.33: when LLM switched to httpx2, plugins that imported httpx without listing it as a direct dependency would break. llm-tools-datasette was one such plugin, and he has now fixed it.

The post describes the cause as plugins that used httpx "without directly depending on it." In other words, the plugin relied on httpx being present because LLM itself brought it in, and that stopped working once LLM changed to httpx2.

The post links to the GitHub release page for llm-tools-datasette 0.1.1, the httpx2 project and the LLM 0.33 changelog. It is tagged datasette and llm.

Key facts

  • Simon Willison released llm-tools-datasette 0.1.1 on 18 October 2026.
  • The plugin's tagline is "Expose Datasette instances to LLM as a tool".
  • The trigger was LLM 0.33 switching to httpx2, which would break plugins that imported httpx without listing it as a direct dependency.
  • llm-tools-datasette was one such plugin, and Willison says he has now fixed it.

Why it matters

The post shows a small but common failure: a plugin that uses a library without declaring it as a dependency works only while the host application happens to supply that library. When LLM 0.33 moved to httpx2, that assumption stopped holding. Willison's own plugin was caught by it.

Who it affects

Users of the llm-tools-datasette plugin, which exposes Datasette instances to LLM as a tool, and by extension anyone running it on LLM 0.33. The post also says plugins in general that imported httpx without listing it as a direct dependency would break. The source does not say how many other plugins were affected.

How to use it

The fix ships as llm-tools-datasette 0.1.1; the post links to its GitHub release page. Plugin authors who import httpx should list it as a direct dependency, which is the gap the post identifies as the cause. The source does not say what the code change in 0.1.1 was.

How solid is it

This is a first-party note from the plugin's author, so the account of what broke and who fixed it comes straight from the maintainer. The post is very short and gives no technical detail of the change.

Risks and caveats

The source does not say what the actual code change in 0.1.1 was, how many other plugins were affected, or when LLM 0.33 was released. It gives no reaction from users or maintainers. Other plugins with the same undeclared httpx import may still need their own fixes, but the post does not say so.

“without directly depending on it.”

— Simon Willison's blog post on llm-tools-datasette 0.1.1, describing plugins that used httpx