2026-11-15 · ← News
Datasette Apps 0.4a0 turns URL fragments into links between small data apps
Datasette Apps 0.4a0 lets an app store view state in a URL fragment, share a specific view and link to other apps. The small alpha release gives an agent a map of existing interfaces instead of asking it to invent the next app blindly.
The image could not be loaded.
Datasette Apps 0.4a0 adds navigation through URL fragments. A sandboxed app can keep its current view in location.hash, respond to fragment changes and link to a specific record. State is mirrored in both directions between the app and the page URL.
A URL fragment makes an app view shareable
A specific screen can now be bookmarked, reloaded, shared and navigated with the browser back and forward buttons. history.pushState() and history.replaceState() also work with fragment only URLs, with the latter changing the fragment without adding a browser history entry.
An app can link to a view in another app using a root relative path and a fragment. Version 0.4a0 is a prerelease and requires Datasette 1.0a42 or newer. It follows 0.3a0, which addressed access to saved queries. This release changes navigation rather than data permissions.
A manifest gives the agent a vocabulary of existing views
Apps can publish a manifest in their HTML describing the fragments they support. Datasette extracts those declarations into a new app_links table whenever an app is saved. A new datasette-agent tool lists links from every app the current user can view and can filter them by table.
An agent can therefore build a search app whose results open a record view in a separate app. That moves the system from isolated generated widgets toward small components that expose known entry points and can be composed.
A link carries state but cannot guarantee meaning or access
A URL fragment solves navigation. It does not prove that a target record exists, that two apps interpret an identifier the same way or that a link will survive a schema change. Access still depends on the user's permissions and on the saved queries used by each app.
The manifest is also an author's declaration. If it becomes stale, an agent may assemble links to the wrong view. The new hash option in app_debug helps inspect the result, but that check still has to become part of the workflow.
Schema changes and a network of apps will provide the real test
Future releases will show whether links survive renamed tables, new app versions and different user permissions. Useful diagnostics will need to identify invalid fragments and reveal which app still depends on an old link format.
If several small apps accumulate over one database, manifests could act as a lightweight contract between them. Without versioning and compatibility checks, a network of links can quickly become a network of dead ends.
Lilith's verdict
The fragment after # looks tiny, but it gives every view a postal address. Datasette now has to stop its agent from delivering letters to houses that vanished after a schema change.