CometChat
Conversations, without the chaos
274 followers
Conversations, without the chaos
274 followers
CometChat packs chat, voice, video, and AI Agents into one full-stack conversations platform - so you can stop duct-taping random tools and praying they play nice. Safety, moderation, and analytics come baked in, keeping things smooth as you scale. Flexible integration options for any stack you’ve got - because our job is running the infra, not making you babysit it.
This is the 5th launch from CometChat. View more
AI Agents in Chat
Launching today
Your AI agent belongs in the chat you already built. CometChat's iOS UI Kit lets you turn your existing messaging experience into an AI conversation with streaming responses, chat history, and a fully customizable UI built in. Connect your agent, match your brand, and ship without building AI chat from scratch.
Launch Team
CometChat
Hey Product Hunt!
Amit from CometChat here 👋
Every time someone tells us they're adding an AI agent to their iOS app, the same thing happens. They think the hard part is the AI. It's not. The hard part is that building a decent chat UI eats weeks you didn't budget for. Message bubbles, streaming, history screens; none of it is hard, it's just a slog, and it's the slog nobody warns you about.
So we stopped watching people rebuild the same thing and put it in our iOS UI Kit.
You get the actual chat experience out of the box: streaming responses, suggested prompts, and conversation history so people can pick up an old chat instead of starting from zero every time. Wire up your agent, restyle it to match your app, ship.
It's 1:1 AI conversations today. Agents in group chat is what we're building next and if that's something you'd actually use, tell me, because we're deciding how far to push it right now.
If you kick the tires, I want to hear where it annoyed you as much as where it worked. We'll be in the comments all day.
The part that ate our time wasn't the bubbles, it was what happens when the stream dies halfway. iOS backgrounds the app, the socket drops, and you're left with half an assistant message that the server thinks it finished sending. We moved to persisting server side and treating the client as a replay of a message id, which killed the duplicates but made resume feel slower. Where does the UI Kit keep the partial, and on reconnect does it resume the same message or start it over?
The iOS UI Kit angle feels very practical. Streaming responses and conversation history are exactly the parts that make an AI chat feel like a real product instead of a demo screen.
For group support, I’d be curious how you’re thinking about agent handoff and context. Would multiple users be able to share one AI thread with the same history, or is the first version more about adding AI into existing group chats?
Finally tried CometChat and the AI Agents integration was smoother than I expected, no weird config headaches. Wish the moderation dashboard had a bit more filtering flexibility, but overall it feels like a real step up from stitching together three different SDKs.
CometChat
@hsanvemx That's great to hear 🙌
The "stop stitching three SDKs together" bit is basically why we built it, so that one means a lot.
And fair call on moderation, more filtering flexibility is on our radar. If you tell me the cuts you'd actually want, I'll pass it straight to the team.
Thanks for really putting it through its paces 🙏
The platform looks solid for bringing chat, voice, and video under one roof. One thing I'd love to see is a built-in branching or threaded transcript view for voice and video sessions, so it's easier to jump back to a specific moment or quote during a follow-up. Right now most tools flatten that history, and it can be a real headache for support or sales teams reviewing calls later.
CometChat
@ilk_l13311 that is quite something and I don't want to hand-wave it. What you're describing isn't a small add or a feature behavior tweak. A branchable, navigable transcript where you can grab a specific moment and carry it into a follow-up is a real product surface: timeline, quote-linking, threading a call moment back into chat. Genuinely interesting, and not at all trivial :)
Today: we've got live captions / transcription (β) for calls (English), that's the raw material the flow you're describing would sit on, but it's the groundwork, not the whole thing.
If you can walk me through how your team would actually move through it right from reviewing a support call, to pulling a sales quote, and what a "jump back" looks like in practice I'll take that straight to the team.
A concrete flow is worth far more than a feature request here. Really appreciate you thinking at this depth 🙏
Embedding agents directly into chat UI makes the interaction feel more natural than switching between tools. How customizable is the agent behavior from the developer side?
CometChat
@abdurrahman_fakhrul Thanks for seeing it the way we intended it :)
On developer control, it goes pretty deep.
Two ways in: build the agent natively in our Agent Builder, or bring your own (OpenAI, LangGraph, Mastra, CrewAI, Vercel…) and run it headless or with our UI. It's model-agnostic, so you can swap providers/models without touching the customer experience.
Behavior itself is shaped by:
- Instructions: tone, guardrails, hand-off rules, how it should respond. You can @-mention specific tools/MCP resources inline so the agent knows exactly when to use each one.
- Tools: call any REST endpoint, with templated context ({{uid}}, {{role}}, message metadata) injected into the request.
- MCP endpoints: connect external services/knowledge bases for richer, live context.
- Frontend actions: the agent can drive your UI (open a modal, navigate, fire a notification), not just reply with text.
So it's not a fixed bot you skin, it's the behavior, the tools, the model, and how it acts on your app, all in your hands.
Docs if you want to dig in:
- Overview: https://www.cometchat.com/docs/ai-agents
- Agent Builder: https://www.cometchat.com/docs/ai-agents/agent-builder/overview
- Instructions: https://www.cometchat.com/docs/ai-agents/agent-builder/instructions
- Tools: https://www.cometchat.com/docs/ai-agents/agent-builder/tools/overview
- MCP: https://www.cometchat.com/docs/ai-agents/agent-builder/mcp/overview
- Frontend actions: https://www.cometchat.com/docs/ai-agents/agent-builder/frontend-actions/overview
What are you looking to build? Happy to point you at the exact layer.
Love that moderation is already baked in, that's saved us headaches before. One thing that would seal the deal for me is a no-code webhook builder for routing events to tools like Zapier or Make, so non-dev teammates can wire up workflows without pinging engineering every time.
CometChat
@hasanfia0 Thanks for the love :) Yes that was a very conscious decision from the early stages of our roadmap.
The event plumbing is already there, webhooks fire on messages, user and group activity, calls, even moderation results, so the signal you'd want to route absolutely exists today. What's missing is the part you're actually pointing at: a no-code layer on top so a non-dev can wire "this event → that tool" without standing up an endpoint and pinging engineering every time.
What are some workflows that you were thinking of solving?