lark-apps

Create an app with lark-cli apps +create --name "<name>" --app-type HTML, then run lark-cli apps +html-publish --app-id <id> --path <file-or-directory>. The response returns a public URL for the deployed app.

Pass the directory path to apps +html-publish, which recursively packages it as tar.gz and deploys it. The directory must contain index.html at its root, and you should use a clean build output like ./dist to avoid packing .git or node_modules.

The Validate stage scans the publish path for credential files such as .env, .npmrc, .netrc, .git-credentials, and cloud SDK configs, and exits non-zero on any hit. Remove those files from the payload, or pass --allow-sensitive only when shipping them is intentional.

Use apps +access-scope-set with one of three mutually exclusive scopes: specific (requires --targets JSON of users, departments, or chats), public (requires --require-login), or tenant (no extra flags). Check current settings with apps +access-scope-get.

The entry file must be named index.html. For directories, index.html must sit at the root; for single-file publishes, the file itself must be named index.html. Names like app.html or demo.html are rejected by +html-publish.

Yes, but you must supply the app_id yourself, either directly as an app_xxx string or extracted from a Miaoda app URL like https://miaoda.feishu.cn/app/app_xxx. The agent does not search or enumerate existing apps; the default behavior is creating a new one.