fix: resolve URL loading timeout issues in @ mentions

[MuriloFP]

Related GitHub Issue

Closes: #1430

Description

Problem

URLs provided through @ mentions were failing to load with "Navigation timeout of 10000 ms exceeded" errors, preventing users from fetching web content for AI assistance.

Solution

• Increased timeout limits: Extended UrlContentFetcher timeout from 10s to 30s and BrowserSession timeout from 7s to 15s for better reliability with slow-loading websites
• Added fallback retry logic: If networkidle2 fails, automatically retry with domcontentloaded only (20s timeout) to handle JavaScript-heavy sites
• Improved error handling: Enhanced error messages with specific guidance for timeout, DNS, network, and HTTP status errors
• Enhanced browser compatibility: Added Chrome launch arguments (--no-sandbox, --disable-web-security, etc.) and set proper viewport/headers to reduce blocking by websites

Files Changed

• src/services/browser/UrlContentFetcher.ts: Increased timeout, added retry logic, enhanced browser setup
• src/services/browser/BrowserSession.ts: Increased navigation timeouts for consistency
• src/core/mentions/index.ts: Improved error handling with user-friendly messages

Impact

Users can now successfully fetch content from slower websites and receive clearer error messages when issues occur, significantly improving the @ mention URL feature reliability.

Test Procedure

Mention an URL and ask for a summary, for example. I tested with "Give me a summary of @#1430".

Before my changes, I got the same result as the issue, with the timeout error.

After the changes, it loaded successfully and the model was able to provide an answer. I tested with models that aren't able to access URL content too, to make sure they were getting the info from our fetch URL tool.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable).
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Documentation Updates

Additional Notes

Also added better error handling for common types of failed fetch URL errors.

Get in Touch

@MuriloFP

---

Important

Fix URL loading timeout issues by increasing timeouts, adding retry logic, and improving error handling in UrlContentFetcher, BrowserSession, and index.ts.

• Behavior:
  • Increased UrlContentFetcher timeout from 10s to 30s and BrowserSession timeout from 7s to 15s.
  • Added retry logic in UrlContentFetcher to fallback to domcontentloaded if networkidle2 fails.
  • Improved error handling in parseMentions() in index.ts with specific messages for timeout, DNS, network, and HTTP errors.
• Browser Configuration:
  • Added Chrome launch arguments in UrlContentFetcher to improve compatibility.
  • Set viewport and headers in UrlContentFetcher to reduce website blocking.
• Files Changed:
  • UrlContentFetcher.ts: Increased timeout, added retry logic, enhanced browser setup.
  • BrowserSession.ts: Increased navigation timeouts for consistency.
  • index.ts: Improved error handling with user-friendly messages.

^{This description was created by for 40156b6. You can customize this summary. It will automatically update as commits are pushed.}