AI browser automation: download and check a CSV with Claude or Codex
Test browser automation with AI in one profile: connect Claude or Codex through MCP, read a report and verify the downloaded file before using a real store.
Prepare one profile
Browser automation with AI should start in one clearly named test profile. Review its proxy and network settings, then open it in visible mode. A separate cookie jar does not by itself change your IP address.
Connect Claude or Codex through MCP
In IFox9’s AI Assistant panel, configure your detected client. Restart that client and run check_connection. Ask it to list profiles and select the test profile explicitly; a successful MCP connection is not proof of the correct target.
Read before downloading
Open the linked practice report. Ask the assistant to identify Demo Store, September 1–3, 2026, UTC and USD. Stop if the page or selected profile differs. These are fictional records, not a live marketplace dashboard.
Download and verify
Use the page’s CSV download button. Check the actual returned file path, open the file and confirm three daily rows, 12 orders and $360 gross sales. A screenshot or a success message alone does not prove a download.
Recover and hand over
If a download is missing, inspect the export state before retrying. Complete logins or human checks yourself. Record the app/client versions, date and unresolved issues, then release browser control. Only adapt this task to stores you are authorized to operate.