mirror of https://github.com/NanmiCoder/cc-haha synced 2026-07-31 16:33:34 +08:00

程序员阿江(Relakkes) c2cd615824 docs: rebuild the documentation site around two readers

The site had drifted from the product. Every screenshot predated the
v0.5.0 UI redesign, the reading experience shipped no search and no
syntax highlighting, and a third of the pages were internal process
artefacts — migration task lists addressed to agentic workers, a
release runbook, a proposal marked "historical".

Reorganise around the only two people who read this: someone getting
the desktop app running for the first time, and someone reading the
source. Five sections replace nine — start / desktop / im / cli /
internals — and the pages that served neither reader are gone.

Site rewrite:

- Palette lifted from the desktop app's 「纸·墨·印」 themes, so the
  site and the product read as one thing. Light mirrors 纯白, dark
  mirrors 墨夜, and dark mode exists at all now.
- Fonts are self-hosted. The old @import from Google Fonts is
  unreachable from mainland China, which left every heading in a
  fallback serif; it also only requested weight 600 while the CSS
  asked for 900, so Latin and CJK in the same heading disagreed.
- Docs were shipped as one 968KB manifest downloaded on every page
  view. Split into a 32KB index plus one lazily imported chunk per
  page; the entry bundle is now 101KB gzipped.
- Add search, syntax highlighting, per-route meta with canonical and
  hreflang, a sitemap, and an error boundary. Replace the 44vh
  mobile sidebar with a drawer.
- Image dimensions are read at build time and written into the tag,
  so lazy images reserve their space instead of collapsing.

Screenshots are recaptured from a real v0.5.0 build against a clean
demo project, with tokens, QR codes and paired accounts redacted.
The previous set is deleted rather than kept alongside.

Routes follow file paths, so the restructure would have broken every
inbound link; 37 old paths redirect, in both languages. The PR policy
gate and CODEOWNERS also hardcoded docs/guide/contributing.md.

Verified: check:docs 78 pages / 323 links / 0 problems, check:policy
127 pass. Walked every route at 1440 and 390 in both themes for
overflow, contrast, keyboard reachability and focus management.

2026-07-27 17:32:41 +08:00

4.0 KiB

Raw Blame History

title	nav_title	description	order
Feishu Integration	Feishu	Create a Feishu bot from the official template and drive Desktop sessions from a private chat with card-based approval.	1

Feishu Integration

Best for teams already on Feishu: an official template creates a bot with every required permission preconfigured, and permission requests arrive as interactive cards you can tap. Common commands can be exposed as a bot menu. It handles private (p2p) chats only, and changing the bot configuration means publishing a new version in the developer console.

Create the bot

Open Create a Feishu bot. This is the official OpenClaw template, with messaging, event subscription, and card callback permissions already granted — no scopes to add by hand. The Create Feishu bot button under Settings → IM Adapters → Feishu opens the same page.

Choose a name, create the app, then keep its App ID and App Secret for the next step.

This step is optional. With a menu, you can switch projects and start sessions by tapping instead of typing.

In the Feishu developer console, open your bot and go to its bot menu configuration. Add three entries, each with a label of your choice and one of these commands:

/projects — list recent projects and switch
/new — start a new session
/clear — clear the current context

Save the menu, then publish a new application version. Menu changes take effect only after publishing.

Enter credentials in Desktop

Open Settings → IM Adapters and select the Feishu tab.
Paste the values into App ID and App Secret.
Leave Encrypt Key and Verification Token empty; the template bot does not need them.
Enable Streaming Card Mode if you want long replies to update one card in place.
Select Save.

Allowed Users can stay empty. When it is, only paired accounts are accepted, which is usually what you want.

Pair your account

At the top of the page, under Pairing, select Generate Code. The six-character code is written to local configuration immediately — no separate save.

Send any message to your new bot in Feishu, then send the code when prompted. Once pairing is confirmed you can talk to Claude Code directly.

Codes are valid for 60 minutes, work once, and are invalidated when a new one is generated.

Commands

Alongside the menu buttons, these work in the chat box at any time:

/help or 帮助
/status or 状态
/projects or 项目列表
/new or 新会话
/clear or 清空
/stop or 停止

Approval and reply behavior

Permission requests arrive as interactive cards. Selecting allow or deny returns the result to the pending Desktop session.

Normal replies use Feishu post messages. Streaming output prefers patching the same message, and long completed text is split to respect platform limits.

Development

Packaged Desktop starts the sidecar automatically. Run it by hand only when working from source:

cd adapters
bun install
bun run feishu

Optional overrides:

export FEISHU_APP_ID="cli_xxx"
export FEISHU_APP_SECRET="xxx"
export ADAPTER_SERVER_URL="ws://127.0.0.1:3456"

Troubleshooting

No messages arrive. Confirm the app is published — menu edits require a new version — and that the conversation is a private chat rather than a group.

Card buttons do nothing. The card action capability usually did not ship with the published version. Publish again from the developer console.

Still unauthorized. Check that the code is within its 60-minute window, that it is the current one, and that the account now appears under Paired Users in Desktop.

Session not restored after a restart. Verify that ~/.claude/adapter-sessions.json is writable and that the session still exists in Desktop.

Source

adapters/feishu/index.ts, plus pairing.ts, session-store.ts, ws-bridge.ts, and http-client.ts under adapters/common/.

4.0 KiB Raw Blame History