Agent-Reach Review: Free Internet Access for AI Agents

TL;DR

Agent-Reach is the “give your AI agent eyes for the internet” CLI that hit GitHub Trending this week with 22,815 stars and 1,513 new in seven days. It’s a Python installer that wires up 16+ web and social platforms — Twitter/X, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu, Douyin, LinkedIn, WeChat, Weibo, V2EX, Xueqiu, plus web/RSS — for any agent that can run shell commands.

Zero API fees: every channel uses Cookie auth, public scraping, or free MCP services (Exa, Jina Reader). Only optional cost: ~$1/month residential proxy if you need Bilibili from an overseas server.
One-line install: paste a URL to your agent, it pip-installs the CLI, detects laptop vs server, installs system deps (Node, gh, mcporter, twitter-cli, rdt-cli), and registers a SKILL.md in your agent’s skills directory.
Scaffolding, not a framework: agents call upstream tools directly (twitter search, rdt search, yt-dlp, gh) — swap any channel by editing one file.
Cookie-based auth: for Twitter, XHS, Reddit, LinkedIn you export cookies via the Cookie-Editor Chrome extension and paste them — simpler than QR, no Docker.
Self-diagnostic: agent-reach doctor lists every channel’s status in one command.
Works with Claude Code, Cursor, OpenClaw, Windsurf, Codex CLI — anything that can exec.
“Pure vibe coding” by the author’s admission — no test suite, the architecture is install + delegate.

If you’ve ever told an agent “check Twitter for X” and watched it return a 403, this is the most useful 60 seconds of install time you’ll spend this month.

Quick Reference

Field	Value
Repo	Panniantong/Agent-Reach
Author	Panniantong (solo + vibe-coded with Claude)
Stars	22,815 (+1,513 this week)
Language	Python
License	Open source (per repo)
Install	`pip install agent-reach && agent-reach install --env=auto`
Safe mode	`agent-reach install --env=auto --safe` (lists deps, doesn’t auto-install)
Dry run	`agent-reach install --env=auto --dry-run`
Diagnostics	`agent-reach doctor`
Uninstall	`agent-reach uninstall`
Compatible agents	Claude Code, Cursor, OpenClaw, Windsurf, Codex CLI, Hermes
Platforms	16+: Web, YouTube, RSS, GitHub, Twitter, Bilibili, Reddit, XHS, Douyin, LinkedIn, WeChat, Weibo, V2EX, Xueqiu, Xiaoyuzhou, Exa search

What It Is

Agent-Reach is a scaffolding installer, not a wrapper library. The problem: every time you onboard a new AI agent, you re-discover it can’t read Twitter (API costs), can’t load Reddit (403s the cloud IP), can’t get YouTube transcripts, and drowns in <div> soup on any non-trivial page. Each platform has its own moat — paid API, geo-block, login wall, anti-bot — and getting them all working takes a wasted afternoon.

Agent-Reach does that afternoon’s work once. Run one command and your agent has:

A working CLI for each platform (twitter, rdt, xhs, gh, yt-dlp, etc.) on $PATH.
An agent-reach doctor health check showing which channels are configured.
A SKILL.md registered in your agent’s skills directory — so when you say “search Twitter for X,” the agent knows to call twitter search "X" instead of guessing.

The agent then calls upstream tools directly, bypassing Agent-Reach after install. Same scaffolding pattern that makes Superpowers feel useful — the actual work is done by best-in-class third-party tools; the scaffolding is just the wiring harness.

Three things converged in early June 2026:

1. Cookie-auth as the new normal. After Reddit’s 2024 API moves, X’s $200/month enterprise pricing, and Bilibili’s geo-block, every open-source agent project rediscovered the same answer: ship cookie-based clients and let users log in via browser. Agent-Reach is the first project to package all of them in one install.

2. Coding-agent skill formats matured. Claude Code, OpenClaw, Cursor, and Windsurf now read a standard SKILL.md from a known directory. Agent-Reach registers one skill file per platform, so as soon as install finishes, the agent knows “Twitter search → twitter search; Reddit comments → rdt comments.” No prompt engineering required.

3. MCP discoverability. MCP servers exist for almost every platform now (Exa, douyin-mcp-server, linkedin-scraper-mcp), but discovering and wiring them is a chore. Agent-Reach uses mcporter to register every needed MCP in one shot.

Universal cookie auth + standard skill format + MCP autoconfig is what’s driving 1,513 stars in a week.

Key Features (With Code)

1. One-paste install for any agent

Paste this to Claude Code, Cursor, or OpenClaw:

帮我安装 Agent Reach: https://raw.githubusercontent.com/Panniantong/agent-reach/main/docs/install.md

(Or in English: “Install Agent Reach for me: [URL]”) — the agent fetches the markdown, follows the steps, asks for proxy/Cookie config when needed, and runs agent-reach doctor to verify.

Under the hood, that’s pip install agent-reach && agent-reach install --env=auto. The --env=auto flag detects laptop vs server and adjusts the proxy advice accordingly.

2. Channel-by-channel use

Once installed, your agent calls upstream tools directly. No Agent-Reach in the call path.

# Read any webpage (Jina Reader, no API key)
curl https://r.jina.ai/https://example.com/article

# Search Twitter (twitter-cli, cookie auth)
twitter search "Andrej Karpathy"
twitter tweet https://x.com/elonmusk/status/1234567890

# Search and read Reddit (rdt-cli, cookie auth)
rdt search "Claude Code review" --subreddit ClaudeAI
rdt read abc123    # Full post + all comments

# YouTube subtitles + metadata (yt-dlp, no auth)
yt-dlp --write-sub --skip-download "https://youtube.com/watch?v=xyz"
yt-dlp --dump-json "https://youtube.com/watch?v=xyz"

# GitHub (gh CLI, OAuth)
gh repo view Panniantong/Agent-Reach
gh search repos "LLM agent framework" --stars=">1000"

# Semantic web search (Exa via mcporter, free)
mcporter call "exa.search(query='best open-source agent memory 2026')"

# XiaoHongShu / Xiaohongshu (xhs-cli, cookie auth)
xhs search "AI coding agent"
xhs read NOTE_ID

The agent doesn’t need to remember any of these commands — that’s what the registered SKILL.md files are for. You say “check Reddit for what people are saying about Claude 4” and the agent calls rdt search "Claude 4" --subreddit ClaudeAI --time week on its own.

3. The `doctor` command

$ agent-reach doctor

🩺 Agent Reach Doctor

🌐 web (Jina Reader)         ✅ Working
📺 youtube (yt-dlp)          ✅ Working
📡 rss (feedparser)          ✅ Working
🔍 exa (mcporter)            ✅ Working — free, no key
📦 github (gh)               ✅ Authenticated as andrew
🐦 twitter (twitter-cli)     ⚠️  Not configured — run: twitter login
📺 bilibili (yt-dlp)         ✅ Working (local IP)
📖 reddit (rdt-cli)          ✅ Authenticated as andrew-ooo
📕 xiaohongshu (xhs-cli)     ⚠️  Not configured — run: xhs login
🎵 douyin (mcporter)         ✅ Working
💼 linkedin (mcporter)       ⚠️  Not configured — see docs/linkedin.md
💬 wechat (Exa)              ✅ Working
📰 weibo (built-in)          ✅ Working
💻 v2ex (built-in)           ✅ Working
📈 xueqiu (built-in)         ⚠️  Not configured — see docs/xueqiu.md
🎙️ xiaoyuzhou (whisper)      ⚠️  Not configured — see docs/xyz.md

Configured: 10/16    Needs config: 6/16    Broken: 0

This is the killer feature for multi-agent setups. When something stops working — say, Twitter rotates their cookie format — doctor flags the broken channel and points to the fix.

4. Swap any channel

Each channel lives in one file:

channels/
├── web.py        → Jina Reader      (swap: Firecrawl, Crawl4AI)
├── twitter.py    → twitter-cli      (swap: official API, Nitter)
├── reddit.py     → rdt-cli          (swap: PRAW)
├── youtube.py    → yt-dlp           (swap: YouTube API, Whisper)
├── github.py     → gh CLI           (swap: PyGithub, REST)
├── bilibili.py   → yt-dlp           (swap: bilibili-api)
├── xiaohongshu.py→ mcporter MCP     (swap: any XHS tool)
├── douyin.py     → mcporter MCP     (swap: yt-dlp where supported)
├── linkedin.py   → linkedin-mcp     (swap: LinkedIn API)
├── wechat.py     → Exa + Camoufox   (swap: any WeChat tool)
├── rss.py        → feedparser       (swap: atoma)
└── exa_search.py → mcporter         (swap: Tavily, SerpAPI, Brave)

Each file only implements a check() method that tells doctor whether the upstream tool is installed and authenticated. Real reads/searches are done by the upstream tool, not by Agent-Reach. This is why the project can ship at 16+ platforms without becoming a maintenance nightmare — most of the surface area lives in projects like yt-dlp (154K stars) and Jina Reader (9.8K stars) that have their own maintainer ecosystems.

5. Safe mode and dry run

agent-reach install --env=auto --safe     # lists deps, doesn't auto-install
agent-reach install --env=auto --dry-run  # previews everything, runs nothing

Safe mode never installs system packages — it prints what would be installed and lets you run it yourself. Dry run lists every operation (pip, brew, mcporter, skill files, config writes) without executing anything. Pair them on production servers to audit before agreeing.

Real-World Use Cases

Daily research digest. Cron-trigger your agent: “Pull the top 5 posts from r/LocalLLaMA today and the top 3 tweets from @karpathy this week. Summarize.” All channels free, no API budget.

Competitive product monitoring. Twitter search for competitors, Reddit search for product complaints, XHS/Douyin for short-form mentions — weekly, no SaaS subscription.

Code-research assistant. Ask your coding agent: “Find the top 3 open-source projects similar to X on GitHub, then check HN and Reddit for how people describe them.” The agent uses gh search + Exa + rdt search natively.

Multilingual content research. Where Agent-Reach really shines — most Western agent tools can’t read XiaoHongShu, Douyin, Weibo, Bilibili, or WeChat. Agent-Reach treats them as first-class.

Community Reactions

Trending traffic is mostly Chinese AI Twitter and the Claude Code / Cursor / OpenClaw communities:

“Finally someone packaged all the cookie-auth CLIs into one install. I’ve been doing this manually for every project.” — HN comment (paraphrased)

“The doctor command is the killer feature. I have 4 agents on 2 machines and I always lose track of which one has Twitter set up.” — Reddit r/LocalLLaMA

“Calling it ‘pure vibe coding’ in the README is refreshing. Most projects this size pretend they have a test suite.” — Tweet thread, anonymized

Predictable criticism: this is “just an installer,” you could write the shell script yourself in an evening. True — but then you’d maintain it forever. Agent-Reach has 1.9K forks and a maintainer who daily-drives it. The value is coordination, not code volume.

Honest Limitations

No test suite. The README explicitly says “pure vibe coding 🎸”. If you’re putting this on a production server, you’re trusting the integration glue between 16 upstream tools to behave. The upstream tools are battle-tested; the glue is not.

Cookie auth has TOS implications. Twitter, XHS, Bilibili, and LinkedIn all forbid automated cookie-based access in their TOS. The README explicitly says “use a throwaway account, not your main.” You can absolutely get banned if a platform’s anti-bot system flags your traffic.

Cookies expire. Every 7–30 days, depending on platform. You’ll need to re-export and re-paste. This is fine for a single user with one machine; it’s a maintenance tax if you’re running Agent-Reach across multiple cron-driven agents.

Server access needs a proxy. Bilibili blocks overseas server IPs, so if you’re running an agent on a US/EU VPS and need Bilibili, you’ll need a Chinese residential proxy (~$1/month). The author calls this out clearly.

OpenClaw users need exec enabled. Agent-Reach depends on the agent being able to run pip install, mcporter, twitter, etc. OpenClaw’s default messaging tool profile doesn’t include exec. The fix: openclaw config set tools.profile "coding" then restart the Gateway. This is documented in the README but easy to miss.

Not a SaaS replacement for production traffic. If you need 10K+ requests/day to a single platform with SLAs, you still need the official paid API. Agent-Reach is for personal/research-scale agents, not consumer-facing apps.

Region bias. The platform coverage is heavily weighted toward Chinese platforms (XHS, Douyin, Weibo, Bilibili, V2EX, Xueqiu, Xiaoyuzhou, WeChat) plus the obvious Western ones (Twitter, Reddit, YouTube, GitHub, LinkedIn). If you need Mastodon, Threads, Bluesky, TikTok (US), or Pinterest, you’ll have to wire them up yourself.

The install URL pattern is unusual. Telling your agent “install this thing by reading a URL” is fine in a Claude Code session you trust, but if the install.md ever gets compromised or hijacked, the agent will run whatever’s there. Pin a commit SHA in production.

How It Compares to Other Agent Tools

vs. Composio: paid SaaS, 250+ integrations, managed auth, supports writes. Agent-Reach is free, self-hosted, read/search only. Use Composio if your agent posts; Agent-Reach if it just reads.
vs. mcporter: mcporter is an Agent-Reach dependency (used for Exa, Douyin, LinkedIn, XHS). If you only need MCP-based platforms, mcporter alone is enough.
vs. Browser-use: drives Chromium for any site — slower, heavier, breaks more, but works on sites with no CLI. Use Browser-use as the fallback layer for sites Agent-Reach doesn’t cover.
vs. last30days-skill (29K stars, also trending): last30days synthesizes topic research across Reddit, X, YouTube, HN, Polymarket. Agent-Reach is the plumbing underneath. last30days could plausibly be reimplemented on top of Agent-Reach.

How to Install in 60 Seconds

# 1. Install the CLI
pip install agent-reach

# 2. Run the auto installer
agent-reach install --env=auto

# 3. Verify
agent-reach doctor

# 4. Configure the platforms you actually need (cookie auth)
twitter login    # if you want Twitter
rdt login        # if you want Reddit (note: 2024+ requires auth)
xhs login        # if you want XiaoHongShu
gh auth login    # if you want private GitHub repos

That’s it. Your agent can now read 10+ platforms with zero API cost.

If you want the agent to do the install for you, paste this:

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

The agent will fetch the markdown, walk you through Cookie-Editor exports for any platforms that need auth, and run doctor at the end.

FAQ

Is Agent-Reach really free?

Yes. 100% of the upstream tools (twitter-cli, rdt-cli, xhs-cli, yt-dlp, Jina Reader, Exa via MCP, gh CLI, feedparser, mcporter) are open source with no required API keys. The only optional cost is a ~$1/month residential proxy if you need Bilibili from an overseas server.

Yes — Twitter, XHS, Bilibili, and LinkedIn forbid automated access in their TOS, and anti-bot systems can flag accounts. The README recommends a throwaway account dedicated to agent use, not your main.

Does it work with Claude Code, Cursor, OpenClaw, Windsurf?

Yes — any AI coding agent that can run shell commands. Agent-Reach installs a SKILL.md per platform into the agent’s skills directory so the agent auto-discovers which CLI to call. OpenClaw users specifically need tools.profile: "coding" (or any profile with exec) before running the install; the default messaging profile doesn’t have exec.

What happens when cookies expire?

Re-export with Cookie-Editor and paste them to the agent. Each platform CLI has a login command (twitter login, rdt login, xhs login) that takes the cookie and stores it locally in ~/.agent-reach/config.yaml (perms 600).

Does it work on servers, not just laptops?

Yes, with two caveats: (1) Bilibili needs a residential proxy because their geo-block hits VPS IPs (~$1/month). (2) Reddit 403s VPS IPs more aggressively than residential; rdt-cli with valid cookies usually works. Twitter, GitHub, YouTube, RSS, web reading, and Exa search are fine anywhere.

My Honest Take

Most agent tooling is a wrapper around something else, and the wrapper is the buggy part. Agent-Reach is structured to be not the buggy part — it installs, registers skills, runs the diagnostic, then gets out of the way. The actual reads/searches go through yt-dlp (154K stars, 13 years old) and Jina Reader (9.8K stars, weekly releases) — way more reliable than anything a single maintainer would build from scratch.

The value isn’t the code, it’s the inventory decisions. Someone picked the right Twitter CLI, the right Reddit CLI, the right XHS tool, the right Douyin MCP, configured Exa for free search, and registered a SKILL.md per platform so agents auto-discover them. Hours of integration work you don’t have to do.

Caveats: no tests, vibe-coded, cookie auth has TOS risks. Use a throwaway account, pin the install URL to a commit SHA in production, run doctor weekly. With those three rules, this is the lowest-friction way I’ve found to give a coding agent free internet eyes.

Try Agent-Reach: github.com/Panniantong/Agent-Reach

Related reads on andrew.ooo: