Jeff R.

Wasm extensions other than MD come from the usual place at extensions.duckdb.org, for example https://extensions.duckdb.org/v1.5.3/wasm_eh/icu.duckdb_extension.wasm

The package does bake in the version of duckdb-wasm, and fetches those assets as well, for example:

https://app.motherduck.com/duckdb-wasm-assets/1.33.1-dev55.0/duckdb-eh.wasm
https://app.motherduck.com/duckdb-wasm-assets/1.33.1-dev55.0/duckdb-browser-eh.worker.js

(The MD native extension checks this automatically; for the MD Wasm extension, the wasm-client package does this.)

The MD wasm extension is also fetched from ext.motherduck.com. Example: https://ext.motherduck.com/v1.5.3-2026-06-118/v1.5.3/wasm_eh/motherduck.duckdb_extension.wasm

Fabian I looked into this and found a bug with how @motherduck/wasm-client recovers from failed initialization (as you describe). I've (just) published a fix in version 1.5.3-r.2. Please give this a try and let us know if it helps.

See my comments in https://github.com/duckdb/duckdb-ui/issues/153.

No timelines. Being able to better collaborate on SQL (of which import/export is a part) is on our near-term roadmap, however. The DuckDB UI and the MotherDuck (web) UI share code, so in most cases a feature will land in both at the same time. Import/export of files is necessarily a little different in the browser vs local, but we aim to for the two experiences to be as similar as possible.

This is a great idea that's also captured here: https://github.com/duckdb/duckdb-ui/issues/38

This remains a priority for us, but we don't have anything to share just yet.

No need to update either DuckDB or the UI extension to use Instant SQL. If you have the DuckDB UI running already, you'll likely need to reload the page.