npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@kognitivedev/backend-cloud

v0.2.29

Published

Reusable backend orchestration helpers for Kognitive Cloud products

Readme

@kognitivedev/backend-cloud

Reusable backend orchestration helpers for Kognitive Cloud products.

This package contains provider-neutral Cloud Voice backend mechanics: session preparation, tool manifest generation, managed tool orchestration, phone session snapshots, and managed phone-control tools such as hang_up_call.

It intentionally does not import Twilio, Next.js, Drizzle, Clerk, or any apps/backend aliases. Applications compose those concrete dependencies.

Boundaries

  • @kognitivedev/backend-cloud owns Cloud Voice orchestration and interfaces.
  • @kognitivedev/telephony owns provider mechanics such as Twilio REST, TwiML, signatures, and media stream helpers.
  • apps/backend owns routes, auth, DB stores, trace/session persistence, environment loading, and concrete adapter registration.

Prepare a Session

import {
  createPhonePrepareSnapshot,
  prepareCloudVoiceSessionConfig,
} from "@kognitivedev/backend-cloud";

const prepare = prepareCloudVoiceSessionConfig(agentConfig, {
  agentName: agent.name,
  sessionId,
  resourceId: { userId },
  channel: "phone",
});

const snapshot = createPhonePrepareSnapshot({
  agent,
  channel: "phone",
  config: agentConfig,
  prepare,
});

Phone channels automatically receive the built-in hang_up_call manifest. Web, iframe, and script channels do not.

Execute Tools

executeCloudVoiceToolBinding is dependency-injected. It does not persist events or read databases.

const { result, metadata } = await executeCloudVoiceToolBinding({
  projectId,
  sessionId,
  tool,
  args,
  resourceId,
  executeWebSearch,
  executeCloudFlow,
  executeKnowledgeBase,
  executePlatformAction,
});

The app should persist voice.tool.started, voice.tool.completed, and voice.tool.failed events around this call.

Phone Control

Phone control is provider-neutral. The package defines the tool flow; provider packages implement the mechanics.

const result = await executeCloudVoicePhoneControlTool({
  toolId: "hang_up_call",
  provider: callLeg.provider,
  providerCallId: callLeg.providerCallId,
  args,
  adapters: [twilioPhoneControlAdapter],
});

To add another phone provider:

  1. Implement a provider adapter in @kognitivedev/telephony.
  2. Register that adapter from apps/backend.
  3. Keep Cloud Voice tool orchestration unchanged.