Cost-Accounting Modularization And Breaking Change

Issue 91 Edition 2026-04-01 4 min read

General

Sources: 1 • Confidence: High • Updated: 2026-04-13 03:33

Key takeaways

In datasette-llm-usage 0.2a0, features related to allowances and estimated pricing were removed.
The /-/llm-usage-simple-prompt page was redesigned and now requires the llm-usage-simple-prompt permission for access.
datasette-llm-usage depends on datasette-llm for model configuration.
Allowances and estimated pricing functionality is handled by datasette-llm-accountant rather than datasette-llm-usage.
If the datasette-llm-usage.log_prompts plugin setting is enabled, full prompts, responses, and tool calls can be logged to the internal llm_usage_prompt_log table.

In datasette-llm-usage 0.2a0, features related to allowances and estimated pricing were removed.
Allowances and estimated pricing functionality is handled by datasette-llm-accountant rather than datasette-llm-usage.

The /-/llm-usage-simple-prompt page was redesigned and now requires the llm-usage-simple-prompt permission for access.
If the datasette-llm-usage.log_prompts plugin setting is enabled, full prompts, responses, and tool calls can be logged to the internal llm_usage_prompt_log table.

What is the precise migration path for users who previously relied on allowances and estimated pricing in datasette-llm-usage, including any data/schema migration needs?
What versions of datasette-llm are required by the new datasette-llm-usage dependency, and are there any breaking configuration changes implied by the shift to datasette-llm-managed model configuration?
What is the retention, redaction, or access model for rows in llm_usage_prompt_log when prompt logging is enabled, and what safeguards exist to prevent sensitive data exposure?
Who is expected to have the llm-usage-simple-prompt permission by default after upgrading, and are there documented role templates or admin guidance for granting it safely?
Is there any direct decision-readthrough (operator, product, or investor) described in the corpus beyond the need to upgrade/install additional plugins and adjust permissions/settings?

Shift of allowances and estimated pricing into datasette-llm-accountant could increase modular adoption and plugin installs, as cost budgeting becomes an add-on rather than bundled with usage tracking.
Permission gating for the simple prompt UI and optional prompt logging suggest a move toward stronger access control and observability, potentially raising enterprise suitability if configured safely.
Dependency on datasette-llm for model configuration indicates consolidation of configuration across plugins, which may reduce fragmentation and influence upgrade cadence and maintenance burden.

Documentation and release notes clearly describe a migration path from prior allowances and estimated pricing, including any data or schema steps, and users successfully upgrade with minimal breakage.
Guidance emerges on retention, redaction, and access for llm_usage_prompt_log and on safe role templates for llm-usage-simple-prompt permission, indicating operational readiness for sensitive environments.
Datasette-llm version requirements and configuration changes are clearly specified, and downstream plugins converge on datasette-llm-managed model configuration without conflicting setups.

Widespread user friction or regressions due to removed allowances and estimated pricing, with unclear migration and reliance on additional plugin installation causing stalled upgrades or churn.
Prompt logging leads to frequent sensitive data exposure concerns because retention and redaction controls are absent or unclear, reducing willingness to enable the feature.
Dependency shift to datasette-llm introduces breaking configuration incompatibilities or tight version pinning that complicates deployments across the plugin ecosystem.