Field noteNov 16, 20266 min read1 source

Datasette Apps 0.4a0 adds URL-fragment linking between sandboxed HTML and JavaScript applications inside

In one minute

Datasette Apps 0.4a0 adds URL-fragment linking between sandboxed HTML and JavaScript applications inside Datasette. The release also reports supported URL schemes to Datasette Agent, so it can help create apps that link to one another. For builders, the change makes separate data interfaces composable through links.

What changed: Datasette Apps 0.4a0 adds URL-fragment linking between apps, enabling one app to link to a specific record view in another.

What happened

Simon Willison’s announcement describes Datasette Apps as sandboxed HTML and JavaScript applications that live inside Datasette. He compares them to Claude Artifacts, with a key distinction: these apps can run SQL queries against the user’s data. The announcement identifies version 0.4a0 as the release adding support for linking.

The new behavior uses URL fragments, the portion of a URL that follows a # character. A user can link to an app with a fragment, and the app can see and use that fragment. Willison does not specify a fragment format, a schema for values, or a particular navigation API; he describes the capability at the level of an app receiving and using the fragment.

The release also changes what Datasette Agent knows about app links. Supported URL schemes are reported back to Datasette Agent so it can help write apps that link to each other. Willison does not describe how the schemes are declared, where that information is stored, or what code the agent generates. He does establish the intended role of the information: helping the agent create linked applications rather than treating every app as an isolated destination.

Willison gives an example of the resulting interaction. One app can show details for a specific record, while a separate app searches those records and links to their representations in the first app. In that arrangement, the search interface and the record-detail interface remain separate applications, but a person can move from a result to its corresponding detail view. The release description does not claim that the apps share state beyond what the linking behavior enables.

The announcement points to the 0.4a0 release on GitHub. It gives no price, hosting requirement, eligibility rule, or broader availability statement. It also does not list compatibility requirements or other changes in this version. The stated capability is specific: URL fragments can carry information an app can use, and supported URL schemes are surfaced to Datasette Agent to help it produce links between apps.

What the archive adds

New Runtime covered Datasette Apps 0.3a0 on 2026-11-08, when the release added permission-aware app references and stored-query controls to workflows using Datasette Agent. Version 0.4a0 is a new fact in that continuing story: it adds linking between apps, rather than restating the earlier permission and query controls. Earlier coverage also discussed Datasette 1.0a41 on 2026-10-01, a broader move toward shared runtime visibility and consistent plugin interfaces.

Trend signal

This release supports agent-ready software exposes capabilities. Datasette Agent receives supported URL schemes and can use that information to help create applications that link to each other. The capability is modest and specific, but it points to an important product boundary: agents can build more useful workflows when software makes its available interfaces legible to them.

Connections to other events

New Runtime’s earlier coverage of Datasette Apps 0.3a0 described permission-aware app references and stored-query controls in Datasette Agent workflows. Those controls concern what apps can access; 0.4a0 concerns how separate apps connect through links. Together, the releases describe different parts of a workflow assembled from small applications: controlled references to data and queries, followed by transitions between an app that searches and one that shows a selected record.

Why it matters

Many data interfaces begin as one application that combines search, results, and detail views. Separating those jobs can make an interface easier to maintain or reuse, but only if users can move between the pieces without losing the reference that connects them. URL fragments offer a simple handoff: a search app can point to a detail app with a value the destination can interpret.

The Datasette Agent integration matters because the release is not only about a human manually wiring links. Reporting supported schemes to the agent gives it information relevant to generating those links. That is a small example of software exposing a capability in a form an agent can use. Teams building data tools can consider whether their apps have stable destinations and clear link conventions that an agent can incorporate into generated interfaces.

The release does not establish that linked apps are automatically safe, that fragments are validated, or that the agent will produce correct destinations in every case. Builders still need to verify links against their own app behavior and data access boundaries. The practical value is narrower: app-to-app navigation can be built around URLs, and the agent is given scheme information to assist with that work.

What happens next

  • Datasette Apps releases will continue to add explicit mechanisms for app composition. (6 months, 55%). Watch for: future release notes describing additional cross-app capabilities beyond URL-fragment links.

Limits and uncertainty

The announcement describes the linking capability and an example, but does not report user adoption, reliability measurements, or performance effects. It does not specify the format or validation rules for URL fragments, nor explain how supported schemes are registered or passed to Datasette Agent. No security review or guarantee about generated links is stated. Willison also does not set out compatibility requirements, pricing, or availability beyond pointing to the 0.4a0 release. The behavior should therefore be read as a new capability, not evidence that every app pair will interoperate without additional implementation or testing.

Skill to build now

If you build a search app and a separate detail app in Datasette, define a stable URL shape for the record-detail destination and decide what identifier the URL fragment should carry. Try the workflow with one record: search for it, follow the generated link, and confirm that the destination interprets the fragment as intended. Then ask Datasette Agent to help create the link and inspect the result rather than assuming the scheme alone guarantees a correct destination.

Reader takeaway

Datasette Apps 0.4a0 gives separate apps a basic way to connect: one app can pass a URL fragment to another, while Datasette Agent is informed about supported URL schemes to help generate those links. It is a focused addition, but it makes linked, multi-app data workflows more practical.

Evidence / sources

  1. 1simonwillison.net/2026/Nov/15/datasette-apps
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicDeveloper ToolsExplore the developer-tools topic hub.
  2. 02topicSandboxExplore the sandbox topic hub.
  3. 03archiveField NotesOpen the latest editorial analysis.
  4. 04sourcesSourcesSee the original sources this archive cites.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract