Packages
Every @cognitiondesk package that's actually published on npm, one page each: what it does, how to install it, a minimal example that runs as-is. @cognitiondesk/mcp has its own page — see MCP Server.
Talk to the API
UI you can embed
@cognitiondesk/widgetv1.9.0Embeddable chat widget for vanilla JS and React. Also re-exports the client for backward compatibility.
Quickstart@cognitiondesk/storefrontv0.2.2Presentational building blocks for a public product catalog — header, grid, cards, gallery. No fetching, no backend calls.
QuickstartBuild agents on top
@cognitiondesk/agent-runtimev0.1.0Wraps @cognitiondesk/client with agent CRUD, model selection, invocation, streaming and usage metrics.
Quickstart@cognitiondesk/orchestration-kitv0.1.0Task delegation, multi-step workflows and progress tracking for multi-agent coordination.
Quickstart@cognitiondesk/skill-packsv0.1.0Injectable skill packs (forum, devops, coordination, rag, insight) plus a SkillInjector.
Quickstart@cognitiondesk/agent-team-orchestrationv0.1.0Composes agent-runtime + orchestration-kit + skill-packs into team (squad) management.
QuickstartAbout backendUrl
client, widget and agent-runtime all default to https://api.cognitiondesk.com when you don't pass backendUrl — you only need it to point somewhere else (self-hosted, staging). This is the option that went unnoticed for a while: an old @cognitiondesk/widget build had the previous, now-decommissioned backend host baked in as the default, and every embed that didn't pass backendUrl went silent the moment that host was suspended. Since widget 1.7.1 (and client 0.2.0, agent-runtime 0.1.0) the default is api.cognitiondesk.com, so most integrations don't need to set it at all — but if you're on an older lockfile, check what your build actually points to.
@cognitiondesk/agents is not published on npm yet (npm view returns 404) — it isn't documented here until it is.
@cognitiondesk/mcp — see MCP Server.