Feishu Bridge

Use this as the router for Feishu/Lark work. Prefer official lark-cli API access whenever a task can be expressed as Docs/Wiki/Drive/Base/Sheets/IM/Calendar/etc. Use browser automation only for web-only flows such as opening arbitrary shared links, pages that require the user's live browser login state, or filling interactive forms.

Local Runtime

Use the lark-cli binary the user installed. If $env:LARK_CLI is set, it holds the full path to the binary; otherwise expect lark-cli on PATH:

$LARK_CLI = if ($env:LARK_CLI) { $env:LARK_CLI } else { "lark-cli" }
& $LARK_CLI --version

I use lark-cli 1.0.32 from the larksuite/cli release v1.0.32; see references/local-runtime.md.

For browser automation I use the chrome-automation skill from anbeime/skill, which drives the user's logged-in Chrome over CDP. It is not part of this repo; if it is not installed, use whatever browser-automation skill or tool the agent has. If there is none, say that the web-only step is blocked instead of guessing.

Routing

1. Read lark-shared/SKILL.md before configuring, logging in, switching identities, or handling scope errors.
2. If the user gives a Feishu/Lark document or asks to read/summarize/update a doc, use lark-doc. For docs v2 commands, always pass --api-version v2.
3. If the user asks about a knowledge base / wiki node, use lark-wiki.
4. If the user asks to search, upload, download, find a file, manage comments, or discover cloud objects, use lark-drive first.
5. If a document contains an embedded spreadsheet or bitable, extract the token and switch to lark-sheets or lark-base rather than stopping at the embedded tag.
6. If the user asks to read/write a multi-dimensional table / 多维表格 / bitable, use lark-base.
7. If the user asks to send, reply, search, or inspect messages, use lark-im, and dry-run risky sends before execution.
8. If the user gives a web link that cannot be cleanly handled by token/API, or asks to fill fields/buttons on a Feishu page/form, use browser automation against the user's logged-in browser (chrome-automation if installed).

Authentication

Assume personal user OAuth by default. Use bot identity only when the user explicitly asks for bot/app behavior.

Typical setup:

& $LARK_CLI config init --new
& $LARK_CLI auth login --recommend
& $LARK_CLI auth status

When config init or auth login emits a verification URL, forward the raw URL exactly as returned. Do not re-encode or rewrite it. If OAuth is not completed in the current session, report API read/write tests as blocked by user authorization rather than claiming success.

Safety

• Do not expose app secrets, access tokens, or private document content in public wiki pages.
• For public wiki records, preserve only neutral metadata, capability notes, and smoke-test status unless the user explicitly permits more detail.
• Use --dry-run before high-risk writes when available.
• Confirm intent before deleting, bulk editing, sending messages, changing permissions, or modifying important business data.

Smoke Test Checklist

• & $LARK_CLI --version works.
• Domain help works, for example docs --api-version v2 --help, wiki --help, base --help, and drive --help.
• OAuth/config status is checked.
• Read/write tests are performed only against user-approved Feishu resources.
• Browser-fill tests use the browser-automation skill on a test page or explicitly approved Feishu form.
• Tell the user which capabilities were verified and which are blocked (for example by missing OAuth scopes).