Why browser-local
Configuration files and private keys can contain sensitive material. Available tool actions run in your browser and do not send that material to an application server. The site still downloads static files and the hosting provider sees ordinary connection metadata, so the privacy boundary is stated precisely rather than presented as “no network.”
How tools are selected
A candidate should solve a frequent, narrow developer problem; work credibly without a backend; benefit from local processing; and be maintainable with tested examples and clear limits. Existing tools are improved before the catalog expands.
What is intentionally absent
There is no AI feature, account system, database, server-side conversion, input telemetry, session replay, or advertising inside tool workspaces. Source values, output, filenames, diagnostics, passphrases, key material, clipboard actions, and downloads are not collected by the application.
Suggest a small developer problem
Email [email protected] with the workflow and the destination format or platform. Do not attach private keys, production configuration, secrets, or customer data.