Research workflows and preview feedback
Tell us what the tab pile represents and what you cannot risk losing.
Contact address set at deploymentContact
Bring the messy
real workflow.
No generic demo request form. Choose the route that fits, and send enough context for a useful reply.
Implementation and contribution questions
Include the package, intended change, and safety impact.
Contact address set at deploymentDesign-partner conversations
Bring a real workflow, current workaround, and deployment boundary.
Contact address set at deploymentResponsible vulnerability disclosure
Use private repository reporting where possible. Include version, browser, minimal reproduction, and impact.
Contact address set at deploymentWhat helps us evaluate a workflow
When does the pain appear?
After a purchase decision, a competitor scan, a literature review, a debugging session, or something else?
What must never close?
Forms, carts, calls, dashboards, authenticated state, changing prices, or unanswered questions?
What would you keep?
A cited decision, a restorable window, a team handoff, or simply confidence that the browser can be clean?