jido-browser

To handle browser authentication and DOM interactions in Jido workflows, use browser automation actions that separate navigation, observation, and mutation steps. Keep site-specific logic in the application layer with explicit selectors, waits, and safety checks.

Use browser automation instead of HTTP clients when rendering pages, handling authentication state, or complex DOM interactions are required. Prefer HTTP or API clients for stable endpoints and reserve browser steps for dynamic sites or complex interactions.

To structure a login flow in a Jido workflow, use a browser action to navigate to the target site, input credentials, and verify the resulting authentication state. Maintain clear separation between navigation, observation, and mutation steps.

The best way to organize site-specific logic is to keep it in the application layer while isolating DOM logic in the browser module. Use explicit selectors, waits, and safety checks to maintain clear boundaries between navigation and mutation steps.

Browser automation workflows fail to extract data from dynamic sites when explicit waits and safety checks are missing. Ensure clear separation of observation and mutation steps, and keep DOM logic in the browser module with explicit selectors.