Reference

Packages

Understand the consolidated package story, the scaffolder, and the import surface the current product expects developers to use.

What developers can install today

The public docs route should reflect the package surface that actually exists in the repository now.

PackagePurposeNotes
clivlyRuntime imports + CLIConsolidated runtime package plus the CLI command developers keep using after setup.
create-clivlyApp creation bootstrapScaffolder for npm create clivly, wrapping the init flow for greenfield starts.
@clivly/sdkCloud connection SDKPackage-local reference for WebSocket presence, HTTP fallback, sync, serverless, and diagnostics.
@clivly/chat-widgetVisitor chat widgetEmbeddable React and script-tag widget with a host-side session bootstrap route.
@clivly/auth-clerkClerk auth adapterClerk adapter for host session resolution.
@clivly/auth-workosWorkOS auth adapterWorkOS adapter for host session resolution.
@clivly/auth-better-authbetter-auth adapterbetter-auth adapter with no runtime dependency lockstep.
@clivly/coreContracts + configEntity config and schema discovery contracts that the runtime shares.

Imports that matter

The consolidated import story is important because the runtime package and CLI now share the same public mental model.

imports.ts
import { createClivlySDK, defineClivlyConfig } from "clivly/sdk";
import { fromDrizzle } from "clivly/drizzle";
import { clivlyVite } from "clivly/vite";
import { createClerkAuthAdapter } from "clivly/auth/clerk";
import { createWorkOSAuthAdapter } from "clivly/auth/workos";
import { createBetterAuthAdapter } from "clivly/auth/better-auth";