KnockOutEZ/wigolo

npx wigolo init
npx wigolo init --agents=claude-code,cursor
Docker: docker run -i --rm -v wigolo-data:/data ghcr.io/knockoutez/wigolo

Usage

• •Requires Node >= 20 and ~1.5GB free disk (downloads browser engine + on-device models)
• •npx wigolo doctor to verify health; npx wigolo config --uninstall --yes to remove
• •Optional free Gemini key for synthesis: export WIGOLO_LLM_PROVIDER=gemini; export GEMINI_API_KEY=<free-key>
• •REST (no MCP client needed): wigolo serve; curl -X POST http://127.0.0.1:3333/v1/search

Key features

• ✓10 tools: search (18 engines, rank fusion, ML rerank), fetch (tiered HTTP→headless-browser on anti-bot challenges), crawl, extract, cache, find_similar, research, agent, diff, watch
• ✓Explainable per-result evidence scores, verbatim excerpts pinned to byte-offset source spans, citation IDs, freshness signals
• ✓Keyless by default; local cache makes re-querying instant; on-device reranker + embeddings
• ✓REST API (OpenAPI 3.1), TypeScript & Python SDKs, Docker, and LangChain/CrewAI/LlamaIndex/Vercel AI SDK integrations
• ✓Public beta with a 7,600-test suite; actively maintained

Best for

Agents that need private, keyless, no-metered-bill web search, fetch, and crawl with transparent, inspectable evidence.

Caveats

• ⚠Public beta status
• ⚠Requires ~1.5GB disk for the on-device browser engine and ML models
• ⚠research/agent/search-answer synthesis needs an optional LLM key (free Gemini tier is enough) or local ollama
• ⚠AGPL-3.0 license (network-service obligation only if you run a modified version as a service)
• ⚠Some challenge-protected sites score IP reputation — datacenter IPs may not clear walls a home connection would