Agent Reach - Internet Access for Agents
Give AI agents eyes to see the entire internet. One CLI, zero API fees. Read and search Twitter/X, Reddit, YouTube, GitHub, LinkedIn, RSS, and more - all locally via cookies, no paid APIs. 16K+ GitHub stars.
The Problem
AI agents can write code, edit docs, and manage projects - but asking them to fetch live information from the web hits a wall:
- Twitter/X search requires a paid API plan
- Reddit blocks server IPs with 403s
- YouTube transcript extraction needs tooling
- LinkedIn, XiaoHongShu, and similar platforms require authentication
- Generic web scraping returns raw HTML garbage
Each platform has its own authentication, rate limits, and anti-bot defenses. Configuring all of them from scratch takes hours per agent environment.
The Solution
Agent Reach is a capability layer - an installer, doctor, channel router, and skill-registration tool that sets up a curated stack of upstream CLI tools. After installation, agents call the upstream tools directly (twitter-cli/OpenCLI, yt-dlp, gh CLI, feedparser, Jina Reader, etc.) without going through Agent Reach as a runtime wrapper. Source: Agent Reach README/CLAUDE.md, 2026-07-01
Install is one command:
pipx install https://github.com/Panniantong/agent-reach/archive/main.zip
agent-reach install --env=auto
Architecture: Scaffolding, Not Framework
Agent Reach installs upstream tools and wires them together. Each channel is a pluggable file that can be swapped independently:
| Platform | Upstream Tool | Zero-Config | Example |
|---|---|---|---|
| Web (any page) | Jina Reader | Yes | curl -s "https://r.jina.ai/URL" |
| Web (fallback) | Defuddle - Web Content Extraction | Yes | npx defuddle parse URL --markdown |
| YouTube | yt-dlp | Yes | yt-dlp --dump-json URL |
| GitHub | gh CLI | Yes (public) | gh repo view owner/repo |
| RSS | feedparser | Yes | python3 -c "import feedparser; ..." |
| Twitter/X | twitter-cli -> OpenCLI -> browser-login fallback | Cookie needed | twitter search "query" -n 10 |
| OpenCLI -> rdt-cli | Login likely needed | rdt search "query" |
|
| linkedin-mcp -> Jina Reader | Cookie / public fallback | mcporter call 'linkedin.get_person_profile(...)' |
|
| Bilibili / XiaoHongShu | bili-cli / OpenCLI routes | Platform-dependent | channel-specific CLI |
| Exa Search | mcporter MCP | Yes (free) | mcporter call 'exa.web_search_exa(...)' |
Swap any channel by replacing or reordering its file in channels/. The current README explicitly treats each platform as an ordered backend list, so routing can change when a single-platform CLI breaks without changing the agent-facing skill. Source: Agent Reach README, 2026-07-01
Visual Artifact Review
The Japanese bookmark screenshot shows the Chinese README, not a product UI. It emphasizes the problem list: agents cannot easily read YouTube transcripts, Twitter/X search, Reddit bug reports, XiaoHongShu reputation, Bilibili videos, arbitrary webpages, GitHub issues, or RSS without platform-specific setup. The prompt block tells the user to ask an agent to install Agent Reach from the raw GitHub install doc, which matches the repo's current "install as a skill" positioning. Source: X/@so_ainsight visual artifact, 2026-04-07
Setup for Kevin's Environment
# Install core (zero-config channels: web, YouTube, GitHub, RSS, Exa)
pipx install https://github.com/Panniantong/agent-reach/archive/main.zip
agent-reach install --env=auto
# Add optional channels
agent-reach install --env=auto --channels=twitter,reddit
# Health check
agent-reach doctor
# Safe mode (preview, no auto-install)
agent-reach install --env=auto --safe
agent-reach install --env=auto --dry-run
Twitter/X requires cookie auth via Cookie-Editor Chrome extension:
agent-reach configure twitter-cookies "COOKIE_STRING"
Security Model
| Measure | Detail |
|---|---|
| Local-only credentials | Cookies stored at ~/.agent-reach/config.yaml, file permission 600 |
| Safe mode | --safe flag lists what's needed without auto-installing |
| Dry run | --dry-run previews all operations |
| Fully open source | Code and all upstream tools are auditable |
| Pluggable channels | Don't trust a component? Swap its file |
Use dedicated/secondary accounts for cookie-based platforms (Twitter, LinkedIn). Cookie auth = full login access; a secondary account limits blast radius.
Current security-sensitive issue to watch: GitHub issue #450 reports configure --from-browser over-collecting and persisting full browser cookie sets. This does not invalidate the tool, but it reinforces the existing rule: dedicated accounts, explicit channels, safe mode/dry run, and review ~/.agent-reach/config.yaml before trusting an install. Source: GitHub issues, 2026-07-01
Relationship to Other Tools
- NIA Docs - Docs as Filesystem for Agents - mounts documentation as filesystem. Agent Reach covers social/media platforms, nia-docs covers library/API docs. Complementary.
- Browser Testing Skills - full browser automation via CDP. Agent Reach is lighter - CLI-based, no browser instance needed. Use agent-browser for interactive UIs; Agent Reach for data fetching.
- Firecrawl / Crawl4AI - web scraping tools used in automations. Agent Reach includes Jina Reader for web but can swap in Firecrawl.
- Defuddle - Web Content Extraction - local fallback web reader by Kepano (Obsidian creator). No API dependency, outputs Obsidian-native Markdown. Used when Jina Reader is rate-limited or unavailable.
- Sherlock - username OSINT across 400+ platforms. Complements Agent Reach when the task is "where does this handle exist?" rather than "what are people saying about X?"
Multi-Step Research Pattern
Agent Reach enables agents to autonomously research across platforms:
- Search Twitter/X for real-time discussion (
twitter search "topic") - Pull YouTube video transcripts for depth (
yt-dlp --dump-json URL) - Check GitHub repos for implementations (
gh search repos "topic") - Read Reddit threads for community signal (
rdt search "topic") - Synthesize findings across all sources
This is the shift from "AI that relies on expensive APIs" to "AI that autonomously reads the net."
Timeline
- 2026-07-01 | Deep-reviewed the Japanese Agent Reach bookmark, local README screenshot, current repo README/CLAUDE.md, tags, and GitHub metadata. Current source snapshot:
agent-reachversion/tagv1.5.0, HEADe87bcdb17713c24513f6151d508f701b87dfd797, MIT, 48,254 stars, 3,836 forks; no PyPI package found, install remains GitHub zip/raw-doc based. Source: X/@so_ainsight, 2026-04-07; GitHub, 2026-07-01 - 2026-06-01 | Cross-linked Sherlock for username OSINT complement to platform read/search channels. Source: X bookmark enrichment absorption, 2026-06-01