Pinecall

@pinecall/voice-core

Framework-agnostic WebRTC voice session client. Zero dependencies.

npm install @pinecall/voice-core

Zero runtime dependencies. Browser-only (requires RTCPeerConnection and getUserMedia).

What it does#

voice-core is what the browser uses to talk to a Pinecall agent over WebRTC. It:

  • Fetches a short-lived token from your backend (or the voice server, in convenience mode)
  • Requests microphone access via getUserMedia
  • Opens a peer connection to voice.pinecall.io
  • Exposes the conversation as a reactive state object + an event stream

It does not render UI. For a drop-in React widget with an animated orb, use @pinecall/voice-widget (which is built on top of voice-core).

Quick start#

import { VoiceSession } from "@pinecall/voice-core";

const session = new VoiceSession({ agent: "mara" });

session.addEventListener("message", (e) => {
  console.log(`${e.detail.message.role}: ${e.detail.message.text}`);
});

await session.connect();

// later
session.disconnect();

That's it. The session manages the connection lifecycle, mic, and transcript. You get a stream of structured events you can wire into any UI.

How it fits with the other packages#

Browser                                  Server
─────────                                ──────
@pinecall/voice-widget   (React UI)
       │
@pinecall/voice-core     (WebRTC + state) ─────► voice.pinecall.io ─────► @pinecall/sdk (your Node.js)
                                                                                │
                                                                            agent.on(...)
                                                                            call.say(...)
  • You write: agent logic in Node.js with @pinecall/sdk
  • You drop in: voice-core (or voice-widget) in the browser
  • The voice server: handles the audio pipeline (STT, LLM, TTS, VAD) and forwards events both ways

Two interfaces: state + events#

voice-core exposes the session two ways. Use whichever fits your framework:

StyleAPIBest for
Reactive statesession.subscribe(cb) + session.getState()React's useSyncExternalStore, Vue's ref, Svelte stores
Event listenerssession.addEventListener("message" | "phase" | "event" | ...)Vanilla JS, imperative code, observability

You can mix them in the same app — they share the same underlying state machine.

What's next#