Offline Browser Execution Mechanics

Each tool definition provides inputs, options, metadata, and a client-side executor.

Execution flow

1. The local catalog loads the tool definition.
2. The page renders its inputs and options.
3. Run Tool collects values in the browser.
4. JavaScript and supported Web APIs process them.
5. The output appears locally.
6. Only lightweight history metadata may be recorded.

Utilities can use DOMParser, XMLSerializer, URL, TextEncoder, Web Crypto, Blob, FileReader, and—only for remote-request tools—Fetch.

The current catalog primarily uses browser JavaScript executors. It does not claim that every utility runs in WebAssembly or a dedicated Web Worker.