Troubleshooting

Agent Can’t Open Your Link?

Fix the common “works in my browser, fails for my agent” issue in under 5 minutes.

A recurring support loop is: “I sent the URL, but the agent says it can’t access it.” Usually the link is private, login-gated, blocked by anti-bot protections, or requires a browser click flow.

Core rule: if a page needs your personal login/cookies, your agent usually cannot see it just from a pasted URL.

Fast triage checklist

  1. Open the link in an incognito/private window where you are not logged in.
  2. If it fails there, it is private or session-gated.
  3. Check whether the task needs clicking/sign-in (not just reading public text).
  4. If private, provide exported text/file/screenshot instead of raw URL.
  5. Retry with a known-public URL to confirm the agent’s fetch path is healthy.

Most common root causes

Known-good test prompt

Use this to quickly isolate whether the problem is the specific URL or broader tool access:

Test these two URLs and summarize each in 3 bullets: 1) https://example.com 2) [my target URL] For each, state: reachable or blocked, and likely reason.

Important: do not paste private auth tokens, session cookies, or secrets to force access. Use exported content instead.

Safe workaround patterns

Copy/paste handoff prompt

You probably can’t access this private URL directly. I will paste/export the content below. Please do: 1) Summarize key points 2) Extract action items 3) Draft a response email in my tone

Support-ready escalation packet

URL access issue report Target URL domain: Expected result: Agent error/result text: Incognito test (works/fails): Known-public URL test (pass/fail): Does the task require login/clicking? (yes/no): What content I can export safely:

Bottom line: if the page is private, share exported content. If the page is public and still fails, escalate with the packet above for fast diagnosis.