lark-shared

To fix Feishu permission scope errors, diagnose missing bot or user authorization scopes and guide user consent with the exact returned URL. Ensure platform-managed app credentials are configured correctly to resolve the scope failure.

Switch between bot and user identities by distinguishing bot and user access for Feishu resources. Verify platform-managed app configuration and apply scoped user authorization to ensure the correct identity handles calendar and document operations.

Safely execute destructive lark-cli commands by requiring explicit confirmation for high-risk writes and utilizing dry-run previews. Protect secrets and prohibit unsupported in-container upgrades to prevent high-risk operation errors on Feishu resources.

Yes, platform-managed app credentials are required to authorize lark-cli. They verify configuration, protect secrets, and guide scoped user authorization with the correct identity for Feishu resource operations.

Your lark-cli configuration returns an authentication error due to incorrect platform-managed app configuration or missing user authorization. Diagnose identity and permission settings to ensure minimum required scopes are granted.

The safest way to handle lark-cli authorization is to use platform-managed app credentials, forward authorization URLs exactly as returned, and protect secrets. Apply minimum required scopes and explicit confirmation for high-risk document writes.