lark-vc

Use lark-cli vc +search with at least one filter such as keyword, time range, organizer IDs, participant IDs, or room IDs. It only searches ended meetings; for future scheduled meetings, use the calendar skill instead.

First run vc +detail with the meeting ID to get the note_id, then call note +detail to check note_display_type. Normal notes expose a verbatim_doc_token readable via docs +fetch; unified notes require note +transcript.

No, vc +search only covers ended historical meetings, including instant meetings not tied to calendar events. For future schedules or upcoming meetings, use the lark-calendar skill instead.

Meeting notes come from the AI summary feature and include a summary document and verbatim transcript identified by note_id. Minutes come from recordings or uploaded media, identified by minute_token, and contain summary, todos, chapters, and transcript. The two pipelines are independent.

Common causes include missing filter conditions, searching future meetings, exceeding the one-month time range limit, or lacking the vc:meeting.search:read permission. Verify authentication with lark-cli auth login and split long ranges into monthly queries.

Run lark-cli vc meeting get with the meeting_id and with_participants set to true. This server-side snapshot works for ended meetings and does not require a bot to have joined the meeting.