Connect to this DuckDB?

This link points at a DuckDB someone is running. Attaching it lets this tab query that machine directly, over an encrypted relay.

Machine

—

Relay

—

• Nothing is installed. DuckDB is WebAssembly running on this page. The session lives in this tab, and closing it ends everything in it.
• That machine gets no access to this one. This tab dials out and reads the answers back. It hands over no files and opens nothing for them to connect to; what comes back is query results, parsed inside the browser's sandbox.
• The relay only carries ciphertext. Traffic is encrypted end to end between this tab and that machine. The relay sees two endpoint ids, the timing and the byte counts — not your SQL, and not the results.
• Treat this full link like a password. The access token is part of it and does not expire. Anyone you pass it on to can query that machine until whoever runs it stops serving — so keep it out of chats, issues and commits, and connect only if you trust who sent it to you.

quackhole: connect to DuckDB from anywhere

A database on a laptop, a VM or a sandbox has no address the internet can reach. quackhole gives it one, and this browser tab queries it directly: nothing installed here, no ports opened there.

Start DuckDB on a VM, sandbox, or laptop

Start DuckDB somewhere with the quackhole extension. Whichever way you start it, it prints a ticket which connects this browser tab to it.

Add a remote DuckDB

Paste the ticket the other machine printed. Opening the link it printed does this for you.

A ticket grants this tab query access to that machine, and grants it nothing on yours — DuckDB runs in this tab. It carries an access token that does not expire, so treat it like a password.

Let an agent drive this workbench

This page hands its own tools to any agent in the browser with WebMCP, so one calls them directly instead of reading the screen and guessing where to click.

Checking this browser…

• list-connections — what is attached, and the tables on each.
• attach-remote — attach a DuckDB from a qh1_… ticket.
• run-sql — type one statement at the terminal and run it.

run-sql types into the terminal you are looking at and returns only that the statement ran, so an agent has to ask you what it said. A page that queried somebody's machine invisibly, beside a terminal showing nothing, is the version of this nobody should ship.

Hand this to an agent that can browse — ChatGPT in a browser that speaks WebMCP, or anything else that does. The link carries a prompt that sends the agent here and says what is waiting.

The button puts that prompt in the URL, so it goes to OpenAI and stays in your chat history. It carries no ticket and no token — an agent that should reach a machine you are serving has to be handed the qh1_… ticket by you.