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

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

Most common root causes

Login wall: Notion, Google Docs, dashboards, and internal tools often require cookies.
Permission scope: Link is visible only to your account, team, or IP range.
Anti-bot/JS gate: Cloudflare or heavy JavaScript pages can block simple fetch tools.
Browser-action requirement: Task needs clicking buttons, forms, or multi-step navigation.
Temporary/expired URL: Signed links and one-time links may expire quickly.

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

Paste plain text: Copy key content directly into chat for analysis.
Upload files: Share a PDF/CSV/screenshot exported from the private tool.
Human-agent handoff: You click and extract; the agent summarizes/transforms.
Public mirror: If appropriate, publish a sanitized public version and share that URL.

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

High-friction social link edge cases (Facebook/Instagram)

Public page vs logged-in view mismatch: if the page only opens while you are logged in, the agent may not be able to read it from URL-only access.
Page role requirement: some business-page content (drafts, insights, unpublished posts) requires owner/editor permissions and will look “missing” to agents.
Geo/age/privacy restrictions: region/age gates can make links appear broken from remote fetch paths.
App/web redirect traps: mobile-app links can redirect to login walls. Prefer full desktop web URLs for testing.

Fast check: open the exact link in an incognito tab while logged out. If it fails there, give the agent exported text/screenshots instead of retrying the URL.

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.