Support

Another process is using port 9988 or 9989. Either stop that process or change Forage's ports in forage.config.json:

{ "uiPort": 9990, "mcpPort": 9991 }

Remember to update your agent MCP config to the new port if you change mcpPort.

Large codebases with many files can take several minutes on first run. Check progress in the terminal where Forage is running.

If it appears stuck, check that your exclude list covers large generated directories like node_modules, vendor, and dist. You can also add a .forageIgnore file to narrow the scope.

First confirm Forage is running by opening http://localhost:9989/mcp in your browser — you should see a JSON tools listing.

If the page doesn't load, start Forage with:

forage --start

If the page loads but the agent still can't connect, most agents cache MCP server discovery. Fully restart the agent (not just reload the window).

Check your include and exclude patterns in forage.config.json. Files matching an exclude pattern are silently skipped.

To force a full re-index:

forage --reindex

Reduce the scope of indexing with more specific include paths, or set autoUpdate: false to disable the file watcher and only re-index on demand.

You can also lower maxFileSizeKb to skip large generated files that are rarely queried.

License tokens are tied to your activation token. Make sure you're using the correct token from your customer portal. If your token has expired, generate a new one from the portal.

If you're behind a firewall or proxy, Forage needs outbound HTTPS access to squrl-labs.com for license verification on startup. Contact support@squrl-labs.com if you need an air-gapped licensing arrangement.

Stop Forage, then uninstall via the same method you used to install:

# npm
npm uninstall -g @squrl/forage

# Homebrew
brew uninstall forage

Graph data is stored in a .forage/ directory in your project root. Delete it to remove all indexed data for that project.