tmeet

Installation and Initialization

tmeet

• If the

  tmeet

  command is detected, you can use it directly
• If the

  tmeet

  command is not detected, the following installation command will be executed automatically:
  bash

  npm install -g @tencentcloud/tmeet

  Install the latest version of Tencent Meeting CLI toolkit

Note: Automatic installation requires network connection and npm environment support. If the installation fails, please manually execute the above command or check your network environment.

Core Concepts

• Meeting: Tencent Meeting instance, identified by

  meeting_id

  or

  meeting_code

  .

  meeting_id

  is only used for command line parameter passing. When displaying meeting information to users, you must use

  meeting_code

  (meeting number), and must not expose

  meeting_id

  to users.
• Recurring Meeting: A repeated meeting with

  meeting_type=1

  , which contains multiple sub-meetings (

  sub_meeting_id

  ).
• Record: Recording file generated after the meeting ends, identified by

  meeting_record_id

  and

  record_file_id

  .
• Smart Minutes: AI-generated minutes based on the recording file.
• Transcript: Verbatim transcription content of the recording file, supports paragraph query and keyword search.
• Report: Statistical data after the meeting ends, including participant list and waiting room members.

Authentication

# Login (output authorization URL, open in browser to complete authorization)
tmeet auth login

# Logout (clear local credentials)
tmeet auth logout

# View current login status and Token validity (can be executed without login)
tmeet auth status

Note: Except for

auth login

and

auth status

, all commands require login first. If you are not logged in, the command will prompt

user config is empty

.

Note: When calling the

auth login

command for the first time or switching models, you must write the currently used agent type (e.g. Cursor/Claude Desktop/Cline/CodeBuddy) and model name (e.g. Claude 3.5 Sonnet/GPT-4o/DeepSeek) into the

TMEET_AGENT

and

TMEER_MODEL

environment variables respectively, no need to ask the user.

Time Format

2026-03-12T14:00:00+08:00

2026-03-12T14:00+08:00

Note: Date-only format (e.g.

2026-03-12

) is not supported, must include time and time zone information.

Time logic check: If the end time provided by the user ≤ start time (e.g. "4 o'clock to 3 o'clock"), do not infer the user's intention by yourself, you must first confirm with the user whether it is cross-day or a typo before executing the command.

Command Overview

tmeet
├── auth
│   ├── login          # OAuth authorized login
│   ├── logout         # Log out and clear credentials
│   └── status         # View current login status and Token validity
├── meeting
│   ├── create         # Create meeting (supports normal/recurring)
│   ├── update         # Update meeting information
│   ├── cancel         # Cancel meeting
│   ├── get            # Get meeting details
│   ├── list           # Get meeting list (in progress/upcoming)
│   ├── list-ended     # Get list of ended meetings
│   └── invitees-list  # Get list of meeting invitees
├── record
│   ├── list                  # Query recording list
│   ├── address               # Get recording file download address
│   ├── smart-minutes         # Get smart minutes
│   ├── transcript-get        # Get transcription details (paged)
│   ├── transcript-paragraphs # Get transcription paragraph list
│   └── transcript-search     # Search transcription content
└── report
    ├── participants      # Get participant list
    └── waiting-room-log  # Get waiting room member list

Subcommand Details

• Authentication:

  references/tmeet-auth.md

• Meeting Management:

  references/tmeet-meeting.md

• Recording Management:

  references/tmeet-record.md

• Meeting Report:

  references/tmeet-report.md

Security Rules

• It is forbidden to output AccessToken / RefreshToken to the terminal in plain text.
• Write operations must be confirmed twice, and direct execution is strictly prohibited: The following commands will have irreversible or high-risk impacts on data. Before calling the command, you must first show the user the details of the operation to be performed, and execute it only after obtaining explicit confirmation from the user, you cannot skip the confirmation step:

  Command	Risk Description
  meeting cancel	Cancel meeting, unrecoverable
  meeting update	Modify meeting information (time, topic, etc.), affecting all participants
  auth logout	Clear local login credentials

  Confirmation process:
  1. Show the user the operation to be performed and key information (use

     meeting_code

     to identify the meeting, do not display

     meeting_id

     );
  2. Wait for the user to explicitly reply with affirmative instructions such as "confirm", "yes", etc.;
  3. Execute the command after receiving confirmation;
  4. If the user does not explicitly confirm or indicates cancellation, terminate the operation.
• When required parameters are missing, you must confirm with the user for supplementation, and filling by yourself is prohibited: If the required parameters for executing the command are not provided by the user, do not infer or fill in default values by yourself, you must clearly inform the user which parameters are missing and request supplementation, and execute the command after the user provides them.

Response Processing Rules

• Only display key information: On the premise that the user does not explicitly request, only display the core fields directly related to the user's question, and do not output redundant fields.
• Unauthorized aggregation or sorting is prohibited: Without user request, do not perform any aggregation statistics or sorting operations on the returned results, and present them as per the original results.

Common Errors

user config is empty

tmeet auth login

--start format error

2026-03-12T14:00:00+08:00

--meeting-id is required

user has been initialized