Zhihu publish (Chrome attach / Linux VNC)

This skill is self-contained: everything runs from {baseDir}/scripts/. No other repository files are required.

Publish column articles (专栏) by attaching to Chrome on 127.0.0.1:9222 after the user logged in via VNC.

Uses exec + bash {baseDir}/scripts/zhihu_publish.sh — not Browser Relay (see ClawHub zhihu-post for Windows).

First-time setup (after ClawHub install)

Run once on the Linux server:

bash {baseDir}/scripts/setup.sh
bash {baseDir}/scripts/install_chromedriver.sh
bash {baseDir}/scripts/start_chrome_debug.sh

In VNC: log in to Zhihu in that Chrome window.

Verify:

bash {baseDir}/scripts/zhihu_publish.sh --check --json

Expect: "ok": true, "logged_in": true.

Details: {baseDir}/references/linux-vnc-setup.md

When to use

• Linux server + VNC, Chrome started with debug port 9222
• Zhihu already logged in (or user can log in after start_chrome_debug.sh)
• User wants to publish with title + body

Scripts in {baseDir}/scripts/

Title and body (parameters)

Auto-start: Every zhihu_publish.sh run automatically calls ensure_chrome_debug.sh first. If the user closed the browser, Chrome restarts in the background with the same profile (~/.chrome-zhihu-automation) — login usually persists. No need to pass a separate flag unless debugging.

Never put user content inside one shell string. Use separate exec args or --body-file.

Agent workflow

0. Check login (Chrome auto-starts if closed)

bash {baseDir}/scripts/zhihu_publish.sh --check --json

1. Dry-run (fill draft, do not publish)

Write body to e.g. /tmp/zhihu_body.txt, then:

bash {baseDir}/scripts/zhihu_publish.sh \
  --publish \
  --title "USER_TITLE" \
  --body-file /tmp/zhihu_body.txt \
  --json

Confirm with user (VNC or chat). JSON has dry_run: true without --submit.

2. Real publish (only after user confirms)

bash {baseDir}/scripts/zhihu_publish.sh \
  --publish \
  --title "USER_TITLE" \
  --body-file /tmp/zhihu_body.txt \
  --submit \
  --json

Success: "ok": true, "submitted": true.

Exec examples

command: bash
args: ["{baseDir}/scripts/zhihu_publish.sh", "--check", "--json"]

command: bash
args: [
  "{baseDir}/scripts/zhihu_publish.sh",
  "--publish",
  "--title", "\x3Ctitle>",
  "--body-file", "/tmp/zhihu_post_body.txt",
  "--submit",
  "--json"
]

Chromedriver (version must match Chrome)

Selenium attach requires chromedriver even when Chrome is already running.
Install to /usr/local/bin/chromedriver (or set CHROMEDRIVER_PATH).

bash {baseDir}/scripts/install_chromedriver.sh
bash {baseDir}/scripts/verify_chrome_stack.sh

If you installed Chrome via dnf RPM (e.g. 148.0.7778.215), chromedriver must be the same build from Chrome for Testing — see {baseDir}/references/linux-vnc-setup.md.

Troubleshooting

Safety

• Without --submit = draft only.
• Use --submit only when the user explicitly asks to publish.
• Wait ≥ 3 minutes between posts if publishing repeatedly.