Pnant
fc24fb699b
The one-liner entry docs were untouched by the backend upgrade — new users following "帮我安装 Agent Reach" would still get the old world. Now: - docs/install.md: xiaohongshu section rewritten (desktop OpenCLI with the one manual extension click / server xiaohongshu-mcp with QR + 150MB first-run warning / legacy xhs-cli kept as fallback); Reddit section says plainly there is no zero-config path; optional-channel menu gains OpenCLI; upstream table matches the new routing with a doctor --json pointer - docs/update.md: full rewrite — upgrade-only-what-exists tool refresh (incl. npm update for OpenCLI/mcporter, pinned git source for rdt-cli), one-time OpenCLI offer for desktops, skill sync now rides doctor's auto-sync instead of an inline python blob, WeChat-era content removed - check-update / watch: "update available" now leads with the one-liner (帮我更新 Agent Reach：<update.md>) which updates package + tools + skill; bare pip stays as the package-only alternative - fix: version compare was `!=` — a local build AHEAD of the latest release (installed from main during a release window) was told to "update" into a downgrade; now semantic tuple compare with fallback (+4 tests) - skill (zh+en): description gains a NOT-for boundary (fetch-only, no write ops, defer to dedicated skills); new standing rule — after substantial tasks run check-update and append a one-liner update hint to the wrap-up, never interrupting or nagging - SKILL_en.md restructured to the same three-layer skeleton as the Chinese version (124-line body, shared references/) instead of a 263-line everything-inline page Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
116 lines
4.3 KiB
Markdown
116 lines
4.3 KiB
Markdown
# Agent Reach — Update Guide
|
||
|
||
## For Humans
|
||
|
||
Copy this to your AI Agent:
|
||
|
||
```
|
||
帮我更新 Agent Reach：https://raw.githubusercontent.com/Panniantong/agent-reach/main/docs/update.md
|
||
```
|
||
|
||
Or in English:
|
||
|
||
```
|
||
Update Agent Reach: https://raw.githubusercontent.com/Panniantong/agent-reach/main/docs/update.md
|
||
```
|
||
|
||
---
|
||
|
||
## For AI Agents
|
||
|
||
### ⚠️ Workspace Rules
|
||
|
||
**Never create files, clone repos, or run commands in the agent workspace.** Use `/tmp/` for temporary work and `~/.agent-reach/` for persistent data.
|
||
|
||
### Goal
|
||
|
||
Update Agent Reach to the latest version, refresh upstream tools, migrate from retired backends, and verify everything works. The user should not need to do anything manually (except things only a human can do, like clicking a browser-extension install button).
|
||
|
||
### Step 1: Check current version
|
||
|
||
```bash
|
||
agent-reach check-update
|
||
```
|
||
|
||
If it says "已是最新版本", skip to Step 4 (verify). Otherwise continue.
|
||
|
||
### Step 2: Update Agent Reach package
|
||
|
||
```bash
|
||
pip install --upgrade https://github.com/Panniantong/agent-reach/archive/main.zip
|
||
```
|
||
|
||
> If pip complains about `externally-managed-environment` (PEP 668), the user
|
||
> originally installed via pipx or a venv — use the matching command:
|
||
> `pipx install --force https://github.com/Panniantong/agent-reach/archive/main.zip`
|
||
> or activate `~/.agent-reach-venv` first.
|
||
|
||
### Step 3: Refresh upstream tools
|
||
|
||
Run these to keep installed tools current. **Only upgrade what is already
|
||
installed — do not install new tools the user never asked for** (the one
|
||
exception: OpenCLI on desktop, see below).
|
||
|
||
```bash
|
||
# Python-based CLIs the user already has (upgrade keeps signatures fresh)
|
||
which twitter >/dev/null 2>&1 && { pipx upgrade twitter-cli 2>/dev/null || uv tool upgrade twitter-cli 2>/dev/null; }
|
||
which bili >/dev/null 2>&1 && { pipx upgrade bilibili-cli 2>/dev/null || uv tool upgrade bilibili-cli 2>/dev/null; }
|
||
which xhs >/dev/null 2>&1 && { pipx upgrade xiaohongshu-cli 2>/dev/null || uv tool upgrade xiaohongshu-cli 2>/dev/null; }
|
||
which yt-dlp >/dev/null 2>&1 && { pipx upgrade yt-dlp 2>/dev/null || uv tool upgrade yt-dlp 2>/dev/null || pip install -U yt-dlp 2>/dev/null; }
|
||
|
||
# rdt-cli is pinned to a git source (PyPI lags upstream)
|
||
which rdt >/dev/null 2>&1 && pipx install --force 'git+https://github.com/public-clis/rdt-cli.git' 2>/dev/null
|
||
|
||
# npm-based
|
||
which mcporter >/dev/null 2>&1 && npm update -g mcporter 2>/dev/null
|
||
which opencli >/dev/null 2>&1 && npm update -g @jackwener/opencli 2>/dev/null
|
||
```
|
||
|
||
**Desktop users without OpenCLI**: since v1.5.0 OpenCLI is the preferred
|
||
backend for 小红书/Reddit (and adds B站 subtitles) by riding the user's
|
||
browser session. Offer it once:
|
||
|
||
> "这次更新引入了 OpenCLI 后端（复用你的浏览器登录态，小红书/Reddit 零配置）。要装吗？装完只需你在 Chrome 商店点一次『添加扩展』。"
|
||
|
||
If yes: `agent-reach install --channels opencli` and guide them through the
|
||
extension click. If no, everything keeps working on existing backends.
|
||
|
||
### Step 4: Coexistence (DO NOT uninstall old tools)
|
||
|
||
**Never uninstall tools the user already has.** Retired backends (e.g. yt-dlp
|
||
no longer serves Bilibili; xhs-cli is no longer installed by default) keep
|
||
working as fallbacks where they still function. Agent Reach routes around
|
||
them automatically — removal is the user's call, not yours.
|
||
|
||
### Step 5: Verify
|
||
|
||
```bash
|
||
agent-reach version
|
||
agent-reach doctor
|
||
```
|
||
|
||
Running `agent-reach doctor` (text mode) also auto-syncs the bundled skill
|
||
(SKILL.md + references) into every detected agent skill directory — no
|
||
separate skill-update step is needed.
|
||
|
||
Check the doctor output:
|
||
|
||
- Every channel shows ✅ / [!] with a clear message, and multi-backend
|
||
channels (小红书/Reddit/B站/Twitter) report `当前后端：…`
|
||
- If a previously-working channel now shows [X]/error, the message contains
|
||
the exact fix (e.g. a venv-reinstall prescription) — run it, then re-check
|
||
- `--json` gives the same data machine-readably (`active_backend` per channel)
|
||
|
||
### Step 6: Report to user
|
||
|
||
Tell the user:
|
||
|
||
1. What version they're on now (`agent-reach version`)
|
||
2. How many channels are available, and which backend each multi-backend
|
||
platform is using (from doctor)
|
||
3. Anything that needs their action (e.g. Chrome extension click, `xhs login`,
|
||
QR scan for xiaohongshu-mcp on servers)
|
||
4. What changed in this update (release notes shown by `check-update`)
|
||
|
||
Done.
|