lark-im

Use the +messages-send shortcut with the target chat_id, for example lark-cli im +messages-send --chat-id oc_xxx --text "hello". If you only know the group name, resolve it first with lark-cli im +chat-search --query "name".

Use lark-cli im +messages-search with keyword, sender, chat, and time-range filters; it supports auto-pagination via --page-all. Note this shortcut works only with user identity (--as user), not bot identity.

User identity (user_access_token) acts as the authorized end user and is required for p2p listing, feed shortcuts, and feed groups. Bot identity (tenant_access_token) is required for image upload, message recall in some cases, and urgent messages; it fails when the bot lacks visibility to target users.

Yes. Use +messages-resources-download, which automatically switches to chunked downloading in 8MB parts for large files and detects the file extension from Content-Type. Alternatively pass --download-resources to message listing commands to fetch all eligible resources at once.

This happens under bot identity when the app's visibility range does not cover the message sender, so the contact API returns no name. Fix it by widening the app's visibility in the Developer Console or by fetching messages with --as user.

Listen with lark-cli event consume card.action.trigger --as bot, then update the card via the delayed-update API using the event token. The token is valid for 30 minutes and at most 2 uses, and the update requires the complete new card JSON.