English | 한국어 | 中文 | 日本語 | Español

---

⚡ Install

/plugin marketplace add https://github.com/fivetaku/gptaku_plugins.git
/plugin install insane-search@gptaku-plugins
/reload-plugins

No commands to learn. Ask Claude Code normally — insane-search kicks in when a fetch gets blocked.

💬 Try it

Just ask normally — insane-search kicks in when a fetch gets blocked:

"Find what people are saying about Claude Code on Reddit and summarize the top threads." "Search X for posts about insane-search." "Summarize this YouTube video."

Expected: Claude reaches each site's public route — Reddit's feed, X via oEmbed, YouTube captions — with no login and no API key, and returns usable text, where the same request returns "I can't access that" without the plugin.

🌐 Works on

X · Reddit · YouTube · Hacker News · Naver · Coupang · LinkedIn · Medium · Substack · arXiv · GitHub · Stack Overflow · Bluesky · Mastodon — plus any site with a public page, feed, or /rss. Full platform list & methods → PLATFORMS.md.

⚙️ Why it gets through

• It escalates, never pre-judges — public API readers → syndication gateways → TLS impersonation → a real headless browser, trying each route until one works.
• It looks human — builds a full browser identity (real TLS fingerprint, cookie warming, referer chain), not just a swapped User-Agent.
• Zero setup — auto-installs what it needs (curl_cffi, yt-dlp, …) on first use. No API keys, no signup.

🆚 Default Claude Code vs + insane-search

When you hit…	Claude Code alone	+ insane-search
A 403 / WAF-blocked page	✖ gives up	✓ escalates until one route gets through
Platform content (X, Reddit, HN)	✖ often blocked or empty	✓ public API readers + syndication
An anti-bot / CAPTCHA challenge	✖ stops	✓ TLS impersonation, then a real headless browser
A media page (YouTube, 1,800+ sites)	✖ no transcript	✓ yt-dlp metadata + captions
Missing tools (curl_cffi, yt-dlp)	—	✓ auto-installs on first use
API keys / signup	—	✓ none
A login wall or paywall	✖	✖ stops here, and says so (see Boundaries)

The differentiating row is the one thing the default fetcher can't do: it keeps trying public routes until one works.

✨ What just happened

Without it	With insane-search
Ordinary fetch hits 403 and Claude says it can't read the page	The plugin picks a public-access route and returns usable text
You manually try mirrors, archives, mobile URLs	Fallbacks escalate automatically, public-only
A blocked page is a dead end	Metadata and structured data still yield titles, prices, summaries

🔁 How it works

Phase 0→3 adaptive scheduler — details

Each phase runs only if the previous one fails or detects a blocking signal:

• Phase 0 — special public endpoints (platform APIs, feeds) it can't discover generically
• Phase 1 — lightweight probes: public API readers, syndication gateways, mobile / .json / /rss URL variants
• Phase 2 — TLS impersonation (curl_cffi: safari → chrome → firefox) with a full browser identity
• Phase 3 — a real headless browser for JS-rendered pages
• Exit — a login or paywall is detected: it reports "authentication required" rather than pretending

Every response is also scanned for OGP / JSON-LD, so even partial pages yield titles, summaries, and prices.

🔒 Boundaries

insane-search is a reader for public content, not a way around authentication.

• Reaches what's available through public pages, public APIs, feeds, archives, and a browser's public responses.
• Stops at logins and paywalls — it reports authentication required instead of trying to defeat them.
• Never logs in as you and never stores or transmits credentials.
• All routes use no-auth public endpoints and standard, documented techniques.
• You are responsible for lawful, authorized use — each site's Terms of Service, robots.txt, rate limits, and applicable law. This is a dual-use developer tool; see DISCLAIMER.md.

License

MIT — see DISCLAIMER.md for acceptable-use and user-responsibility terms.

---