Native Unread Thread Reply Indicator in Message List (iOS UI Kit)

Currently, in CometChat iOS UI Kit v5, threaded messages only display the total number of replies for a parent message in the message bubble. However, there is no native indicator to show when a thread has unread or newly received replies. This limitation makes it difficult for users to quickly identify which message threads have new activity without manually opening each thread. A customer recently requested the ability to visually indicate new or unread thread replies directly in the message list, similar to unread indicators used for conversations.

Sending Bot Messages to Specific Agentic Conversations via Send Bot Message API

Currently, the Send Bot Message API does not support sending bot messages within agentic conversations. Use Case: In some implementations, backend systems may perform actions (e.g., executing a tool, completing an external workflow, or retrieving data) whose results need to be communicated back to the agent. Ideally, developers should be able to send a bot message tied to the specific agentic conversation. Requested Enhancement: Allow the Send Bot Message API to send messages for agentic bots.

Remove Android Support Library Dependencies from CometChat Android SDK to Enable Jetifier Disablement

The customer would like to disable Jetifier in their Android project; however, the current CometChat Android SDK still depends on legacy Android Support libraries, which forces Jetifier to remain enabled. When attempting to manually exclude these transitive dependencies, the application crashes during SDK initialization due to the missing class android.arch.lifecycle.ProcessLifecycleOwnerInitializer. The customer noted that this dependency could be replaced with the AndroidX equivalent androidx.lifecycle.ProcessLifecycleOwnerInitializer. They are requesting that the CometChat Android SDK update its dependencies to fully adopt AndroidX and remove legacy support library references so that projects can safely disable the deprecated Jetifier option.

Ability to sort or group conversations by Tags (e.g., "Open" and "Closed") in the Conversations component in real time

Currently, the Conversations component does not support sorting or grouping conversations by tags (e.g., open or closed). In our use case, we want to display conversations in two sections: Open Chats and Closed Chats. As a workaround, we used two separate Conversations components, each with its own ConversationsRequestBuilder filter: readonly openConversationsRequestBuilder = new CometChat.ConversationsRequestBuilder() .setLimit(30) .setGroupTags(['open']) .withTags(true) .withUserAndGroupTags(true); readonly closedConversationsRequestBuilder = new CometChat.ConversationsRequestBuilder() .setLimit(30) .setGroupTags(['closed']) .withTags(true) .withUserAndGroupTags(true); Initially, the conversations appear correctly. However, when a new message is sent, the conversation sometimes reappears in the other Conversations component, even though it does not match the tag filter. Expected Behavior: Conversations should remain filtered according to the ConversationsRequestBuilder, even when real-time updates occur.

Support Reporting Frontend Action Execution Results to Agent in BYO Agent (AG-UI) Integration

Currently, in CometChat’s BYO Agent (AG-UI) integration, there is no mechanism to report the execution result of frontend-triggered actions back to the AI agent. When an agent triggers an action that is executed on the frontend (for example, schedule_appointment, chat_escalation_handoff, or other UI-driven workflows), the frontend can execute the action but cannot communicate the success or failure status back to the agent. Example Flow: User: "My app keeps crashing, please create a ticket"Agent → CometChat: TOOL_CALL (create_support_ticket) CometChat → Frontend: Trigger action Frontend → Backend API: Create support ticket Backend: Ticket #12345 created successfully Expected behavior: The frontend should be able to report the result back to the agent (e.g., success with ticket ID or failure with an error message), allowing the agent to respond: "Your ticket #12345 was created successfully. Our support team will respond within 24 hours."

Fallback Handler for Unregistered Action Calls in CometChatAIAssistantChat

Introduce a fallback handler that triggers whenever an unregistered action call is detected. This would allow developers to implement custom logic on the frontend when such cases occur.

Add 24-Hour Clock Format Support in Web Widget

In Sweden, the 24-hour clock format is the standard, so the timestamps should appear in 24-hour format instead. Additionally, the widget displays “em” and “fm” instead of the expected 24-hour time representation, which makes the timestamps appear incorrect for Swedish users.

React Native UIKit: Support group conference (meet) call logs in CometChatCallLogs component

I am using the React Native UIKit CometChatCallLogs component to display call history in my app. Currently, it only shows direct call logs (category: "call") and does not include group conference calls (category: "meet"). Group calls are visible in the CometChat dashboard, but they are not displayed in the UIKit call logs component. It would be helpful if CometChatCallLogs could also support meet-type call logs, so we can show a complete call history (both 1:1 and group calls) in the app without needing to build a custom implementation.

Display Custom User Metadata in Widget User Profile

We would like to request the ability to display additional user metadata fields within the frontend user profile in the widget.

Add hideScrollToBottomButton Toggle and Scroll-to-Bottom Button Customization in CometChatMessageList in Flutter

Add a hideScrollToBottomButton toggle and a parameter to pass a custom widget as public properties in CometChatMessageList. This will allow developers to control the visibility of the scroll-to-bottom button and provide better customization options so the button can be modified to match the application's UI and behavior requirements.

Add Sensitive Data Masking (Phone & Email) Support in New Moderation System

We are currently using the new Moderation system and observed that the Contact Details Filter and Email Filter only block messages when phone numbers or email addresses are detected. In the earlier Legacy Data Masking feature, there was an option to mask sensitive information (such as phone numbers and email addresses) while still allowing the message to be delivered. However, this masking capability does not appear to be available in the new Moderation system. Current Behavior: Messages containing phone numbers or email addresses are completely blocked. Expected Behavior / Requirement: The message should be delivered successfully. Sensitive information such as phone numbers and email addresses should be automatically masked instead of blocking the message. Example: Phone: 9876543210 → 98XXXXXX10 Email: john.doe@gmail.com → jo***@gmail.com

Include detailed violation “Reasons” in moderation_engine_blocked Webhook Payload

Description: Moderation is functioning correctly, and the CometChat Dashboard displays comprehensive Violation Details → Reasons whenever a message is blocked. However, the moderation_engine_blocked webhook payload currently only includes rule metadata such as: rule_id rule_name revision action blockedAt The payload does not include the detailed “Reasons” explanation that is visible in the dashboard. Problem Statement: Since the webhook does not expose the violation reason, client applications can only show a generic message like “Message blocked” to end users. This limits transparency and negatively impacts user experience. Requested Enhancement: Enhance the moderation_engine_blocked webhook JSON payload to include a detailed violation_reasons (or similar) field, matching the Violation Details → Reasons shown in the dashboard.

CometChat – Blocked State Messages Should Not Update Delivery Status After Unblock

We have identified an issue related to message delivery status behavior in CometChat when users are blocked and later unblocked. Scenario: User A logs in on Device 1 User B logs in on Device 2 User A blocks User B User B sends messages to User A (messages correctly show single tick) User A unblocks User B User B sends a new message after being unblocked Current Behavior: Messages that were sent by User B while blocked initially show a single tick (correct behavior). However, once User A unblocks User B, those old messages are automatically updated to double blue ticks, even though they were never delivered to User A at the time they were sent. Expected Behavior: Messages sent while the sender was blocked should permanently remain in a single tick (undelivered) state, even after the unblock action. Only messages sent after the unblock event should follow the normal delivery and read receipt lifecycle.

Archive Conversation Feature in Flutter CometChat UIKit

Request to add an Archive Conversation feature in the CometChat UIKit. Currently, there is no built-in support for archiving chats. Users should be able to archive conversations (primarily groups, but ideally both group and one-to-one chats) directly from the conversation list. Archived conversations should be moved out of the main list and accessible in a dedicated Archive section, with an option to unarchive them.

Ability to Customize Group Action System Messages

Currently, when a user is removed from a group, the system automatically displays the message “System kicked user.” For a business-to-business application, the term “kicked” may come across as informal and unprofessional. We would like the ability to modify or customize group action system messages specifically the wording used when a user is removed from a group.

Add Toggle to Exclude Deleted Thread Replies from Thread Reply Count

Currently, deleted replies are still included in the total reply count of a thread. The proposed enhancement would introduce a toggle in dashboard which will exclude deleted replies from the thread reply count when enabled

Export Functionality for notification Logs

Could you please provide an export functionality (or a full export) of the complete notification logs so that we can identify any patterns or root causes?

Call Continuity During App Navigation

Confirmation of call continuity while navigating across different screens within the app

Support for Picture-in-Picture mode

We would like to request support for Picture-in-Picture (PiP) mode during ongoing audio and video calls within the application. The PiP mode should allow users to: Minimize the active call screen into a floating window. Ability to chat during ongoing audio/video calls(video and chat working simultaneously) Drag and reposition the PiP window freely across the screen for better usability and visibility.

Real-Time Group Avatar Update

The group avatar update functionality should reflect changes instantly for all group members. When a user edits or changes the group profile picture, the updated avatar must be displayed in real time across all participants’ devices without requiring a manual refresh or app restart.