Currently, CometChat provides unread message counts at the conversation/group level, but there is no way to retrieve unread counts filtered by a specific sender within a group conversation. We need the ability to fetch the unread message count for messages sent by a particular user (for example, a doctor) from another user's perspective (for example, a patient).

Request support for advanced bot functionality within group conversations: Protected Bot Membership Automatically add a predefined bot to every newly created group. Prevent the bot from being removed, blocked, muted, or otherwise restricted by any group member, admin, or owner. Ensure the bot remains a permanent participant in the group. Selective Message Visibility in Groups Allow bots to send messages within a group that are visible only to specific users or user segments. Enable use cases such as personalized notifications, role-based announcements, and targeted reminders while keeping the conversation context inside the group. These capabilities would help developers build more advanced automation, notification, and assistant-driven experiences within CometChat groups.

urrently, CometChat does not provide a mechanism to delete all users and groups in bulk through either the Dashboard or an API. Customers managing test, staging, or development environments often need to reset application data efficiently without manually deleting individual users and groups. We request the introduction of: A Bulk Delete Users API. A Bulk Delete Groups API. An option in the CometChat Dashboard to clear/delete all users and groups. Appropriate safeguards such as confirmation prompts, permissions, and audit logging to prevent accidental deletion.

Currently, editMessage() allows updating metadata associated with a MediaMessage (such as captions, tags, or custom metadata), but it does not support replacing the actual uploaded file or attachment. The attachment URL remains permanently linked to the original uploaded file, requiring users to delete the existing message and send a new one whenever they need to replace an image, video, audio file, or document.

We would like to request support for filtering groups and conversations directly by membersCount=0 through the REST APIs. Currently, this requires fetching records and performing client-side filtering, which adds additional API calls and processing overhead. Having a server-side filter for empty groups would simplify implementation and improve efficiency for use cases involving inactive or abandoned groups.

Currently, the CometChat Widget only supports changing the language, but it does not allow overriding or customizing localization/translation keys. We need support for custom localization key overrides within the Widget so developers can modify default UI text according to their application requirements without migrating to the full UI Kit or UI Kit Builder.

Introduce support for additive push token registration in the SDK to enable simultaneous push notifications for multiple logged-in users on the same device. Currently, when the same FCM/APNs token is registered for another user via registerPushToken, it gets reassigned from the previously registered user, causing only the most recently registered account to receive notifications. This limitation impacts applications implementing in-app account switching or multi-account experiences where users remain signed into multiple accounts concurrently. The requested enhancement would allow a single device token to be associated with multiple CometChat users at the same time, ensuring independent push delivery for each account and enabling seamless multi-account notification support similar to modern messaging platforms.

Currently the Chat Logs section in the CometChat dashboard only supports filtering by SenderUIDs. Please add support for ReceiverUID-based filtering as well, as it would help us efficiently monitor and audit conversations across multiple public chat groups in our integration. Support for combined SenderUID and ReceiverUID filtering would also be very useful.

Currently, a conversation between two users is only created after a message is sent or through indirect workarounds such as sending and deleting a message or using the Add Friends API with addToConversations: true. We need a direct way to create/initiate a conversation between users without requiring any message exchange.

Currently, navigating between conversations, groups, and chat sections shows a temporary grey loading/skeleton state while data is re-fetched and re-rendered. We would like support for offline caching or persistent local storage in the UIKit to enable smoother transitions and reduce visible loading states during navigation, improving the overall chat experience and perceived performance.

When a user searches for a word/message in the chat and clicks on a search result, the entire page refreshes unexpectedly instead of smoothly navigating to the selected message. This negatively impacts the user experience and breaks the expected navigation flow during message search in React applications using the CometChat UI Kit. As per the CometChat React Search documentation, onMessageClicked should support custom navigation behavior without triggering a full page reload. Requirement: Prevent full page refresh when clicking a search result Allow smooth navigation/scrolling to the selected message Ensure onMessageClicked works correctly for custom navigation handling in SPA-based React applications This enhancement would improve usability and align the behavior with expected React application navigation patterns.

Request to support for increasing the current 50-entity limit per Data Import API request or providing an alternative bulk CSV import mechanism to improve import efficiency and reduce operational overhead. This would help streamline large-scale migrations and reduce the number of API calls and batching logic required during onboarding.

request for a REST API capability similar to the SDK method getMessageReceipts(), which would allow identifying the exact group members to whom a group message was sent using the messageId. This is specifically needed for cases where group membership changes over time, as current APIs only return the current group members and not the historical recipients at the time the message was sent.

Introduce built-in state persistence support for the CometChatSearch component in the Flutter UI Kit so that previously entered search keywords and search results are retained when users navigate away from and reopen the search screen during the same app session. Currently, the search state resets completely upon reopening the component, forcing users to re-enter search queries and repeat the search process. This behavior negatively impacts usability, especially in workflows involving frequent navigation between conversations and search results. Providing automatic state retention or exposing properties/callbacks to preserve and restore the search context would align the component with modern search UX standards, improve user experience, and reduce the need for custom state-management implementations.

Introduce native support for inline URL preview generation within CometChatMessageComposer in the Flutter UI Kit. Currently, link preview metadata is fetched and displayed only after the message has been successfully sent, whereas modern messaging applications such as WhatsApp and Microsoft Teams provide real-time preview generation while the user is composing the message. This feature should detect valid URLs as they are typed or pasted, fetch preview metadata before sending, and display a dynamic preview card inline above the composer. Supporting pre-send link previews would significantly improve user confidence, enhance the messaging experience, and align the UI Kit with modern chat application standards without requiring developers to build complex custom implementations.

Introduce dedicated styling support for mention text (e.g., @username) within the Message Information section of the UI Kit. Currently, mention names rendered in this view do not respect any customizable styling properties, making it difficult to maintain UI consistency with the main message list where mention styling is typically configurable. This limitation prevents developers from aligning colors, fonts, and emphasis for mentions across different parts of the application. Providing a property such as mentionTextStyle or a granular customization hook for mentions specifically within the Message Information component would ensure visual consistency, improve flexibility, and eliminate the need for complex custom overrides.

Introduce native support in the UI Kit and SDK for editing captions of media messages (such as images, videos, audio, and documents) directly within the message composer. Currently, while developers can implement captions for media using custom CometChatMessageTemplate, there is no built-in mechanism to edit these captions once the message is sent. This limitation forces developers to create complex custom workflows, which do not integrate seamlessly with the existing composer or editing flow. Providing a standardized solution—where media captions can be edited similar to text messages within the composer—would ensure consistency, reduce implementation overhead, and significantly improve both developer experience and end-user usability.

Introduce a native in-chat search functionality within the message screen of the UI Kit, allowing users to search messages directly inside an active conversation (similar to apps like WhatsApp). Currently, there is no built-in support for an integrated search bar within the message view, which limits usability and impacts the overall user experience. This feature should enable users to quickly search, navigate, and highlight messages within a conversation without leaving the chat screen. Providing this as a configurable UI Kit component or property would enhance usability, maintain UI consistency, and eliminate the need for custom implementations, thereby improving developer experience and end-user satisfaction.

Currently, the CometChat SDK provides real-time events only for the user who initiates the block action (ccUserBlocked / ccUserUnBlocked). The blocked user (User B) does not receive any real-time event when another user (User A) blocks or unblocks them. The hasBlockedMe flag on the user object is only updated when the user object is explicitly fetched from the server via CometChat.getUser() or on screen navigation. This makes it impossible to update the blocked user's UI in real-time without relying on workarounds such as polling, send-failure detection, or a webhook-based backend solution. The request is to add a new real-time listener event (e.g., onUserBlockedMe / onUserUnblockedMe) in the SDK's UserListener that fires on the blocked user's client when they are blocked or unblocked by another user. This would allow UIKit and app developers to immediately hide the composer, show a "You have been blocked" indicator, and update the conversation list without requiring server-side infrastructure or manual user object re-fetching.

Introduce direct styling support for the message bubble displayed in the CometChatMessageInformation component within the Flutter UI Kit. Currently, the message bubble shown in the Message Information view does not respect configurations provided via messageInformationStyle, resulting in inconsistent UI compared to the main message list. Developers are unable to customize properties such as background color, text color, or overall appearance, and the only available workaround is overriding the entire listItemView, which increases complexity and maintenance overhead. Providing a dedicated property such as messageBubbleStyle or a granular customization hook for the message bubble would ensure design consistency, improve developer experience, and maintain the modular integrity of the UI Kit without requiring full component overrides.