Release: Datasette-Extract 0.3A0 Availability

Issue 91 Edition 2026-04-01 3 min read

Not accepted General

Sources: 1 • Confidence: Medium • Updated: 2026-04-12 09:58

Key takeaways

datasette-extract 0.3a0 has been released.
datasette-extract now uses datasette-llm to manage model configuration for extraction tasks.
Model availability for datasette-extract extraction tasks can be controlled using the "extract" purpose and LLM model configuration.

datasette-extract now uses datasette-llm to manage model configuration for extraction tasks.

Model availability for datasette-extract extraction tasks can be controlled using the "extract" purpose and LLM model configuration.

What specific functional changes, breaking changes, or migrations are included in datasette-extract 0.3a0 relative to the previous release?
What is the exact configuration format and location by which datasette-extract reads datasette-llm model configuration for extraction tasks?
Are any previous datasette-extract model configuration methods deprecated, removed, or still supported in 0.3a0?
How does the "extract" purpose gating behave across different interfaces (CLI, UI, API), and what happens when a disallowed model is requested or configured as default?
Which specific models/providers are supported for extraction tasks under datasette-llm configuration in this release, and are there any constraints or limitations?

Centralizing extraction model configuration in datasette-llm may increase interoperability across Datasette components, potentially reducing maintenance burden and encouraging broader plugin adoption.
Purpose-based gating using an extract purpose may indicate a move toward stronger operational controls over which models can run extraction workloads, potentially improving governance and safer deployment patterns.
A pre-release 0.3a0 may signal upcoming API or behavior changes that could affect downstream users, creating near-term migration work but potentially enabling a cleaner long-term configuration surface.

Release notes or documentation that detail migration steps and show extraction model configuration exclusively managed through datasette-llm with clear, stable configuration format.
Evidence that purpose gating is consistently enforced across CLI, UI, and API for extraction tasks, with predictable behavior when a disallowed model is selected.
Subsequent releases that keep the datasette-llm integration and expand supported providers or models for extraction without reverting the configuration approach.

Documentation or issues indicating the datasette-llm configuration path is unreliable, unclear, or requires frequent breaking changes to keep extraction working.
Reports that purpose gating is inconsistently applied across interfaces, or that disallowed models can still be used for extraction despite configuration.
A follow-on release that deprecates or abandons the datasette-llm dependency for extraction model configuration, reverting to bespoke settings.