CometChat Skills v4.3.0 adds a Visual Builder path to chat integration. When you run /cometchat add chat to my app, the dispatcher now asks one extra question: do you want to customize visually with drag-and-drop in the browser, or in code with code-driven defaults?
Pick Visually and the dispatcher opens CometChat's UI Kit builder in your browser, waits while you set colors, layout, and features, then fetches the config and writes the integration straight into your project. No ZIP downloads. No copying files out of a dashboard and into your repo by hand. It all starts from one line: npx @cometchat/skills add.
Where this fits
A lot of teams are building with Cursor, Claude Code, Kiro, and other agentic coding tools. We didn't ask them to leave. We met them where they already work. The Skills path is a fast way to add chat through the agent you're already typing into, and it sits alongside the integration methods we've spent years on: the Widget Builder, the UI Kit Builder, the UI Kits, and the SDKs. Same product, one more on-ramp.
Why this matters to you as a developer
The visual-versus-code tradeoff used to be a real fork. Visual tools gave you a nice editor and then handed you a ZIP to reconcile against your actual codebase. Code-first gave you control and a stack of styling decisions to make by hand. v4.3.0 removes the reconciliation step. You design in the browser, and the agent emits production code into the files you already have, in the framework you're already using.
You also keep your edits. Re-run /cometchat, pick re-sync, and updated dashboard customizations pull into your app without overwriting code you changed by hand.
Key features and capabilities
The UI-Kit Builder path covers React, React Native, Android V6, and Flutter V6 today. Angular auto-detects and falls back to the in-code path, with a note explaining why.
Three CLI commands back the workflow, and the agent calls them under the hood, though you can run them yourself:
CometChat builder create spins up a builder instance, reusing an active builder on the same app so you don't pile up orphaned ones. Pass --force when you actually want a fresh one.
CometChat builder fetch pulls your saved config back down once you've customized.
CometChat builder list shows the builders tied to your app.
Then cometchat verify --builder validates the result before anything hits runtime. It checks:
Settings files and the builder envelope
Wrapper components
Dependency wiring
The generated application structure
What's interesting about the tech
Every Visual Builder integration carries a builder envelope with an ID, a name, and the settings. Earlier integrations that left it out fell back to default config silently, which is the worst kind of bug: it compiles, it runs, it just ignores everything you set. v4.3.0 enforces the envelope across the React, React Native, Android, Flutter, and iOS recipes, and verify --builder flags anything missing it.
The dispatcher also handles the messy real-world states instead of leaving you a half-finished integration:
Expired builders
Missing permissions
A browser that won't launch
Stale config
An active-builder conflict
Reference links
GitHub release: https://github.com/cometchat/cometchat-skills/releases/tag/v4.3.0
CometChat documentation: https://www.cometchat.com/docs
Nivedita Bharathy
Product Marketing Specialist , CometChat