lark-shared

To configure Lark CLI authentication, run the `lark-cli config init` command to initialize your project and follow the on-screen prompts to complete the authentication flow for accessing Feishu or Lark resources.

Switching between user and bot identities in Lark CLI is supported through the identity management feature, allowing you to manage different contexts and handle permissions or scopes for your specific application requirements.

Troubleshooting Lark CLI permission errors involves interpreting the permission-related responses provided by the system, specifically utilizing the generated `console_url` and `hint` messages to identify and resolve access issues.

Yes, managing scopes is required when using Lark CLI for user and bot contexts, as the identity management feature explicitly handles scope configuration to ensure correct access levels across different identity types.

Lark CLI configuration requires a safety prompt during login to securely manage the authentication workflows, protecting sensitive credentials and ensuring safe access to your Feishu or Lark resources.

No, initializing a Lark CLI project requires setting up the authentication flow, as configuration onboarding explicitly integrates the login process to properly establish access to Lark resources from the start.