chore: revert docs

2026-04-28 06:51:16 +08:00 · 2026-04-26 18:46:55 +07:00
parent 0f3a6f0fb3
commit 2511207cb0
3 changed files with 1 additions and 135 deletions
--- a/README.md
+++ b/README.md
@@ -169,99 +169,7 @@ scripts/run_tests.sh
 - 💬 [Discord](https://discord.gg/NousResearch)
 - 📚 [Skills Hub](https://agentskills.io)
 - 🐛 [Issues](https://github.com/NousResearch/hermes-agent/issues)
- - 🔌 [HermesClaw](https://github.com/AaronWong1999/hermesclaw) — Community WeChat bridge: Run Hermes Agent and OpenClaw on the same WeChat account.
-
---
-
-## Clipboard Troubleshooting
-
-Hermes TUI (standalone) and dashboard both support copying via `Ctrl+C` / `Cmd+C`. This requires either:
-
- A terminal with **OSC 52** support enabled, **or**
- Native clipboard utilities (`pbcopy`, `wl-copy`, `xclip`, `xsel`, `clip.exe`) available in PATH **and** a running display server (X11 or Wayland).
-
-If the UI says "copied" but the text is not in your system clipboard, follow these steps.
-
-### Standalone TUI (`hermes --tui`)
-
-#### Verify OSC 52 support
-
-Run this in the same terminal you use for Hermes:
-```bash
-printf '\e]52;c;%s\a' "$(echo -n 'test-osc52' | base64)" && echo
-```
-Then paste (Cmd+V / Ctrl+Shift+V). If you see `test-osc52`, OSC 52 works.
-
-If it fails, enable OSC 52 in your terminal:
-
-| Terminal     | Setting                                                                 |
-|--------------|-------------------------------------------------------------------------|
-| iTerm2       | Preferences → General → Selection → check "Copy to pasteboard"        |
-| Kitty        | `allow_remote_control yes` (default: on)                               |
-| WezTerm      | `enable_osc52_copy = true`                                              |
-| VS Code      | Usually works; if blocked, check DevTools console for permission error |
-| GNOME        | Enabled by default                                                      |
-
-#### tmux users
-
-tmux absorbs OSC 52 unless explicitly configured. Add to `~/.tmux.conf`:
-```tmux
-set -g set-clipboard on
-set -g allow-passthrough on
-```
-Then reload: `tmux source-file ~/.tmux.conf`.
-
-#### Docker/headless environments
-
-Inside a Docker container, `$DISPLAY` and `$WAYLAND_DISPLAY` are typically unset, so native clipboard tools fail immediately. OSC 52 is the only path — it must be supported by your local terminal emulator (the one connected to the container's PTY). If your terminal doesn't support OSC 52, consider:
-
- Using `ssh -X` / `ssh -Y` to forward X11 and run `xclip` on the host via SSH
- Running Hermes on the host directly, not inside a container
- Writing copied text to a file: `/copy` saves to `~/.hermes/clipboard.txt` (fallback)
-
-#### Force OSC 52 emission
-
-If your terminal supports OSC 52 but Hermes isn't emitting it (e.g., inside SSH where native tools are skipped), set:
-```bash
-export HERMES_TUI_CLIPBOARD_OSC52=1
-hermes --tui
-```
-
-#### Debug mode
-
-To see exactly which clipboard path Hermes takes:
-```bash
-export HERMES_TUI_DEBUG_CLIPBOARD=1
-hermes --tui
-```
-Then attempt a copy and watch stderr for messages like:
-```
-[clipboard] [native] Linux: no DISPLAY or WAYLAND_DISPLAY — native clipboard unavailable
-[clipboard] [native] Linux: clipboard probe complete → xclip
-[clipboard] [osc52] no sequence emitted — native clipboard or tmux buffer path in use
-```
-
-### Dashboard (`hermes dashboard` → /chat)
-
-The dashboard uses the browser's Clipboard API. There are two copy paths:
-
-1. **Ctrl/Cmd+Shift+C** — direct copy from xterm's selection (most reliable)
-2. **Ink's Ctrl+C** — emits OSC 52 → xterm OSC 52 handler → Clipboard API; this is more fragile because the Clipboard API requires a **user gesture**. In some browsers the OSC 52 response is processed outside the original key event's activation window, causing a silent failure.
-
-If copy doesn't work in the dashboard:
- Use `Ctrl+Shift+C` (Linux/Windows) or `Cmd+Shift+C` (macOS) instead
- Check the browser console (F12) for warnings like `[dashboard clipboard] OSC 52 write failed`
- Ensure the page has clipboard permissions (browser may ask on first use)
-
-Clicking the "copy last response" button also sends `/copy` over the WebSocket, which suffers from the same OSC 52 timing issue.
-
-### When all else fails: file-based fallback
-
-You can save copied text to a file manually:
-```bash
-hermes --tui  # inside TUI, use /copy which includes a file fallback in future versions
-```
-Or implement a custom skill that writes the last assistant message to disk.
+- 🔌 [HermesClaw](https://github.com/AaronWong1999/hermesclaw) — Community WeChat bridge: Run Hermes Agent and OpenClaw on the same WeChat account.

 ---