mirror of https://github.com/larksuite/cli.git synced 2026-09-14 18:42:53 +08:00

Files

T

xiahjay cd1c2a3c8f docs: make enterprise/embedded integration discoverable from the repo (#2066 )

The embedding guide (extension mechanism: Credential / Transport /
Restrict / Observer / Wrap / On) lives on the Open Platform doc site,
but the repo itself never mentions it — enterprise IT scanning GitHub
cannot discover the centralized-integration path at all.

- README(.zh): add a 'Personal or Enterprise?' routing table right
  after 'Why lark-cli?', linking the official embedding guide and
  extension/; add 'Enterprise' to the nav bar; document the '.md'
  raw-Markdown trick for AI Agents
- extension/README.md: thin index mapping packages to extension
  points, pointing to platform/README.md and the official guide

2026-08-12 11:13:39 +08:00

1.1 KiB

Raw Blame History

Extension

Embed lark-cli into your own Agent or application — swap credential sources, audit every command, restrict the command surface — without modifying CLI source. Write a Go package against these interfaces, import it from a wrapper main, and build your own enhanced binary.

Main extension points:

Package	Extension point	What it does
`credential/`	Credential	Bring your own credential source: database, Vault, config center…
`transport/`	Transport	Intercept every HTTP request: inject headers, rewrite targets, logging & monitoring
`platform/`	Restrict · Observer · Wrap · On	Command allow/deny rules, audit hooks, onion-style middleware (approval gates, rate limiting), process lifecycle — see the Plugin SDK README

📖 Full guide: Embed lark-cli in your Agent (中文)

1.1 KiB Raw Blame History

Extension

1.1 KiB

Raw Blame History