@tencent-rtc/mcp 1.6.7 → 1.7.0

package/resource/knowledge/roomkit/best-practice/common/room-status-after-all-leave.md

@@ -0,0 +1,69 @@
+---
+title: "TUIRoomKit Room Status and Billing After All Members Leave（TUIRoomKit / 所有人离开 / 房间销毁 / 回收房间 / 解散房间）"
+product: room
+frameworks: [react, vue, web, android, ios, flutter]
+scope: platform_common
+tags: [TUIRoomKit, all members leave, room destruction, room reclaim, dismiss room, billing, meeting end, room existence, room count]
+version_range: ">=2.0.0"
+---
+
+# TUIRoomKit Room Status and Billing After All Members Leave
+
+## 1. Key Takeaways
+
+- A room is **not** automatically destroyed immediately when "all members leave."
+- After a meeting ends, the business side should **proactively call the dismiss room API** to end the meeting.
+- If not manually dismissed: the backend attempts to reclaim the room **6 hours after** the meeting end time, provided the **member count is 0**.
+- Billing is based on actual push/pull stream and call consumption. After all members leave and there is no media usage, audio/video duration charges generally stop; however, the room object still occupies room count quota until dismissed or reclaimed.
+
+## 2. Field / API Reference
+
+| Field / Capability | Purpose | Notes |
+|---|---|---|
+| Dismiss room API | Proactively end a meeting | Business side calls after meeting ends |
+| Backend reclaim | Automatic room cleanup | Attempted 6 hours after meeting end; condition: member count is 0 |
+| Room member count | Room member statistics | Reclaim condition: member count is 0 |
+| Audio/video duration billing | Call consumption billing | Billed by actual push/pull stream and call consumption |
+| Room count occupation | Room object occupation | Still occupies room count quota until dismissed or reclaimed |
+
+## 3. Mechanism & Sequence
+
+All members leave room -> Room is not destroyed immediately -> Business side proactively calls dismiss room API (recommended), or waits for backend automatic reclaim -> Backend attempts reclaim 6 hours after meeting end (condition: member count is 0) -> Room is reclaimed.
+
+Billing dimensions:
+
+- Audio/video duration is billed by actual push/pull stream and call consumption.
+- After all members leave and there is no media usage, audio/video duration charges for that room generally stop.
+- The room object still occupies room count quota until dismissed or reclaimed.
+
+## 4. Standard Usage
+
+1. After the meeting ends, the business side proactively calls the dismiss room API to end the meeting, avoiding lingering rooms.
+2. If manual dismissal is forgotten, the backend automatically reclaims the room after 6 hours (when member count is 0).
+3. When evaluating room count occupation, note that undismissed and unreclaimed room objects still consume quota.
+
+## 5. Expected Results
+
+- After proactive dismissal, the room ends immediately.
+- Without proactive dismissal, the backend reclaims the room 6 hours after meeting end when member count is 0.
+- After all members leave and there is no media usage, audio/video duration charges stop.
+- Undismissed and unreclaimed room objects still occupy room count quota.
+
+## 6. Common Pitfalls
+
+- Pitfall 1: Assuming rooms are automatically destroyed after all members leave (requires proactive dismissal or waiting 6 hours for backend reclaim).
+- Pitfall 2: Assuming undismissed rooms incur no cost (room objects still occupy room count quota, potentially affecting concurrent capacity).
+- Pitfall 3: Neglecting proactive dismissal by the business side (recommended to call the dismiss API rather than relying on backend reclaim).
+
+## 7. Problem Definition (retrieval hint)
+
+Whether a TUIRoomKit room still exists after all members leave, whether billing continues, and how to proactively dismiss a room.
+
+## 8. Alternative Queries (retrieval recall)
+
+- Does the room auto-destroy after everyone leaves?
+- Does an empty TUIRoomKit room still incur charges?
+- How to dismiss a room after a meeting ends?
+- How long does room reclaim take?
+- What happens when room member count is 0?
+- Does the room object still occupy room count quota?

package/resource/knowledge/roomkit/best-practice/vue/room-uikit-vs-atomicx.md

@@ -0,0 +1,111 @@
+---
+title: "Comparison of tuikit-atomicx-vue3/room vs roomkit-web-vue3（roomkit-web-vue3 vs tuikit-atomicx-vue3/room 的区别）"
+product: room
+frameworks: [vue, web]
+scope: platform_specific
+tags: [TUIRoomKit, Atomicx, UIKit, tuikit-atomicx-vue3, roomkit-web-vue3, useRoomState, conference, layer comparison, no-UI, pre-built UI, custom integration, dependency, vue3]
+version_range: ">=2.0.0"
+---
+
+# Comparison of tuikit-atomicx-vue3/room vs roomkit-web-vue3
+
+## 1. Key Takeaways
+
+- `tuikit-atomicx-vue3/room` (Atomicx) is the **atomic capability layer**: the primary path for no-UI / highly customized integration, decomposing room, device, and member states into reactive State Hooks.
+- `@tencentcloud/roomkit-web-vue3` (RoomKit / UIKit) is the **pre-built UI low-code layer**: an out-of-the-box meeting suite with page-level components.
+- Dependency: **RoomKit (pre-built UI) is a productized wrapper built on top of Atomicx/Room capabilities**. From a business perspective, RoomKit reuses/interfaces with Atomicx capabilities rather than being two independent room protocols.
+- API entry points: Atomicx uses `useRoomState()`, UIKit uses `conference`.
+
+## 2. Field / API Reference
+
+| Field / Capability | Purpose | Notes |
+|---|---|---|
+| `useRoomState` | Atomicx room state entry | `createAndJoinRoom` / `joinRoom` / `leaveRoom` / `endRoom` / `currentRoom` |
+| `useDeviceState` | Atomicx device state | Device toggles, screen sharing, etc. |
+| `useRoomParticipantState` | Atomicx participant state | Member management, event subscriptions |
+| `useLoginState` | Atomicx login state | Login capability, reusable within UIKit sessions |
+| `conference` | UIKit meeting facade API | Recommended: `createAndJoinRoom` / `joinRoom` / `leaveRoom` / `endRoom` |
+| `ConferenceMainView` | UIKit pre-built view | Complete meeting UI: login, join room, meeting controls, layout, seat management |
+
+## 3. Mechanism & Sequence
+
+### Layer Comparison
+
+| Comparison | `tuikit-atomicx-vue3/room` (Atomicx) | `@tencentcloud/roomkit-web-vue3` (RoomKit / UIKit) |
+|---|---|---|
+| **Layer** | Atomicx (atomic capability layer): State Hooks + optional atomic UI components | UIKit / pre-built UI low-code layer: out-of-the-box meeting suite with page-level components |
+| **Package positioning** | No-UI / highly customized integration path; decomposes room, device, and member into reactive State | Pre-built UI rapid integration path; provides complete meeting UI and `conference` facade API |
+| **Core capabilities** | `useRoomState` / `useDeviceState` / `useRoomParticipantState` / `useLoginState`: create room, join meeting, device control, screen sharing, member management, event subscription; compose your own UI | `conference` + pre-built views (e.g. `ConferenceMainView`): login, join room, meeting controls, layout, seat management; supports selective component visibility / custom Widgets |
+| **Use cases** | Embedding audio/video into your own business UI (telemedicine, OA, education dashboards, etc.) with 100% control over interaction and branding | Fastest path to launch a standard meeting/webinar with minimal UI coding, accepting the official meeting interaction |
+| **Dependency** | Built on RoomEngine / TRTC / IM; an atomic integration approach | Pre-built UI reuses/interfaces with Atomicx capabilities (e.g. login uses `useLoginState`, in-meeting logic uses Room capabilities); RoomKit (pre-built UI) is a productized wrapper on top of Atomicx/Room |
+| **API entry** | `useRoomState()`: `createAndJoinRoom` / `joinRoom` / `leaveRoom` / `endRoom`, `currentRoom`, event subscriptions, etc. | `conference`: recommended `createAndJoinRoom` / `joinRoom` / `leaveRoom` / `endRoom` |
+| **UI form** | Optional pre-built atomic components + primarily self-composed custom modules | Primarily pre-built complete meeting UI, with limited customization via Widget / visibility configuration |
+
+## 4. Standard Usage
+
+### Atomicx Approach (no-UI, custom integration)
+
+```javascript
+import { useRoomState } from 'tuikit-atomicx-vue3/room';
+
+const { createAndJoinRoom } = useRoomState();
+
+createAndJoinRoom({
+  roomId: 'YOUR_ROOM_ID', // 必填：建议由业务后台生成的唯一标识
+  options: {
+    roomName: '项目进度周会',
+  },
+});
+// 通过 useDeviceState / useRoomParticipantState 等获取响应式状态自拼 UI
+```
+
+### UIKit Approach (pre-built UI, rapid integration)
+
+```javascript
+import { conference, ConferenceMainView, ConferenceMainViewH5, RoomEvent, genTestUserSig } from '@tencentcloud/roomkit-web-vue3';
+const SDKAppID = 0; // 替换为您在开通服务阶段获取的 SDKAppID
+const SDKSecretKey = ''; // 替换为您在开通服务阶段获取的 SDKSecretKey
+const handleEnterRoom = async () => {
+  if (!SDKAppID || !SDKSecretKey) {
+    return;
+  }
+  try {
+    const { userSig } = genTestUserSig({ userId: 'test01', sdkAppId: SDKAppID, secretKey: SDKSecretKey });
+    await conference.login({ sdkAppId: SDKAppID, userId: 'test01', userSig });
+    await conference.setSelfInfo({ userName: 'test', avatarUrl: '' });
+    await conference.createAndJoinRoom({ roomId: '123456', options: { roomName: `test01 的会议` } });
+    inRoom.value = true;
+  } catch (error) {
+    console.error('进入会议失败:', error);
+  }
+};
+// 使用预制 ConferenceMainView 渲染完整会议 UI
+```
+
+## 5. Expected Results
+
+- No-UI / highly customized needs: choose Atomicx, use `useRoomState()` + State Hooks to compose your own UI.
+- Fastest path to a standard meeting: choose UIKit, use `conference` + `ConferenceMainView`.
+- Dependency: UIKit reuses Atomicx capabilities; they are not two independent protocols.
+- API entry: Atomicx uses `useRoomState()`, UIKit uses `conference`.
+
+## 6. Common Pitfalls
+
+- Pitfall 1: Assuming Atomicx and UIKit are two independent room protocols (UIKit is built on top of Atomicx/Room capabilities).
+- Pitfall 2: Assuming Atomicx includes a complete meeting UI (Atomicx provides State Hooks + optional atomic components; UI must be self-composed).
+- Pitfall 3: Assuming UIKit cannot be customized (it supports selective component visibility / custom Widgets).
+- Pitfall 4: Confusing the API entry points of the two approaches (Atomicx uses `useRoomState()`, UIKit uses `conference`).
+
+## 7. Problem Definition (retrieval hint)
+
+Comparing the positioning differences between two TUIRoomKit Vue3 integration approaches: `tuikit-atomicx-vue3/room` (Atomicx Core SDK, no-UI, State Hooks self-composed) vs `@tencentcloud/roomkit-web-vue3` (RoomKit UIKit, pre-built UI, conference low-code) in terms of layer, capabilities, use cases, dependency, and API entry (useRoomState vs conference).
+
+## 8. Alternative Queries (retrieval recall)
+
+- What is the difference between Atomicx and RoomKit?
+- How to choose between `tuikit-atomicx-vue3/room` and `roomkit-web-vue3`?
+- How to choose between TUIRoomKit no-UI and pre-built UI approaches?
+- What is the difference between `useRoomState` and `conference`?
+- Is RoomKit based on Atomicx?
+- Which package for custom meeting room UI?
+- Use Atomicx or UIKit for rapid meeting integration?

package/resource/knowledge/roomkit/core-sdk/android/call-user-to-room.md

@@ -235,7 +235,3 @@ fun rejectCall(roomID: String, reason: CallRejectionReason = CallRejectionReason
 |Store/Component|Description|API Documentation|
 |---------|---------|---------|
 |**RoomStore**|Manages the full room lifecycle: create and join, join, leave, end room, update/retrieve room information, schedule rooms, invite external members, listen for passive room events (such as room dissolution, room info updates, etc).|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-store/index.html)|
-
-## Contact Us
-
-If you have any questions or suggestions during integration or usage, contact info_rtc@tencent.com.

package/resource/knowledge/roomkit/core-sdk/android/room-participant-state.md

@@ -582,7 +582,3 @@ private fun subscribeParticipantState() {
 |Store/Component|Description|API Documentation|
 |---------|---------|---------|
 |**RoomParticipantStore**|Manages room participants: assign admin, transfer ownership, retrieve participant list, remove participant, control participant devices (close, invite to enable camera/microphone, etc.), request device enablement.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-participant-store/index.html)|
-
-## Contact Us
-
-If you have any questions or suggestions during integration or use, please contact info_rtc@tencent.com.

package/resource/knowledge/roomkit/core-sdk/android/room-state.md

@@ -358,7 +358,3 @@ private fun subscribeCurrentRoomState() {
         **What does this mean for developers?**
 
         `participantCount` is a highly accurate, near real-time estimate. In rare cases with extremely high concurrency, brief delays or data loss may occur. We recommend using it for UI display only—not for billing, statistics, or scenarios requiring absolute precision.
-
-## Contact Us
-
-If you have questions or feedback during integration or usage, please email info_rtc@tencent.com.

package/resource/knowledge/roomkit/core-sdk/android/schedule-room.md

@@ -94,7 +94,7 @@ Follow the Integration Overview to integrate the AtomicXCore SDK. Make sure you
 | <code>scheduleStartTime</code> | <code>Long</code> | Yes | - Scheduled start time (Unix timestamp in seconds).<br>- Must be greater than the current time.<br>- We recommend aligning to a future minute. Example: 1736164800 (2025-01-06 20:00:00). |
 | <code>scheduleEndTime</code> | <code>Long</code> | Yes | Scheduled end time (Unix timestamp in seconds).<br>- Must be greater than <code>scheduleStartTime</code>.<br>- Set based on expected duration, e.g., <code>scheduleStartTime</code> + 3600 for one hour. |
 | <code>reminderSecondsBeforeStart</code> | <code>Int</code> | No | - Reminder time before the scheduled start (seconds). Used for system-triggered notifications.<br>- Recommended: 300 (5 min) or 900 (15 min) for local app notifications. |
-| <code>scheduleAttendees</code> | <code>List</code> | No | - List of participant user IDs. The system will send invitations to these users.<br>- For details, see retrieving the participant list for scheduled rooms. |
+| <code>scheduleAttendees</code> | <code>List</code> | No | - List of participant user IDs. The system will send invitations to these users.<br>- . |
 | <code>isAllMicrophoneDisabled</code> | <code>Boolean</code> | No | Whether to mute all participants by default.<br>- true: Disabled.<br>- false: Not disabled (default). |
 | <code>isAllCameraDisabled</code> | <code>Boolean</code> | No | Whether to disable all participant cameras by default.<br>- true: Disabled.<br>- false: Not disabled (default). |
 | <code>isAllScreenShareDisabled</code> | <code>Boolean</code> | No | Whether to disable screen sharing for all participants.<br>- true: Disabled.<br>- false: Not disabled (default). |
@@ -334,7 +334,3 @@ If you are not receiving the upcoming event notification after scheduling a room
   - **Edge Case:** If the room is scheduled to start very soon (e.g., in 5 minutes) but the reminder is set for 10 minutes before start, the system cannot send the notification, and the event will be missed.
 
   - **Solution:** Ensure the scheduled start time is sufficiently further in the future than the reminder interval you've set.
-
-## Contact Us
-
-For questions or feedback during integration or usage, contact info_rtc@tencent.com.

package/resource/knowledge/roomkit/core-sdk/ios/call-user-to-room.md

@@ -227,7 +227,3 @@ func rejectCall(roomID: String, reason: CallRejectionReason = .rejected) {
 |**Store/Component**|**Description**|**API Documentation**|
 |---------|---------|---------|
 |**RoomStore**|Room lifecycle management: create and join, join, leave, end room, update and retrieve room info, reserve room, call users outside the room, listen to passive room events (such as room dissolution, updates, etc.).|[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/roomstore)|
-
-## Contact Us
-
-If you have any questions or suggestions during integration or usage, contact info_rtc@tencent.com.

package/resource/knowledge/roomkit/core-sdk/ios/room-participant-state.md

@@ -563,7 +563,3 @@ private func subscribeParticipantState() {
 |**Store/Component**|**Description**|**API Documentation**|
 |---------|---------|---------|
 |**RoomParticipantStore**|Manage participants in the room: assign admin roles, transfer ownership, retrieve participant list, remove participants, control participant devices (e.g., close, invite to enable camera/microphone), request device enable (e.g., request to enable camera/microphone).|[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/roomparticipantstore)|
-
-## Contact Us
-
-If you have any questions or suggestions during integration or use, please contact info_rtc@tencent.com.

package/resource/knowledge/roomkit/core-sdk/ios/room-state.md

@@ -319,7 +319,3 @@ private func subscribeRoomState() {
       **What does this mean for developers?**
 
       `participantCount` provides a highly accurate, near real-time estimate. However, during periods of extremely high concurrency, updates may be briefly delayed or lost. We recommend using it for **UI display** purposes only, not for billing, analytics, or other scenarios requiring absolute precision.
-
-## Contact Us
-
-If you have questions or feedback during integration or usage, please email info_rtc@tencent.com.

package/resource/knowledge/roomkit/core-sdk/ios/schedule-room.md

@@ -89,7 +89,7 @@ func scheduleRoom() {
 | <code>scheduleStartTime</code> | <code>Int</code> | Yes | - Scheduled start time (Unix timestamp in seconds).<br>- Must be greater than the current time.<br>- We recommend aligning to a future minute. Example: 1736164800 (2025-01-06 20:00:00). |
 | <code>scheduleEndTime</code> | <code>Int</code> | Yes | - Scheduled end time (Unix timestamp in seconds).<br>- Must be greater than <code>scheduleStartTime</code>.<br>- Set based on expected duration, e.g., <code>scheduleStartTime</code> + 3600 for one hour. |
 | <code>reminderSecondsBeforeStart</code> | <code>Int</code> | No | - Reminder time before the scheduled start (seconds). Used for system-triggered notifications.<br>- Recommended: 300 (5 min) or 900 (15 min) for local app notifications. |
-| <code>scheduleAttendees</code> | <code>[String]</code> | No | - List of participant user IDs. The system will send invitations to these users.<br>- For details, see retrieving the participant list for scheduled rooms. |
+| <code>scheduleAttendees</code> | <code>[String]</code> | No | - List of participant user IDs. The system will send invitations to these users.<br>- . |
 | <code>isAllMicrophoneDisabled</code> | <code>Bool</code> | No | Whether to mute all participants by default.<br>- true: Disabled.<br>- false: Not disabled (default). |
 | <code>isAllCameraDisabled</code> | <code>Bool</code> | No | Whether to disable all participant cameras by default.<br>- true: Disabled.<br>- false: Not disabled (default). |
 | <code>isAllScreenShareDisabled</code> | <code>Bool</code> | No | Whether to disable screen sharing for all participants.<br>- true: Disabled.<br>- false: Not disabled (default). |
@@ -316,7 +316,3 @@ If you are not receiving a "room starting soon" notification after scheduling, c
   - If the room's start time is too close (e.g., 5 minutes away) and the reminder is set too far in advance (e.g., 10 minutes before), the event will not trigger.
 
   - Make sure the scheduled start time is at least as far in the future as the reminder value you set.
-
-## Contact Us
-
-For questions or feedback during integration or usage, contact info_rtc@tencent.com.

package/resource/knowledge/roomkit/core-sdk/vue/call-user-to-room.md

@@ -138,7 +138,7 @@ onUnmounted(() => {
 
 ## Practical Tutorial: Improving the Call Answer Rate
 
-To achieve a higher call answer rate in your business, beyond implementing the basic functionality, it is recommended to refer to the following strategies to optimize the user experience:
+To achieve a higher call answer rate in your business, beyond implementing the basic functionality, it is recommended to
 
 ### 1. Enhance Call Awareness (Avoid Users Missing Calls)
 

package/resource/knowledge/roomkit/core-sdk/vue/device-state.md

@@ -74,9 +74,6 @@ watch(currentCamera, (camera) => {
 });
 ```
 
-> **Note:**
->
-
 > When you call [setCurrentCamera](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#setCurrentCamera) to switch the device, if the camera is already on, Atomicx will automatically stop capturing from the current device and restart capturing with the new device, so the video stream switches seamlessly. If switching fails, the original device will continue to be used.
 >
 
@@ -331,9 +328,6 @@ watch(outputVolume, (volume) => {
 
 Using the [networkInfo](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#networkInfo) data from [useDeviceState](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#module-DeviceState), you can monitor the local user's network quality in real time.
 
-> **Note:**
->
-
 > Valid data can only be obtained from [networkInfo](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#networkInfo) when the local user has joined a room via [joinRoom](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#joinRoom) and turned on the microphone or camera.
 >
 

package/resource/knowledge/roomkit/core-sdk/vue/free-beauty-panel.md

@@ -37,9 +37,6 @@ It is generally recommended to place `FreeBeautyPanel` inside a Dialog or Modal,
 
 **The following example shows how to implement a complete interaction where clicking a button opens the beauty settings:**
 
-> **Note:**
->
-
 > All TUIKit components must be wrapped inside UIKitProvider; otherwise, they will not be able to obtain their context dependencies, resulting in abnormal styling.
 >
 
@@ -117,9 +114,6 @@ This section mainly describes how to implement basic beauty via the atomicx-core
 
 When the user adjusts the beauty parameters (for example, by dragging a slider), use [setFreeBeauty](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#setFreeBeauty) for real-time preview. At this point, the effect is only visible locally and will not be transmitted to remote users.
 
-> **Note:**
->
-
 > The value range of the parameters is 0-100.
 >
 
@@ -143,9 +137,6 @@ const updatePreview = async (beauty: number, white: number, ruddy: number) => {
 
 After the user confirms that they are satisfied with the preview, call [saveBeautySetting](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#saveBeautySetting) to apply the current configuration to the video stream. At this point, remote users can see the beauty effect.
 
-> **Note:**
->
-
 > The beauty feature depends on a camera device. You can use [useDeviceState](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#module-DeviceState) to check the device status.
 >
 > - [cameraList](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#cameraList): The list of currently available camera devices. If the list is empty, it means no camera was detected or camera permission is denied.

package/resource/knowledge/roomkit/core-sdk/vue/room-chat.md

@@ -35,7 +35,6 @@ This feature offers two integration approaches, and you can choose the one that
 After the user successfully joins the room, you need to call the [setActiveConversation](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#setActiveConversation) API to initialize the chat data. We recommend listening for changes to [currentRoom](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#currentRoom) to handle this automatically.
 
 > **Note:**
->
 > - `GROUP` is a fixed prefix. The `setActiveConversation` argument must be ``GROUP${roomId}``; otherwise, messages cannot be sent or received properly.
 > - `GROUP` is the fixed prefix for IM SDK group conversations (see [IM conversation types](https://web.sdk.qcloud.com/im/doc/zh-cn/Conversation.html)). Room chat is built on IM groups, so the conversation ID must be in the ``GROUP${roomId}`` format.
 
@@ -60,9 +59,6 @@ watch(() => currentRoom.value?.roomId, (roomId) => {
 
 In your page, you can directly combine these two components. At the same time, use [useRoomParticipantState](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#module-RoomParticipantState) to obtain the current user's mute status and control the availability of the input box.
 
-> **Caution:**
->
-
 > All TUIKit components must be wrapped inside UIKitProvider; otherwise, they cannot obtain their context dependencies, resulting in abnormal styles.
 >
 
@@ -144,9 +140,6 @@ const openChatWindow = () => {
 
 This section mainly explains how to implement a custom chat interface using the atomicx-core SDK APIs [useMessageListState](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#module-MessageListState) and [useMessageInputState](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#module-MessageInputState).
 
-> **Caution:**
->
-
 > `MessageInputState` supports integration with the `@tiptap/vue-3` editor by default. If you only need a simple text input (such as `<input>` or `<textarea>`), please **ignore** the editor-instance-bound APIs such as `setEditorInstance` and `setContent`, and simply use `updateRawValue` and `sendMessage`.
 >
 
@@ -155,7 +148,6 @@ This section mainly explains how to implement a custom chat interface using the
 After the user successfully joins the room, you need to call the [setActiveConversation](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#setActiveConversation) API to initialize the chat data. We recommend listening for changes to [currentRoom](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#currentRoom) to handle this automatically.
 
 > **Note:**
->
 > - `GROUP` is a fixed prefix. The `setActiveConversation` argument must be ``GROUP${roomId}``; otherwise, messages cannot be sent or received properly.
 > - When switching rooms or leaving a room, we recommend resetting or clearing the active conversation to avoid sending messages to the wrong conversation.
 
@@ -241,9 +233,6 @@ const handleSend = async () => {
 
 Use the [loadMoreOlderMessage](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#module-MessageListState) method to fetch historical messages page by page. This is usually triggered when scrolling to the top of the list.
 
-> **Caution:**
->
-
 > After loading historical messages, you usually need to manually adjust the scrollbar position to keep the current viewport from jumping.
 >
 

package/resource/knowledge/roomkit/core-sdk/vue/room-participant-state.md

@@ -81,7 +81,6 @@ const { participantList } = useRoomParticipantState();
 ```
 
 > **Note:**
->
 > - `RoomParticipantList` automatically fills the height and width of its parent container, so make sure its parent container has explicit dimensions.
 > - When using the `RoomParticipantList` component, make sure to configure the global `UIKitProvider` in `App.vue`. For details, refer to [Configuring App.vue](https://cloud.tencent.com/document/product/647/81962#ce98ee15-b0cb-43af-81da-70f51231430e).
 
@@ -111,9 +110,6 @@ const handleLoadMore = async () => {
 };
 ```
 
-> **Note:**
->
-
 > The data successfully fetched by the `getParticipantList` interface is automatically maintained in `participantList`. The UI only needs to render the data in `participantList`.
 >
 
@@ -355,7 +351,7 @@ await kickParticipant({ userId });
 
 ### Step 9: Invite others to join the room
 
-In actual business scenarios, you may need to send a call invitation to users who have not yet entered the room. Atomicx provides full support for a calling system. For details, refer to In-Meeting Calling.
+In actual business scenarios, you may need to send a call invitation to users who have not yet entered the room. Atomicx provides full support for a calling system. .
 
 ## API Documentation
 

package/resource/knowledge/roomkit/core-sdk/vue/room-state.md

@@ -32,9 +32,6 @@ const {
 
 Create a room (room owner): Use [createAndJoinRoom](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#createAndJoinRoom). After a successful call, the user automatically gains room owner permissions.
 
-> **Note:**
->
-
 > It is recommended that the roomId specified when creating a room be generated and delivered by the business backend, to ensure the uniqueness and stability of the room ID across the entire application globally.
 >
 
@@ -148,9 +145,6 @@ await updateRoomInfo({
 })
 ```
 
-> **Note:**
->
-
 > The room owner must be inside the room to call [updateRoomInfo](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#updateRoomInfo). If the room owner has already left the room, they need to rejoin before they can update the room information.
 >
 
@@ -175,7 +169,6 @@ await endRoom();
 ```
 
 > **Note:**
->
 > - If the room owner leaves the room but does not call [endRoom](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#endRoom), the room will continue to exist until the automatic reclamation condition is met (no users for 6 consecutive hours).
 > - The room owner can transfer the room owner identity to another user via the [transferOwner](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#transferOwner) interface.
 
@@ -261,7 +254,7 @@ Atomicx provides complete scheduled room capabilities, including:
 
 - **Join reminders:** Support automatic reminder logic before the start.
 
-   If you need to implement the more complex business logic for managing multi-person audio/video rooms described above, please refer to: Schedule Room.
+ If you need to implement the more complex business logic for managing multi-person audio/video rooms described above, please .
 
 ## FAQ
 

package/resource/knowledge/roomkit/core-sdk/vue/room-view.md

@@ -52,9 +52,6 @@ import { RoomView } from 'tuikit-atomicx-vue3/room';
 </style>
 ```
 
-> **Note:**
->
-
 > `RoomView` automatically fills the height and width of its parent container, so make sure its parent container has explicit dimensions.
 >
 

package/resource/knowledge/roomkit/core-sdk/vue/screen-share.md

@@ -60,9 +60,6 @@ const handleStartScreenShareWithAudio = async () => {
 |Firefox|Not supported|System audio sharing is not yet supported|
 |Safari|Not supported|System audio sharing is not yet supported|
 
-> **Note:**
->
-
 > System audio sharing requires browser support, and the user must check the **Share audio** option in the screen picker. If the browser does not support system audio sharing, the `screenAudio` parameter is ignored, but the screen sharing feature is not affected and works normally.
 >
 

package/resource/knowledge/roomkit/core-sdk/vue/virtual-background.md

@@ -50,7 +50,6 @@ It is generally recommended to place the [VirtualBackgroundPanel](https://github
 **The following example shows how to implement a complete interaction where clicking a button opens the virtual background settings:**
 
 > **Note:**
->
 > - Publish the `node_modules/trtc-sdk-v5/assets` directory to a CDN or static resource server. For details, see the [SDK documentation](https://web.sdk.qcloud.com/trtc/webrtc/doc/zh-cn/tutorial-36-advanced-virtual-background.html).
 > - When using the [VirtualBackgroundPanel](https://github.com/Tencent-RTC/TUIKit_Vue3/tree/main/packages/tuikit-atomicx-vue3/src/components/VirtualBackgroundPanel) component, pass the `assetsPath` static resource address via props.
 > - All TUIKit components must be wrapped inside UIKitProvider; otherwise, they will not be able to obtain their context dependencies, resulting in abnormal styling.
@@ -122,7 +121,6 @@ This section mainly describes how to implement the virtual background via the at
 Before invoking the virtual background feature, you must first check whether the browser supports it and initialize the resource path.
 
 > **Note:**
->
 > - Publish the node_modules/trtc-sdk-v5/assets directory to a CDN or static resource server. For details, see the [SDK documentation](https://web.sdk.qcloud.com/trtc/webrtc/doc/zh-cn/tutorial-36-advanced-virtual-background.html).
 > - When using the [initVirtualBackground](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#initVirtualBackground) interface, pass the assetsPath static resource address.
 > - The virtual background feature depends on a camera device. You can use [useDeviceState](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#module-DeviceState) to check the device status.
@@ -155,9 +153,6 @@ onMounted(async () => {
 
 Before the user confirms applying the background, you usually need to preview the effect first. Use the [setVirtualBackground](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#setVirtualBackground) method to set the preview effect. At this point, it is not applied to the video stream visible to remote users.
 
-> **Note:**
->
-
 > Calling `setVirtualBackground` only takes effect in the local preview. Remote users will not see the virtual background effect; it is synchronized to the remote video stream only after `saveVirtualBackground` is called.
 >
 

package/resource/knowledge/roomkit/preset/android/integration.md

@@ -1,9 +1,6 @@
 TUIRoomKit is a comprehensive multi-party audio and video conferencing solution built on TRTC. It provides a complete set of UI components along with all the core functionality you need to get up and running quickly.
 
 This documentation walks you through integrating TUIRoomKit into your project to enable reliable multi-party audio/video conferencing. You'll also find step-by-step guides for customizing image assets, localizing UI text, and configuring other options—everything you need to build audio/video experiences that align with your brand.
-| Room Preparation Page | Room Main Page | Member Management |
-| --- | --- | --- |
-|  |  |  |
 
 ## Prerequisites
 
@@ -95,7 +92,6 @@ After completing the above steps, Android Studio will usually prompt you to **Sy
 After integrating the code, complete the login process. This step is **required to use TUIRoomKit features**—you must log in successfully before accessing any functionality. Verify that all parameters are set correctly:
 
 > **Note:**
->
 > The sample code calls the login API directly. In production scenarios, always call AtomicXCore's login service **after** completing your own user authentication and login workflow. This ensures correct business logic flow, prevents data inconsistencies, and integrates seamlessly with your user management and permission systems.
 >
 

package/resource/knowledge/roomkit/preset/flutter/integration.md

@@ -1,7 +1,4 @@
 TUIRoomKit is a comprehensive multi-party audio and video conferencing solution powered by TRTC. It provides a full suite of UI components and essential features out of the box. This guide walks developers through integrating TUIRoomKit into their projects to enable robust multi-party audio and video conferencing. It also covers how to quickly customize image assets, localize UI text, and configure other settings, empowering you to build branded audio and video applications.
-| Room Preparation Page | Standard Room Home | Large Webinar Room Home | Member Management |
-| --- | --- | --- | --- |
-|  |  |  |  |
 
 ## Prerequisites
 
@@ -111,7 +108,6 @@ To enable proper page navigation and multilingual UI, update your Flutter app as
 After integration, complete the login process—a **critical step for using TUIRoomKit**. You must log in successfully before accessing TUIRoomKit features. Ensure all parameters are configured correctly:
 
 > **Note:**
->
 > The sample code calls the login interface directly. In production, always call TUIRoomKit's login service **after your own user authentication and login logic**. This prevents business logic confusion and data inconsistencies, and ensures seamless integration with your user management and permission system.
 >
 
@@ -233,7 +229,7 @@ class YourMainPage extends StatelessWidget {
 | Parameter | Type | Description |
 | --- | --- | --- |
 | <code>roomID</code> | <code>String</code> | - Unique Room Identifier.<br>- Length: 0-48 bytes.<br>- Use only numbers, English letters (case-sensitive), underscores (_), and hyphens (-). Avoid spaces and Chinese characters. |
-| <code>behavior</code> | <code>RoomBehavior</code> | - Main Room Page initialization source.<br>- Parameter options:<br>- create: Host creates the room (requires Room Creation Options). For detailed usage of CreateRoomOptions, please refer to: CreateRoomOptions Structure Specifications.<br>- enter: Participant joins the room. |
+| <code>behavior</code> | <code>RoomBehavior</code> | - Main Room Page initialization source.<br>- Parameter options:<br>- create: Host creates the room (requires Room Creation Options). For detailed usage of CreateRoomOptions, please .<br>- enter: Participant joins the room. |
 | <code>config</code> | <code>ConnectConfig</code> | Controls audio/video device behavior after entering the room. |
 
 **ConnectConfig Parameter Descriptions:**
@@ -313,21 +309,16 @@ class YourMainPage extends StatelessWidget {
 **For detailed parameter descriptions, see:** RoomMainWidget Constructor Parameter Descriptions and ConnectConfig Parameter Descriptions.
 
 > **Note:**
->
 > When joining a large webinar room using TUIRoomKit, ensure the room ID created on the web starts with `webinar_`.
 >
 
 ## Core Features
 
 Once `RoomMainWidget` is integrated, you get a full-featured multi-party audio and video conferencing interface, including member management, device control, room information display, and more. This is the core of the TUIRoomKit component.
-| Standard Room | Large Webinar Room |
-| --- | --- |
-|  |  |
 
 ## UI Customization
 
 > **Note:**
->
 > UI customization, icon customization, and text customization require modifying TUIRoomKit source code. When integrated via the pub Dependency Manager, TUIRoomKit is treated as an immutable dependency. Each time you run flutter pub get, Flutter:
 >
 > 1. Checks the version in pubspec.lock.
@@ -349,9 +340,6 @@ Once `RoomMainWidget` is integrated, you get a full-featured multi-party audio a
 > `      path: room`
 
 The `RoomMainWidget` main room page is highly customizable and feature-rich. Developers can adapt the UI to fit their business requirements. Below are the main view components in `RoomMainWidget` for quick modification.
-| Standard Room | Large Webinar Room |
-| --- | --- |
-|  |  |
 
 **RoomMainWidget Component Details**
 

package/resource/knowledge/roomkit/preset/ios/integration.md

@@ -1,9 +1,6 @@
 TUIRoomKit is a comprehensive multi-party audio and video conferencing solution built on TRTC. It provides a complete set of UI components along with all the core functionality you need to get up and running quickly.
 
 This documentation walks you through integrating TUIRoomKit into your project to enable reliable multi-party audio/video conferencing. You'll also find step-by-step guides for customizing image assets, localizing UI text, and configuring other options—everything you need to build audio/video experiences that align with your brand.
-| Room Preparation Page | Room Main Page | Member Management |
-| --- | --- | --- |
-|  |  |  |
 
 ## Prerequisites
 
@@ -88,7 +85,6 @@ To enable audio/video features, your app must request microphone and camera perm
 After integrating the code, complete the login process. **This step is required to use TUIRoomKit.** You must log in successfully before accessing any features. Verify that all parameters are correctly configured:
 
 > **Note:**
->
 > In the sample code, login is handled in the `didFinishLaunchingWithOptions` method. In real-world projects, **call the AtomicXCore login service only after your own user authentication and login procedures have completed**. This prevents business logic conflicts and ensures seamless integration with your user management and permission systems.
 >
 
@@ -279,7 +275,6 @@ Once you've integrated `RoomMainView`, your application will offer a full-featur
 ## Customize UI
 
 > **Note:**
->
 > Customizing UI elements, icons, or text requires modifying the TUIRoomKit source code. When you integrate TUIRoomKit via CocoaPods, it acts as an immutable dependency. Each time you run `pod install`, CocoaPods will:
 >
 > - Check the version listed in Podfile.lock.
@@ -329,7 +324,6 @@ TUIRoomKit manages UI image resources in `TUIRoomKit.xcassets`. Use Xcode's grap
 TUIRoomKit uses the [Apple Strings Catalog](https://developer.apple.com/documentation/xcode/localizing-and-varying-text-with-a-string-catalog) tool to manage UI text. You can easily adjust text using Xcode's visual tools.
 
 > **Note:**
->
 > The Apple Strings Catalog (.xcstrings) format, introduced in Xcode 15, streamlines localization management. It supports structured formats for plurals, device-specific variants, and more, and is now the recommended localization approach for iOS and macOS apps.
 >