mirror of https://github.com/larksuite/cli.git synced 2026-09-14 18:42:53 +08:00

Files

T

zhicong666-bytedance 35bd5ecfcd feat(vc): add agent meeting control shortcuts (#2466 )

* feat(vc): add agent calendar meeting actions

* feat(vc): add meeting screenshot shortcut for visual context

* feat(vc): add meeting countdown commands and events

* fix(skills): avoid screenshot recall from meeting description

* fix(vc): omit screenshot log ID on success

---------

Co-authored-by: renaocheng <renaocheng@bytedance.com>
Co-authored-by: shike.11 <shike.11@bytedance.com>

2026-08-24 21:26:44 +08:00

1.6 KiB

Raw Permalink Blame History

VC E2E Coverage

Agent Calendar Lifecycle

Status	Cmd	Coverage	Notes
Dry-run	`vc +meeting-join --action start`	`vc_agent_meeting_actions_dryrun_test.go::TestVCAgentMeetingActionsDryRun/start and join`	Verifies the bot join endpoint and `action=2`.
Dry-run	`vc +meeting-invite`	`vc_agent_meeting_actions_dryrun_test.go::TestVCAgentMeetingActionsDryRun/invite all suggested`	Verifies the Agent invite endpoint and long `meeting_id`.
Dry-run	`vc +meeting-end`	`vc_agent_meeting_actions_dryrun_test.go::TestVCAgentMeetingActionsDryRun/end meeting`	Verifies the bot end endpoint and that `--dry-run` bypasses the real-execution confirmation gate.

Live E2E Blocker

vc +meeting-end terminates a meeting for every participant. The shared E2E tenant does not provide an isolated Calendar fixture that can reliably create an Agent-enabled meeting where the test app bot becomes Host and has a distinct eligible invitee. Running against an existing meeting would be unsafe and is not self-cleaning.

Required Fixture

A dedicated test app with the Agent Calendar feature enabled for its meeting owner.
A disposable app-calendar event that creates a VC meeting and makes that app bot Host.
A second user open_id scoped to the same test app for a SELECTED invite assertion.

Substitute Evidence

On 2026-08-24, the gray-lane manual lifecycle created a bot-owned Calendar event, started it, sent an ALL_SUGGESTED invite, ended it as the Host bot, deleted the event, and verified that the active-meeting list was empty. The fixture above is required before promoting this sequence to CI live E2E.

1.6 KiB Raw Permalink Blame History