Director AI

Director AI Pro Tips

➩ Ground context up front: preload creds/secrets, add reference pages, and specify environments (prod vs staging).
➩ Start narrow, then widen: automate one high-ROI flow (single site/report) before generalizing inputs and sites.
➩ Use observe → act: ask Director to locate elements via observe steps before clicking to survive dynamic UIs.
➩ Be explicit on selectors: mention button text/ARIA labels (“click ‘Continue’ with role=button”) to boost reliability.
➩ Encode time windows as parameters: “last 7 days” → from/to inputs so the Stagehand script is reusable.
➩ Add checkpoints: request screenshots/logs after key steps (login, filter applied, export complete) for faster debugging.
➩ Rate-limit and backoff: instruct retries on 429/5xx with exponential backoff to avoid bans and flaky runs.
➩ Keep secrets safe: store passwords/API keys in Director/Browserbase vaults; never paste plain text into prompts.
➩ Export the script for hardening: hand the generated Stagehand code to devs to add types, guards, and CI/cron.
➩ Let Browserbase scale: use cloud browsers + proxies for volume jobs instead of local headless instances.
➩ Version everything: save prompt versions and script diffs when sites change (“button label now ‘Next’”).
➩ Use table-driven runs: feed lists (domains/IDs/dates) to batch the same automation across many inputs.