Worker Patterns may detect when a task looks browser-related and recommend a browser-capable route. It does not include a browser automation runtime.
- detect browser/web-app signals in objective text;
- add safety notes to the selected plan;
- render a dry-run route that says browser-capable tooling may be appropriate later.
- opening websites;
- entering credentials;
- accepting cookies or terms;
- scraping live user data;
- clicking buttons;
- mutating remote state;
- bypassing access controls.
- Use the selector to identify whether browser capability is needed.
- Inspect the dry-run plan.
- Route the work to an explicitly approved browser harness or manual workflow.
- Keep credentials and real website actions outside this package.