Foxl Docs

Troubleshooting

Solutions to common issues with the Foxl desktop app, web app, and Chrome extension

Desktop App

App won't open on macOS

Right-click the app in Applications and select Open. macOS Gatekeeper may block first launch. Foxl is notarized by Apple (Team ID: B47A25FR9P).

"Node.js not found" error

Foxl requires Node.js 22 or later. Install from nodejs.org or via Homebrew:

brew install node@22

Agent not responding

  1. Check the Logs page in the sidebar for errors
  2. Try restarting the desktop app
  3. Verify your internet connection (needed for cloud model access)
  4. If using BYOK, check that your API key is valid in Settings > Providers

High memory usage

The agent runs a Node.js process. If memory usage is high:

  1. Close unused conversations
  2. Restart the app to clear agent state
  3. Check for long-running background processes in the Agent page

Web App (app.foxl.ai)

Can't sign in

  • Try a different sign-in method (Google, Apple, or email magic link)
  • Clear browser cookies for app.foxl.ai and try again
  • Check that your browser allows third-party cookies (needed for OAuth)

"Desktop Offline" but desktop app is running

  1. Check that both devices are connected to the internet
  2. Verify the pairing in desktop Settings > Relay
  3. Try disconnecting and re-pairing with a new 6-character code
  4. Check if a firewall or VPN is blocking WebSocket connections

Conversations not loading

Web app conversations are stored in localStorage. If they disappeared:

  • Check if you cleared browser data
  • Try a different browser to see if conversations are browser-specific
  • Conversations in relay mode are stored in the browser, not synced across devices

Slow responses

  • Check your internet connection
  • Try switching to a faster model (Haiku 4.5 is fastest)
  • Check status.foxl.ai for service status

Chrome Extension

Extension shows "Disconnected"

The extension connects to the desktop agent via localhost WebSocket:

  1. Make sure the desktop app is running
  2. Check chrome://extensions for any error messages
  3. Reload the extension (toggle off/on in chrome://extensions)

Agent can't see page content

Some pages block content extraction:

  • Pages with strict CSP (Content Security Policy)
  • CAPTCHAs and bot protection
  • Dynamic SPAs that load content after initial render

Try refreshing the page or using the Playwright-based browser tool as a fallback.

Extension interfering with normal browsing

The extension is passive by default — it only activates when the agent requests it. If you experience issues:

  1. Disable the extension in chrome://extensions
  2. Use only when needed with the desktop agent

Windows: SmartScreen warning on first launch

Foxl for Windows is currently self-signed. When you first run it, Windows SmartScreen may show a warning. Click More info then Run anyway. This is safe.

Windows: "Node.js not found" error

Install Node.js 22+ from nodejs.org. If you used a portable Node.js install, make sure the node binary is in your system PATH.

Windows: PowerShell terminal not working

Foxl prefers PowerShell 7+ (pwsh.exe). If not available, it falls back to Windows PowerShell. Install PowerShell 7:

winget install Microsoft.PowerShell

Credits and Billing

Credits show as 0 after signup

Credits may take a moment to sync. Try:

  1. Refresh the page
  2. Sign out and sign back in
  3. Wait 30 seconds and check again

"Rate limit exceeded"

You've hit the daily request limit:

  • Free: 200/day
  • Pro: 2,000/day
  • Ultra: 10,000/day

Wait until midnight UTC or upgrade your plan.

Charged but credits not updated

Contact [email protected] with your account email and transaction ID.

Scheduling

Schedules not running

  1. Desktop app must be running for schedules to execute
  2. Check the Schedules page for any failed runs
  3. Verify the cron expression is correct
  4. Check Logs for any errors during execution

Schedule ran but produced no output

  • The scheduled task may have failed silently
  • Check Logs for the specific schedule execution
  • Try running the task manually first to verify it works

Getting Help

On this page