Roadmap and limitations
This page lists what Chat does not do today, so you can plan around it. It is a list of limitations, not a release schedule. No dates are promised.
Not available yet
Section titled “Not available yet”| Area | Today | What to do now |
|---|---|---|
| UI components | There are no embeddable components such as a message list or a composer. You build the UI with the client libraries. | Use the Angular and React pages as a starting point. The Chat web app is available as a standalone UI. |
| Message search | Not available. | Keep your own index if you need search. |
| Voice, video and screen sharing | Not available. | Use a separate service. |
| Bots and webhooks | Not available. Chat does not call your server when something happens. | Send messages from your backend with a backend client. Receive live events in the web app with ccs-chat-notifications-client. |
| Integrations and AI features | Not available. | Build them in your own application. |
Attachments
Section titled “Attachments”A message can reference files, up to 10 attachments each. An attachment is a reference by file_id with a name, a type and a size. Chat does not store files, and it does not upload or serve them. A separate File service is planned. Until then, your application stores its files and puts their ids in the messages. See Messages.
Notifications
Section titled “Notifications”- Push is not per conversation. Push goes to members who are offline. Chat tracks whether the user is online, not which conversation is open, so an online user looking at another conversation gets no push for this one. A per-conversation “actively viewing” signal is not available. See Push notifications.
- Push is web only in the SDKs.
ccs-chat-notifications-clientregisters web push. Native mobile push registration is not covered by any SDK. - Channel push is for mentions. In a channel, push goes to mentioned members only.
- TypeScript only. The three libraries are TypeScript, with Angular and React adapters. For Java, .NET, Python, Go and others, call the REST API or generate a client. See Use the REST API from any stack.
- React Native.
ccs-chat-user-clientworks with the globalfetch.ccs-chat-notifications-clientis not covered, because React Native lacksEventSourceand the Push API without polyfills. See Mobile and React Native. - No Angular wrapper for push. Use
ChatPushClientfrom your own service. - The hooks are not a cache. If you use TanStack Query or SWR, call the client from those.
- Module formats. Each package ships ES modules and CommonJS. Load it one way per app: the two builds are separate copies, so
instanceofchecks do not cross them.
Product behaviour to know
Section titled “Product behaviour to know”- Direct conversations are fixed. A
DIRECTconversation has two members that never change. Its status can be changed only by a backend client. - Business rules stay with you. Chat enforces permissions and membership. It does not know who may talk to whom. See Chat permissions.
- The Identity Server is required. Chat has no sign-in of its own. See The Identity Server comes first.
See the changelog for what has shipped.