GitHub - fivetaku/insane-search: Auto-bypass for blocked websites in Claude Code — Phase 0→3 adaptive scheduler, no API keys
Service

GitHub - fivetaku/insane-search: Auto-bypass for blocked websites in Claude Code — Phase 0→3 adaptive scheduler, no API keys

fivetaku
2026.06.29
·GitHub·by Leon
#AI Plugin#Automation#Bypass#Claude Code#Web Scraping

Key Points

  • 1insane-search is a resilient plugin for Claude Code that automatically bypasses web access restrictions to fetch and summarize public content from platforms like X, Reddit, and YouTube.
  • 2The system employs a multi-phase adaptive scheduler that escalates from public APIs and syndication gateways to TLS impersonation and headless browsing to successfully bypass 403 or WAF-blocked pages.
  • 3While designed to navigate anti-bot measures and provide useful data from public pages, the tool strictly adheres to privacy boundaries by refusing to bypass authentication, logins, or paywalls.

Overview
*insane-search* is a specialized plugin designed for Claude Code that enhances the tool's ability to retrieve and interpret public web content. It effectively overcomes common obstacles such as 403 Forbidden errors, Web Application Firewall (WAF) blocks, and anti-bot challenges that typically prevent standard fetch operations from succeeding. By automating a multi-staged, adaptive retrieval process, the plugin enables Claude Code to access structured data and content from platforms like X, Reddit, YouTube, and GitHub without requiring API keys, user authentication, or manual proxy configuration.

Core Methodology and Technical Architecture
The plugin operates on an adaptive, hierarchical scheduling mechanism (Phase 0 through Phase 3) that progressively increases technical complexity to bypass access barriers:

  • Phase 0 (Specialized Endpoints): The system first targets platform-specific public endpoints, including official syndication feeds and undocumented internal APIs discovered via observation of standard browser network patterns.
  • Phase 1 (Lightweight Probes): If initial attempts fail, the plugin probes the target URL using lightweight strategies, such as appending common path suffixes (e.g., /rss, /.json) and utilizing mobile-specific or alternative public URL variants to retrieve lightweight site metadata.
  • Phase 2 (TLS Impersonation): To counter sophisticated anti-bot detection, the system utilizes curl_cffi to perform TLS impersonation. This mimics the handshake signatures of legitimate browsers (Safari, Chrome, Firefox). Unlike simple User-Agent switching, this phase constructs a full browser identity, including coherent referer chains and cookie warming, to satisfy WAF verification.
  • Phase 3 (Headless Browser Execution): As a final resort, the system initiates a real headless browser session. This environment monitors the internal network traffic of the target site to extract the specific JSON APIs the page utilizes to render content, allowing the plugin to capture data even when the primary HTML document is obfuscated.

Data Extraction and Processing
Regardless of the phase through which data is retrieved, the plugin performs an ongoing scan for Open Graph Protocol (OGP) metadata and JSON-LD structured data. This ensures that even when a page is partially blocked or rendered in a non-standard way, the plugin can synthesize meaningful titles, summaries, and price points. Furthermore, for media-centric platforms like YouTube, the plugin integrates yt-dlp to extract captions and metadata that are otherwise inaccessible via standard HTTP requests.

Operational Boundaries
The tool adheres to a strict "public-access only" policy. It does not engage in credential-based authentication, bypass paywalls, or store user logins. If a resource requires a login, the plugin detects the authentication wall and returns an error state, ensuring it remains a reader for public information rather than an unauthorized access tool. The plugin is self-contained, handling the auto-installation of necessary dependencies (such as curl_cffi and yt-dlp) upon first invocation to ensure a zero-setup user experience.