Unread Thread Indicator on Message Bubbles
Add support for displaying unread indicators on message bubbles that contain threads (e.g., β12 repliesβ). The indicator can either show the unread count or a simple unread marker.
π‘ Feature Request
Unread Thread Indicator on Message Bubbles
Add support for displaying unread indicators on message bubbles that contain threads (e.g., β12 repliesβ). The indicator can either show the unread count or a simple unread marker.
π‘ Feature Request
Idea
User List Export from Dashboard
Request to add an export option in the CometChat dashboard to download active and inactive user lists directly. This would improve ease of access and reduce reliance on API calls for basic data retrieval.
π‘ Feature Request
Idea
User List Export from Dashboard
Request to add an export option in the CometChat dashboard to download active and inactive user lists directly. This would improve ease of access and reduce reliance on API calls for basic data retrieval.
π‘ Feature Request
Idea
Add Local Caching Mechanism to Improve Chat Load Performance in CometChat React Native UI Kit
Opening a conversation in the CometChat React Native UI Kit currently triggers a full reload of messages from the server each time, resulting in slower load times and a less responsive user experience. In a real-time chat application, users expect conversations to open instantly with previously viewed messages readily available. The lack of a local caching mechanism leads to repeated network calls and unnecessary data fetching, even for recently accessed chats. Introducing a local caching mechanism to store recent conversations and messages on the device would allow chats to load instantly while syncing with the server in the background. This would significantly improve performance, reduce latency, and provide a smoother and more seamless user experience, especially in low or unstable network conditions.
π‘ Feature Request
Idea
Add Local Caching Mechanism to Improve Chat Load Performance in CometChat React Native UI Kit
Opening a conversation in the CometChat React Native UI Kit currently triggers a full reload of messages from the server each time, resulting in slower load times and a less responsive user experience. In a real-time chat application, users expect conversations to open instantly with previously viewed messages readily available. The lack of a local caching mechanism leads to repeated network calls and unnecessary data fetching, even for recently accessed chats. Introducing a local caching mechanism to store recent conversations and messages on the device would allow chats to load instantly while syncing with the server in the background. This would significantly improve performance, reduce latency, and provide a smoother and more seamless user experience, especially in low or unstable network conditions.
π‘ Feature Request
Idea
Retry or Re-upload Option for Failed Media Uploads Due to Network Issues
Currently, when a media or image upload fails due to poor or unstable network connectivity, there is no option for the user to retry or re-upload the file directly. We propose adding a retry or re-upload option for failed media uploads, allowing users to easily attempt the upload again without restarting the entire process. This enhancement would improve usability and provide a smoother experience in cases where uploads fail due to temporary network issues.
π‘ Feature Request
Idea
Retry or Re-upload Option for Failed Media Uploads Due to Network Issues
Currently, when a media or image upload fails due to poor or unstable network connectivity, there is no option for the user to retry or re-upload the file directly. We propose adding a retry or re-upload option for failed media uploads, allowing users to easily attempt the upload again without restarting the entire process. This enhancement would improve usability and provide a smoother experience in cases where uploads fail due to temporary network issues.
π‘ Feature Request
Idea
Support for video resolution configuration using UI or programmatically
Support for video resolution configuration using UI or programmatically
π‘ Feature Request
Idea
Support for video resolution configuration using UI or programmatically
Support for video resolution configuration using UI or programmatically
π‘ Feature Request
Idea
Support Multiple Group GUIDs in Get Messages API
Currently, the GET /groups/{guid}/messages API supports fetching messages for only a single group GUID per request. Customers who need messages from multiple groups must make separate API calls for each GUID. A feature enhancement is requested to allow multiple group GUIDs to be passed in a single request (e.g., 10β15 GUIDs) and return the messages for all those groups in one response.
π‘ Feature Request
Idea
Support Multiple Group GUIDs in Get Messages API
Currently, the GET /groups/{guid}/messages API supports fetching messages for only a single group GUID per request. Customers who need messages from multiple groups must make separate API calls for each GUID. A feature enhancement is requested to allow multiple group GUIDs to be passed in a single request (e.g., 10β15 GUIDs) and return the messages for all those groups in one response.
π‘ Feature Request
Idea
Support for Message Forwarding and Multi-Message Selection in React Native UIKit
Feature request for message forwarding and multi-message selection in the React Native UIKit. This feature would allow users to select single or multiple messages within a conversation and perform bulk actions such as Forward, Delete, and Copy. Additionally, users should be able to forward selected messages to one or multiple users or groups directly from the chat interface. Providing this functionality in the React Native UIKit would help developers implement a more advanced and user-friendly chat experience, similar to popular messaging applications like WhatsApp, and would significantly improve message management within conversations.
π‘ Feature Request
Idea
Support for Message Forwarding and Multi-Message Selection in React Native UIKit
Feature request for message forwarding and multi-message selection in the React Native UIKit. This feature would allow users to select single or multiple messages within a conversation and perform bulk actions such as Forward, Delete, and Copy. Additionally, users should be able to forward selected messages to one or multiple users or groups directly from the chat interface. Providing this functionality in the React Native UIKit would help developers implement a more advanced and user-friendly chat experience, similar to popular messaging applications like WhatsApp, and would significantly improve message management within conversations.
π‘ Feature Request
Idea
Expose CometChat Dashboard Metrics via API for CRM Integration
We have a use case where customers want to display CometChat dashboard metrics directly inside their internal CRM or applications. Currently, while messaging events can be captured using webhooks, there is no API available to programmatically fetch dashboard-level metrics (such as message counts, usage analytics, user activity, etc.). Providing an API or endpoint to access these metrics would allow teams to automatically sync CometChat analytics with their internal systems and display them in custom dashboards for stakeholders such as brokers, admins, or support teams. This enhancement would enable better reporting, automation, and deeper integration of CometChat analytics into external platforms like CRMs and internal business tools.
π‘ Feature Request
Idea
Expose CometChat Dashboard Metrics via API for CRM Integration
We have a use case where customers want to display CometChat dashboard metrics directly inside their internal CRM or applications. Currently, while messaging events can be captured using webhooks, there is no API available to programmatically fetch dashboard-level metrics (such as message counts, usage analytics, user activity, etc.). Providing an API or endpoint to access these metrics would allow teams to automatically sync CometChat analytics with their internal systems and display them in custom dashboards for stakeholders such as brokers, admins, or support teams. This enhancement would enable better reporting, automation, and deeper integration of CometChat analytics into external platforms like CRMs and internal business tools.
π‘ Feature Request
Idea
Add Full RTL Support in Web Widget and UI Kits for Arabic Localization
Currently, Arabic localization is not fully supported in our Web Widget and UI Kits because Right-to-Left (RTL) layout support is not yet implemented. Arabic requires proper RTL handling across the UI, including message layouts, navigation elements, alignment, and component structure. Adding full RTL support would enable proper Arabic language localization and improve accessibility for applications targeting Arabic-speaking users. This feature would allow developers to implement Arabic translations while ensuring the UI renders correctly in an RTL layout. Implementing RTL compatibility across the UI Kits will help expand usability in regions where Arabic is widely used and make localization more flexible for developers.
π‘ Feature Request
Idea
Add Full RTL Support in Web Widget and UI Kits for Arabic Localization
Currently, Arabic localization is not fully supported in our Web Widget and UI Kits because Right-to-Left (RTL) layout support is not yet implemented. Arabic requires proper RTL handling across the UI, including message layouts, navigation elements, alignment, and component structure. Adding full RTL support would enable proper Arabic language localization and improve accessibility for applications targeting Arabic-speaking users. This feature would allow developers to implement Arabic translations while ensuring the UI renders correctly in an RTL layout. Implementing RTL compatibility across the UI Kits will help expand usability in regions where Arabic is widely used and make localization more flexible for developers.
π‘ Feature Request
Idea
Add Full RTL Support in UI Kits for Arabic Localization
Currently, Arabic localization is not fully supported in our UI Kits because Right-to-Left (RTL) layout support is not yet implemented. Arabic requires proper RTL handling across the UI, including message layouts, navigation elements, alignment, and component structure. Adding full RTL support would enable proper Arabic language localization and improve accessibility for applications targeting Arabic-speaking users. This feature would allow developers to implement Arabic translations while ensuring the UI renders correctly in an RTL layout. Implementing RTL compatibility across the UI Kits will help expand usability in regions where Arabic is widely used and make localization more flexible for developers.
π‘ Feature Request
Idea
Add Full RTL Support in UI Kits for Arabic Localization
Currently, Arabic localization is not fully supported in our UI Kits because Right-to-Left (RTL) layout support is not yet implemented. Arabic requires proper RTL handling across the UI, including message layouts, navigation elements, alignment, and component structure. Adding full RTL support would enable proper Arabic language localization and improve accessibility for applications targeting Arabic-speaking users. This feature would allow developers to implement Arabic translations while ensuring the UI renders correctly in an RTL layout. Implementing RTL compatibility across the UI Kits will help expand usability in regions where Arabic is widely used and make localization more flexible for developers.
π‘ Feature Request
Idea
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.
π‘ Feature Request
Idea
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.
π‘ Feature Request
Idea
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.
π‘ Feature Request
Idea
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.
π‘ Feature Request
Idea
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.
π‘ Feature Request
Idea
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.
π‘ Feature Request
Idea
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.
π‘ Feature Request
Idea
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.
π‘ Feature Request
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."
π‘ Feature Request
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."
π‘ Feature Request
Idea
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.
π‘ Feature Request
Idea
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.
π‘ Feature Request
Idea
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.
π‘ Feature Request
Idea
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.
π‘ Feature Request
Idea
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.
π‘ Feature Request
Idea
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.
π‘ Feature Request
Idea
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.
π‘ Feature Request
Idea
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.
π‘ Feature Request