Panniantong
|
62aacf38b5
|
feat: migrate Twitter backend from bird CLI to xreach CLI
bird CLI (@steipete/bird) is deprecated and no longer maintained.
xreach CLI (xreach-cli on npm) is our maintained fork with:
- Fixed SearchTimeline (POST + updated query ID)
- Built-in proxy rotation support
- Additional features (DMs, notifications, lists)
Changes across 11 files:
- channels/twitter.py: detect xreach instead of bird/birdx
- cli.py: install/doctor/uninstall all reference xreach-cli
- SKILL.md: updated command examples (bird read → xreach tweet)
- guides/setup-twitter.md: rewritten for xreach
- docs/troubleshooting.md: updated proxy guidance
- README.md + README_en.md: all references updated
- config.py: twitter_bird → twitter_xreach
- core.py, mcp_server.py: comment updates
npm package: https://www.npmjs.com/package/xreach-cli
Source: https://github.com/Panniantong/xfetch
|
2026-02-27 08:17:51 +01:00 |
|
Panniantong
|
a37e9aa190
|
refactor: strip to installer + doctor + docs, remove read/search wrapper layer
BREAKING CHANGE: Remove all `agent-reach read` and `agent-reach search-*` commands.
Agent Reach is now an installer, configuration tool, and doctor —
not a wrapper layer. After installation, agents call upstream tools
directly (bird CLI, yt-dlp, mcporter, gh CLI, Jina Reader, etc.).
What's kept:
- agent-reach install: one-shot installer
- agent-reach doctor: channel status overview
- agent-reach configure: cookies, proxy, credentials
- agent-reach setup: interactive wizard
- SKILL.md: complete guide for agents to use upstream tools directly
What's removed:
- agent-reach read URL (and all channel read() methods)
- agent-reach search-* commands (and all channel search() methods)
- ReadResult / SearchResult data classes
- URL routing system (get_channel_for_url)
- All parsing/conversion logic (VTT, Reddit JSON, bird text parser, etc.)
- MCP server read/search tools (kept only get_status)
Net change: -1790 lines. Less code = fewer bugs.
|
2026-02-26 08:15:56 +01:00 |
|
Panniantong
|
f70711e75e
|
remove(instagram): 移除 Instagram 渠道
Instagram 反爬封杀导致所有开源工具（instaloader 等）失效，
无论有无 cookies 都无法正常使用。
- 删除 instagram.py 渠道文件
- 移除 CLI 中 search-instagram、configure instagram-cookies 等命令
- 移除 setup/doctor 中 instaloader 依赖检查
- 更新 README、docs、SKILL.md、pyproject.toml
上游 issue: instaloader#2585, instaloader#2648
Relates to: #13
|
2026-02-26 07:20:13 +01:00 |
|
Panniantong
|
e3804108fe
|
feat: 新增 Instagram、LinkedIn、Boss直聘 三个渠道
新增渠道：
- Instagram: 基于 instaloader (⭐9.8K)，读取帖子/Profile，Cookie 登录
- LinkedIn: 基于 linkedin-scraper-mcp (⭐900+) MCP 服务，Jina Reader fallback
- Boss直聘: 基于 mcp-bosszp MCP 服务，Jina Reader fallback
代码改动：
- 新建 channels/instagram.py, linkedin.py, bosszhipin.py
- 注册到 channels/__init__.py
- cli.py 添加 search-instagram/linkedin/bosszhipin 子命令
- cli.py 安装逻辑添加 instaloader 自动安装
- core.py 添加 search_instagram/linkedin/bosszhipin 方法
- README.md + docs/README_en.md 更新平台表格和选型表格
- docs/install.md 添加三个新渠道的配置说明和 Quick Reference
|
2026-02-25 10:25:30 +01:00 |
|
Panniantong
|
93ad9c5722
|
fix: birdx → bird CLI (npm @steipete/bird)
birdx 从来不是 PyPI 包，pip install birdx 必然失败。
实际工具是 npm 包 @steipete/bird，一个 Twitter GraphQL CLI。
变更：
- 安装器改用 npm install -g @steipete/bird
- twitter.py 直接调 bird，通过环境变量传 AUTH_TOKEN/CT0
- 兼容已有的 birdx wrapper（shutil.which 回退）
- 更新所有文档引用
- 重写 setup-twitter.md 指南
|
2026-02-25 04:02:42 +01:00 |
|
Panniantong
|
7d0da09222
|
feat: 新增 YouTube/Bilibili/XHS 搜索 CLI 命令 + 修复 B站搜索
- cli.py: 新增 search-youtube / search-bilibili / search-xhs 子命令
- core.py: 新增 search_youtube / search_bilibili / search_xhs 方法
- bilibili.py: 搜索策略改为 yt-dlp → Exa fallback（服务器 IP 被 B站 412）
- 本地机器走 yt-dlp bilisearch（有 title/uploader）
- 服务器自动 fallback 到 Exa site:bilibili.com
- 修复 mcporter 输出解析（Title:/URL: 格式）
测试结果: 15/15 全通（8 read + 7 search）
|
2026-02-24 13:39:21 +01:00 |
|
Panniantong
|
5c62a21f32
|
rename: Agent Eyes → Agent Reach
全局重命名：
- 包名: agent_eyes → agent_reach
- CLI: agent-eyes → agent-reach
- 类名: AgentEyes → AgentReach
- 显示名: Agent Eyes → Agent Reach
- GitHub: Panniantong/agent-eyes → Panniantong/Agent-Reach
所有 36 个测试通过，CLI/doctor/read/search 全部正常。
|
2026-02-24 10:25:46 +01:00 |
|