Your agent can write the PR. It still cannot read the tweet that reported the bug — until you give it eyes.
Agent Reach (Panniantong/Agent-Reach, MIT, ~65K stars) is a capability layer: it chooses today’s working free backends, installs them, runs agent-reach doctor, and routes channels so Claude Code / OpenClaw / Cursor can fetch YouTube captions, X posts, Reddit threads, Bilibili, Xiaohongshu, GitHub, RSS, and web pages without you becoming a full-time anti-bot engineer.
Tagline: Give your AI agent eyes to see the entire internet. The deeper claim: access methods churn; your skill file should not.
TL;DR
| Item | Detail |
|---|---|
| Repo | Panniantong/Agent-Reach |
| Install | One prompt → docs/install.md raw URL |
| Update | Same pattern → docs/update.md |
| Doctor | agent-reach doctor — what’s green / how to fix |
| Model | Preferred + fallback backends per platform |
| Money | Free tools; optional ~$1 proxy on servers |
| Privacy | Cookies local; open source; --safe / --dry-run |
| Works with | Claude Code, OpenClaw, Cursor, Windsurf, … |
The problem it kills
Typical agent fails:
| Ask | Usual failure |
|---|---|
| Summarize this YouTube | No captions path |
| Search X for product takes | Paid API or login wall |
| Reddit same bug? | 403 on datacenter IP |
| Xiaohongshu / Bilibili | Login or risk-control blocks |
| “Read this page” | Raw HTML sludge |
None of these are intellectually hard. All of them are config debt. Agent Reach turns that debt into: tell the agent to install Agent Reach.
Install in one sentence
帮我安装 Agent Reach：https://raw.githubusercontent.com/Panniantong/agent-reach/main/docs/install.md
English-equivalent: ask your agent to follow that install markdown. Variants:
- Safe mode — no auto system packages; lists what you must approve (
--safe). - Dry run — preview only.
- Update — point at
docs/update.mdthe same way.
OpenClaw caveat: enable exec / tools.profile: "coding" and restart the gateway before install, or the agent cannot run pip / CLIs.
After install, you do not memorize commands — the agent reads SKILL.md and picks tools.
Uninstall / reset without drama
agent-reach uninstall # config + skills + mcporter bits
agent-reach uninstall --dry-run # preview
agent-reach uninstall --keep-config # keep tokens; wipe skills for reinstall
pip uninstall agent-reach
Secrets live under ~/.agent-reach/. Treat that directory like SSH keys when you wipe a laptop.
Platform matrix (mental model)
| Platform | Zero-config-ish | After config |
|---|---|---|
| Web | Jina Reader | — |
| YouTube | yt-dlp captions + search | — |
| RSS | feedparser | — |
| GitHub | gh public | login for private / PRs |
| X/Twitter | single tweet paths | Cookie-Editor / twitter-cli / OpenCLI |
| Bilibili | bili-cli search/detail | OpenCLI for richer paths |
| — (anon dead) | OpenCLI or rdt-cli + cookies | |
| Facebook / Instagram | — | OpenCLI desktop session |
| Xiaohongshu | — | OpenCLI session or Cookie-Editor → MCP |
| Jina public pages | linkedin MCP | |
| Exa search | — | mcporter MCP (free keyless path per README) |
| V2EX / Xueqiu / podcasts | varies | see channel docs |
2026-06 lesson they document: yt-dlp got 412’d by Bilibili risk control → route flipped to bili-cli. Users did not rewrite skills. That is the product.
Zero-config wins first
On a fresh laptop, the highest-ROI checks after doctor goes green:
- Web — Jina Reader via
https://r.jina.ai/URL(agent usually wraps this). - YouTube — captions + search through yt-dlp.
- GitHub —
gh repo view/ search for public repos. - RSS — feedparser for monitoring sources.
- Bilibili search — bili-cli without login for many read paths.
Only then spend the cookie/OpenCLI budget on X, Reddit, Xiaohongshu, Facebook, Instagram. That order keeps “eyes” useful before you touch high-risk credentials.
Architecture: channels as ordered backends
channels/
├── web.py → Jina Reader
├── twitter.py → twitter-cli ▸ OpenCLI ▸ bird
├── youtube.py → yt-dlp
├── bilibili.py → bili-cli ▸ OpenCLI ▸ search API
├── reddit.py → OpenCLI ▸ rdt-cli
├── xiaohongshu.py → OpenCLI ▸ xiaohongshu-mcp ▸ xhs-cli
└── ...
doctor probes candidates (not just which), elects the first healthy backend, and prints repair tips. Reads still go to upstream tools directly — Agent Reach is the selection + install + health layer, not a second HTTP proxy wrapping every GET.
Capability layer vs “another scraper package”
The README’s design claim is the important one: Agent Reach sits above concrete readers. It selects, installs, doctors, and reorders; it does not re-implement every site’s HTML parser. When a single-platform CLI dies (the 2026 wave of abandoned CLIs), maintainers change channel order instead of forcing every Claude skill rewrite. That is why it pairs cleanly with agent skills and OpenClaw claws — your skill says “use Agent Reach / follow SKILL.md,” not “hard-code twitter-cli forever.”
For research workflows that already touch Reddit/X/YouTube, compare last30days-style skills: those encode a search recipe; Agent Reach encodes how the pipes stay alive.
Hard pages: when BrowserAct shows up
Dynamic sites with filters, pagination, and multi-step navigation sit outside “curl a reader URL.” The README points at BrowserAct-style browser bots for structured extraction with stealth/proxy options. Treat that as an optional commercial escalator — not part of the free core channel matrix.
Security (read this before cookies)
| Control | Detail |
|---|---|
| Local secrets | ~/.agent-reach/config.yaml mode 600 |
| Safe install | --safe / --dry-run |
| Open source | Audit channels; delete one file to drop a backend |
| Cookie policy | Prefer alt accounts; ban risk is real |
| OpenCLI | Reuses user-controlled Chrome sessions; docs spell out what it will not auto-inject |
Twitter cookies via Cookie-Editor for doctor completeness still need env vars for direct upstream twitter CLIs — follow current README; auth guidance tightened in recent commits.
Cookie policy nuances the README emphasizes: Twitter expects user-exported Cookie-Editor content; Agent Reach does not silently scrape Xiaohongshu login for you; OpenCLI only reuses Chrome sessions you already control. configure xhs-cookies does not inject cookies into OpenCLI/Chrome — if there is no session, export manually into the MCP / legacy tool path. That friction is a feature when the alternative is an agent stealing your main-account session.
Ban risk is not theoretical: platforms detect non-browser API patterns. Use alt accounts for X / XHS / Reddit automation. Local desktop usually needs no proxy; server deployments may need a cheap residential/proxy hop (~$1/mo as they estimate) so datacenter IPs stop eating 403s.
How it pairs with memory and curriculum
| Layer | Tool |
|---|---|
| Learn GenAI | Microsoft GenAI for Beginners |
| Remember team context | TencentDB Agent Memory v2 |
| See the live web | Agent Reach |
| Skills / MCP surface | explainx.ai /skills · /mcp-servers |
Reach without memory = every research session starts cold. Memory without reach = elegant amnesia about the outside world.
OpenClaw / Claude Code ops notes
| Runtime | Gotcha |
|---|---|
| OpenClaw | Default messaging tool profiles block pip / shell — set tools.profile to coding, restart gateway, new chat |
| Claude Code / Cursor | Usually fine if the agent can run terminal; still prefer --safe on shared machines |
| Headless VPS | Desktop-only OpenCLI channels (FB/IG/some Reddit paths) will not magically work — plan cookies/MCP or skip those platforms |
Once eyes work, feed durable findings into TencentDB Agent Memory so Scout’s web digests become Chat Memory / Wiki instead of dying in a scrollback buffer. For personal assistants, see What is OpenClaw?.
Agent Reach checklist
□ OpenClaw: enable coding/exec profile first
□ Install via raw install.md prompt (or --safe)
□ Run agent-reach doctor; fix red channels
□ Configure X / Reddit / XHS with alt accounts only
□ Try: YouTube summary, gh repo view, Jina page read
□ Unpin dead backends emotionally — trust doctor’s active route
□ Uninstall: agent-reach uninstall (--dry-run / --keep-config)
□ Pair with Memory Hub if you run multi-agent teams
Honest limitations
- Social platforms change anti-bot rules weekly — expect backend churn.
- “完全免费” still assumes you accept ToS risk of automation.
- Some channels require desktop OpenCLI — headless servers are harder.
- Not a substitute for official APIs when you need SLA write access.
- Star count (~65K) includes trend spikes; pin a release for prod.
- BrowserAct / commercial extractors mentioned as optional for hard sites — separate product.
Closing
Agent Reach is the missing “eyes” package for coding agents: free, multi-backend, self-diagnosing, and honest about cookies. Install it once; let doctor absorb the next platform crackdown.
Follow @explainx_ai when new channels land — and star upstream if you depend on their on-call against 403s.
Related on explainx.ai
- TencentDB Agent Memory v2
- Microsoft Generative AI for Beginners
- What is OpenClaw?
- OpenClaw + ChatGPT Plus / OAuth
- Hermes vs OpenClaw
- What are agent skills?
- MCP servers directory
- Cloudflare Computer agent runtime
Sources
- github.com/Panniantong/Agent-Reach — README, install.md, update.md
- docs/install.md
- Upstream tools credited in README: OpenCLI, twitter-cli, yt-dlp, Jina, Exa, bili-cli, …
Platform backends and cookie guidance reflect Agent Reach README as of mid/late 2026. Re-run doctor after upgrades — preferred backends change when platforms break.