Twilio ConversationRelay phone channel for Eve — early standalone library

[Jorybraun]

We built phone conversations for PIPEY and extracted the transport into a small MIT library that other Eve apps can use:

eve-conversation-relay

Twilio ConversationRelay handles speech recognition and synthesis. The adapter sends recognized text into your Eve agent and streams its replies back to the caller. Your app supplies the agent, model, tools, memory and access policy.

Included:

• A ready-made incoming-call channel with signed HTTP and WebSocket routes.
• Streaming replies, interruption handling and durable one-connection call claims.
• A complete standalone helpdesk starter with a SQLite call store.
• A lower-level adapter for apps with their own outgoing-call workflow.

The recommended starter uses Eve 0.70.1 and Node 24+. The package is an early preview: independent installation, build and signed localhost protocol checks pass; live-call validation of the standalone starter is still pending. npm publication is also pending, so use the tarball in GitHub Releases.

This uses Eve as a package through its public custom-channel API. No Eve fork is needed. It supports Twilio's managed STT/TTS choices; it is not a general raw-audio SDK.

Related to the native voice discussion in #637. I'd love feedback on the channel API, the starter, and what would make this useful in your own Eve app.

[IObert]

I love it!

[vasanthsreeram]

One use case for the lower-level adapter is a coding agent waiting on its owner to name a toy project: Cedar or Pine. Your README says hangup closes transport reading while an accepted Eve turn can continue. I would test interruption followed by hangup, and have the host distinguish a captured explicit choice from a finished call or queued turn. No captured choice leaves the task unresolved.

The fresh per-call Eve address and durable one-connection claim are useful boundaries. Persist the question/request identity separately from call identity, so a later call answering another question cannot satisfy the first one. The app still owns authorized-decision-maker checks. I have read the announcement and README; I have not installed the library or made a live call with it.

Disclosure: I build JustCallMe, a hosted phone channel for these owner questions. Would you be open to comparing one harmless Cedar/Pine checkpoint in a disposable Claude Code/Codex session? I can help with your own-phone verification and private scoped-key skill setup. Eve/relay pairing is unimplemented and untested; the comparison would cover only the standalone question/answer experience. Keep phone numbers, codes, keys and real task details private.