Want to request a feature?

Create a new request and help us improve CometChat!

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

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

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

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

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