👁️ Agent Reach

Give your AI Agent one-click access to the entire internet

Quick Start · 中文 · Platforms · Philosophy

AI Agents can already access the internet — but "can go online" is barely the start.

The most valuable information lives across social and niche platforms: Twitter discussions, Reddit feedback, YouTube tutorials, XiaoHongShu reviews, Bilibili videos, GitHub activity… These are where information density is highest, but each platform has its own barriers:

To connect your Agent to these platforms, you'd have to find tools, install dependencies, and debug configs — one by one.

Agent Reach turns this into one command:

Install Agent Reach: https://raw.githubusercontent.com/Panniantong/agent-reach/main/docs/install.md

Copy that to your Agent. A few minutes later, it can read tweets, search Reddit, and watch Bilibili.

Setup levels: Zero config = install and go · Auto-configured = handled during install · mcporter = needs MCP service · Cookie = export from browser · Proxy = $1/month

Copy this to your AI Agent (Claude Code, OpenClaw, Cursor, etc.):

Install Agent Reach: https://raw.githubusercontent.com/Panniantong/agent-reach/main/docs/install.md

The Agent auto-installs, detects your environment, and tells you what's ready.

pip install https://github.com/Panniantong/agent-reach/archive/main.zip
agent-reach install --env=auto

npx skills add Panniantong/Agent-Reach@agent-reach

No configuration needed — just tell your Agent:

• "Read this link" → curl https://r.jina.ai/URL for any web page
• "What's this GitHub repo about?" → gh repo view owner/repo
• "What does this video cover?" → yt-dlp --dump-json URL for subtitles
• "Read this tweet" → xreach tweet URL --json
• "Subscribe to this RSS" → feedparser to parse feeds
• "Search GitHub for LLM frameworks" → gh search repos "LLM framework"

No commands to remember. The Agent reads SKILL.md and knows what to call.

Don't use it? Don't configure it. Every step is optional.

Tell your Agent "help me configure Twitter cookies" — it'll guide you through exporting from your browser. Local computers can auto-import.

Reddit and Bilibili block server IPs. Get a proxy (Webshare recommended, $1/month) and send the address to your Agent.

Local computers don't need a proxy. Reddit search works free via Exa even without one.

$ agent-reach doctor

👁️  Agent Reach Status
========================================

✅ Ready to use:
  ✅ GitHub repos and code — public repos readable and searchable
  ✅ Twitter/X tweets — readable. Cookie unlocks search and posting
  ✅ YouTube video subtitles — yt-dlp
  ⚠️  Bilibili video info — server IPs may be blocked, configure proxy
  ✅ RSS/Atom feeds — feedparser
  ✅ Web pages (any URL) — Jina Reader API

🔍 Search (free Exa key to unlock):
  ⬜ Web semantic search — sign up at exa.ai for free key

🔧 Configurable:
  ⬜ Reddit posts and comments — search via Exa (free). Reading needs proxy
  ⬜ XiaoHongShu notes — needs cookie. Export from browser

Status: 6/9 channels available

Agent Reach is a scaffolding tool, not a framework.

Every time you spin up a new Agent, you spend time finding tools, installing deps, and debugging configs — what reads Twitter? How do you bypass Reddit blocks? How do you extract YouTube subtitles? Every time, you re-do the same work.

Agent Reach does one simple thing: it makes those tool selection and configuration decisions for you.

After installation, your Agent calls the upstream tools directly (xreach CLI, yt-dlp, mcporter, gh CLI, etc.) — no wrapper layer in between.

Each platform maps to an upstream tool. Don't like one? Swap it out.

channels/
├── web.py          → Jina Reader     ← swap to Firecrawl, Crawl4AI…
├── twitter.py      → xreach            ← swap to Nitter, official API…
├── youtube.py      → yt-dlp          ← swap to YouTube API, Whisper…
├── github.py       → gh CLI          ← swap to REST API, PyGithub…
├── bilibili.py     → yt-dlp          ← swap to bilibili-api…
├── reddit.py       → JSON API + Exa  ← swap to PRAW, Pushshift…
├── xiaohongshu.py  → mcporter MCP    ← swap to other XHS tools…
├── douyin.py       → mcporter MCP    ← swap to other Douyin tools…
├── linkedin.py     → linkedin-mcp    ← swap to LinkedIn API…
├── bosszhipin.py   → mcp-bosszp      ← swap to other job tools…
├── rss.py          → feedparser      ← swap to atoma…
├── exa_search.py   → mcporter MCP    ← swap to Tavily, SerpAPI…
└── __init__.py     → Channel registry (for doctor checks)

Each channel file only checks whether its upstream tool is installed and working (check() method for agent-reach doctor). The actual reading and searching is done by calling the upstream tools directly.

📌 These are the current choices. Don't like one? Swap out the file. That's the whole point of scaffolding.

This project was entirely vibe-coded 🎸 There might be rough edges here and there — sorry about that! If you run into any bugs, please don't hesitate to open an Issue and I'll fix it ASAP.

Want a new channel? Open an Issue to request it, or submit a PR yourself.

Want to add one locally? Just have your Agent clone the repo and modify it — each channel is a single standalone file, easy to add.

PRs always welcome!

Jina Reader · yt-dlp · xreach · Exa · feedparser · douyin-mcp-server · linkedin-scraper-mcp · mcp-bosszp

MIT