Skip to main content
CometChat ships two complementary command-line tools:
Neither CLI writes framework code. The credentials CLI is a pure dashboard/API client — it authenticates and hands your app credentials to the agent skills, which own all framework detection, env-file writing, and code generation.
Both run through npx with no global install, and every command accepts --json for machine-readable output.

Prerequisites

  • Node.js 18+ — both CLIs run through npx.
  • A CometChat accountsign up free. auth login opens the dashboard in your browser to authenticate.

Credentials CLI — @cometchat/skills-cli

Its only job is authenticating against the CometChat dashboard and fetching your App ID / Region / Auth Key, then writing a neutral .cometchat/config.json the skills build on.

Quick start

Authenticate

Opens your browser at the CometChat dashboard for device authentication and stores the bearer token in your OS keychain (falling back to a chmod 600 file).

Provision credentials

Fetches your App ID / Region / Auth Key, prints them as JSON, and writes a neutral .cometchat/config.json. It writes no framework env file — the skill reads config.json and writes the framework-specific env (.env / VITE_ / NEXT_PUBLIC_ …) itself. The config file provision writes:
.cometchat/config.json contains your Auth Key — add it to .gitignore. The Auth Key is for development only; in production, mint a per-user auth token on your backend and log in with loginWithAuthToken() instead of shipping the Auth Key to a client.

Manage config

Read and edit the local .cometchat/config.json (credential/app state only):

Toggle features

Enable or disable app features from the terminal:

Skills CLI — @cometchat/skills

Installs and manages the AI Agent Skills that let your coding agent build with CometChat.
See Agent Skills for the install picker, supported agents, and the prompt-driven workflow.

Scripting and CI

Every command supports --json, and add can be pinned to one agent with --ide, so the whole flow runs non-interactively:
Commands exit non-zero on failure and surface dashboard errors verbatim (for example ACCESS_DENIED, EXPIRED, TIMEOUT, ABORTED), so a broken auth or provisioning step fails the CI job loudly instead of continuing with empty credentials.

Next steps

Agent Skills

Install the skills and build CometChat from natural-language prompts

MCP Integration

Connect CometChat to any Model Context Protocol–compatible agent

React Integration

The manual React UI Kit setup, credentials and all

Get your credentials

Open the CometChat dashboard