Robots: Record fallback selectors per step and self-heal when the primary one breaks
UiPath Unified Target keeps several targeting strategies and the Healing Agent votes on a candidate selector when one is not found, recommending or applying fixes (https://docs.uipath.com/agents/automation-cloud/latest/user-guide-ha/what-is-healing-agent); Browse AI says it detects layout changes and adapts the robot, notifying the user (https://help.browse.ai/en/articles/10486935-how-browse-ai-uses-ai); Stagehand re-infers a selector when a cached one stops resolving (https://docs.stagehand.dev/v4/best-practices/caching). Our recorder computes candidates but keeps only the first unique one (generateSelector in lib/robots-recorder.ts), and resolveTarget tries one selector and then visible text (lib/robots-interpreter.ts). Selector rot is the main maintenance cost of browser robots. First scope: store a fallbacks array (testid, aria-label, name, text, CSS path) per step from the recorder, try them in order at runtime, log 'healed via fallback N', and offer a one-click 'promote fallback' in the run view. Priority: high. Effort: M. Compared with UiPath (StudioX, Autopilot, Orchestrator, Healing Agent), Browse AI, Axiom.ai, Bardeen, Browserbase/Stagehand, Skyvern.
Comments 0
No comments yet.
Sign in to comment