smooth-browser-use

name

smooth-browser-use

description

Use when operating browser-based workflows that need smooth, human-like navigation, reliable text entry, real paste/input events, form validation, translators, AI detectors, Moodle editors, rich text fields, React/Vue/SPA forms, or any web page where front-end state must update correctly. Also use when a browser page is blank, stuck, stale, desynchronized, or should be refreshed back to a clean state before retrying.

Smooth Browser Use

Overview

Use browser pages the way a careful human would: wait for the real UI, click visible controls, paste through the page, and verify the page's own state before continuing.

Accessibility set_value can make text visible without firing the page's paste, input, change, validation, translation, word-count, or enable-button logic. Treat it as a narrow tool, not the default for web app text entry.

When a browser page is stuck, stale, or desynchronized, refresh back to a clean initial state before retrying.

Smooth Workflow

1. Load the page and wait for the real app UI, not just the address bar or a blank shell.
2. Use get_app_state before interacting after navigation, reloads, user interruptions, or failed clicks.
3. Prefer visible controls and keyboard operations over direct accessibility value injection.
4. After each meaningful action, verify the page reacted before moving on.
5. If the page state looks wrong, refresh early instead of compounding bad state.

State Checks

Do not trust visible text alone. Trust the page's own state indicators:

• Word or character counters update.
• Translation output changes.
• Analyze, detect, submit, or continue buttons become enabled.
• The page shows a completed result instead of placeholder text.
• Error banners disappear after retry or refresh.