Public planning
The roadmap prioritizes browser-local utility, privacy-visible workflows, and sustainable open-source maintenance. It does not propose accounts, cloud history, or server-side payload processing.
Active
Keep sensitive-input warnings, external-request confirmations, Trust Center links, and storage guards aligned with manifests.
Active
Improve local batch workflows, export controls, mobile layouts, keyboard paths, and actionable validation states.
Active
Add higher-quality comparison, guide, workflow, and llms.txt surfaces without mass-generating thin pages.
Exploring
Evaluate whether PWA, browser extension, or desktop wrapper access can preserve local-only processing with low maintenance risk.
New features must preserve local-first behavior by default. Public requests should use sanitized examples and must not include production secrets, private payloads, customer data, tokens, logs, or screenshots containing sensitive content.
