← Back to parent livestream

Segment 25: Boris Starkov (ElevenLabs): speech engines, turn taking, and conversational voice agents

AI Engineer10h 9mTranscript ✅Added May 29, 12:54 am GMT+8

  • Timestamp: 07:55:31
  • Duration: 11m 58s
  • Livestream range: 07:55:31 → 08:07:29
  • Transcript evidence: 22 chunks, about 1729 words

Actionable Insights

  1. Turn speech engines into an operating checklist. Turn the speaker’s idea into a concrete workflow: define the user, the input, the tool boundary, the review step, and the failure condition.
  2. Separate capability from accountability. The recurring lesson in this chapter is that more capable AI changes who does the work, but not who owns the outcome. When applying it to voice and relationship AI, write down what the system may do autonomously and what still requires explicit human judgment.
  3. Instrument the loop before scaling it. The useful operating loop is: capture context, let the tool act, review the result, preserve the learning, and tighten the next run. Write down acceptance criteria and review notes early so the workflow can be audited later.
  4. Design for the failure mode, not the demo. The polished demo version of speech engines, turn taking, and conversational voice agents is less important than the places it breaks: weak context, unsafe permissions, weak evaluation, unclear ownership, latency, or poor human review.
  5. Convert this into a personal/relationship agents checklist. The durable takeaway from Boris Starkov (ElevenLabs) is to turn “speech engines, turn taking, and conversational voice agents” into explicit operating rules: what the system may do, what it must prove, what evidence a reviewer needs, and where a human must stay accountable. The next useful artifact is a short checklist or eval case that someone can actually run.

What they actually use/show that is worth copying

  • NanoClaw as the agent platform: NanoClaw is valuable here because it is understandable and containable. The user can inspect the short codebase and reason about the safety boundary instead of treating the assistant as magic.
  • email/calendar/call-note connectors: This is a concrete mechanism from the talk. The useful question is whether it reduces friction, improves reliability, or makes human review easier in a real workflow.
  • ChatGPT / AGI builder stack: The valuable part is preserving editability and taste. The tool is useful when it keeps design intent alive instead of producing generic one-shot output.
  • Exa search primitive: The agent is embedded in the existing delivery workflow. That makes review, testing, and handoff happen where the team already works.
  • GroqCloud low-latency inference: The key idea is persistent, inspectable context. The workflow becomes more valuable when knowledge survives beyond one chat and humans can browse or correct it.
  • ElevenLabs speech/turn-taking stack: This is a concrete mechanism from the talk. The useful question is whether it reduces friction, improves reliability, or makes human review easier in a real workflow.
  • Prime Intellect memory / recursive models: The agent is embedded in the existing delivery workflow. That makes review, testing, and handoff happen where the team already works.

Core thesis

Boris Starkov (ElevenLabs) uses this chapter to make a specific argument about speech engines, turn taking, and conversational voice agents. The useful pattern is not just the named product or institution; it is how the segment exposes the new operating model for voice and relationship AI: humans keep taste, accountability, and deployment judgment while agents or models absorb more of the execution loop.

The chapter starts from this evidence: “Take coding agents for example. uh most if not all of them actually have some sort of use voice mode uh button.” That opening matters because it frames the segment as a concrete slice of the broader AIE Singapore Day 1 theme: agentic systems are moving from novelty demos into production workflows, institutions, creative tools, infrastructure, and embodied systems. The analysis should therefore be read as a nested talk-level packet, not as a generic summary of the entire livestream.

Comment insights

The extracted YouTube comments do not provide reliable speaker-specific audience reactions for Boris Starkov (ElevenLabs). So this section should not pretend there is detailed sentiment about the talk. The useful audience-facing read is instead content-based: this segment is valuable for viewers who care about speech engines, turn taking, and conversational voice agents, especially the concrete implementation choices and operating constraints called out in the transcript.

Deep research

The research value of this talk is the practical architecture behind speech engines, turn taking, and conversational voice agents. Boris Starkov (ElevenLabs) is not only making a broad claim; the useful details are the concrete mechanisms named in the transcript: NanoClaw as the agent platform, email/calendar/call-note connectors, ChatGPT / AGI builder stack, Exa search primitive, GroqCloud low-latency inference, ElevenLabs speech/turn-taking stack.

The main question to take away is how those mechanisms change the workflow. What becomes cheaper, what needs a stronger checkpoint, and what must remain human-owned? For this talk, the strongest evidence is in the speaker’s examples rather than in generic AI optimism. Use the named tools and operating choices as the starting point for further research, then validate whether the same pattern fits your own environment, security constraints, and evaluation loop.

Verdict

  • The talk contains a specific operating lesson about speech engines, turn taking, and conversational voice agents: Agree. The speaker gives enough segment-level evidence to extract concrete implications rather than treating it as generic conference commentary.
  • The named tools/examples should be copied blindly: Disagree. They are useful design references, but each needs to be checked against local security, data, latency, cost, and human-review requirements.
  • The most valuable part is the concrete workflow detail: Agree. The strongest takeaways are the mechanisms, constraints, and examples the speaker actually names.
  • The implementation details are transcript-supported: Agree. This page cites details such as NanoClaw as the agent platform, email/calendar/call-note connectors, ChatGPT / AGI builder stack, Exa search primitive.
  • Human accountability disappears when agents improve: Disagree. The recurring production pattern is to move execution into tools while keeping ownership, review, and failure handling explicit.

Screen-level insights

  • 7:56:32 — opening frame: Boris Starkov (ElevenLabs) frames the talk around speech engines, turn taking, and conversational voice agents, with the useful setup being: “sure this is a voice input and this is a voice output but this is not conversational. And today I want to talk about how to improve this uh architecture to make it feel much more like a natural humanto human uh conversation.”
  • 8:04:48 — NanoClaw as the agent platform: The talk shows or names this as part of the actual workflow. The relevant evidence is: “product that we we have. We didn’t publicly announce it yet. It’s uh we’re going to start testing it starting next week.”
  • 7:58:36 — email/calendar/call-note connectors: The talk shows or names this as part of the actual workflow. The relevant evidence is: “here we trained another model again a very smart uh turn detector model that takes into account not only voice activity but also the actual context of what’s been said before to predict whether this is the end of the sentence or uh the speaker the user is goin…”
  • 8:03:15 — ChatGPT / AGI builder stack: The talk shows or names this as part of the actual workflow. The relevant evidence is: “part of uh making your turnpaced model feel truly conversational is handling interruptions, letting the user interrupt the model. That comes with a with a lot a lot a lot of uh different um corner cases, horistics, etc.”
  • 8:06:02 — Exa search primitive: The talk shows or names this as part of the actual workflow. The relevant evidence is: “Thank you so much. Next up, we have Jackman from Prime Intellect. He’s a founding research engineer. Jackman, you can set up. Um, and he’ll be talking about continual learning for longunning agents, agents that keep getting better.”
  • 8:04:48 — closing implication: The later part of the talk turns the idea into a practical takeaway: “product that we we have. We didn’t publicly announce it yet. It’s uh we’re going to start testing it starting next week.”

Verification notes

Verified against the extracted transcript for Boris Starkov (ElevenLabs)’s talk on speech engines, turn taking, and conversational voice agents. The supported claims in this page are based on concrete tools/artifacts named in the talk: NanoClaw as the agent platform, email/calendar/call-note connectors, ChatGPT / AGI builder stack, Exa search primitive, GroqCloud low-latency inference, ElevenLabs speech/turn-taking stack, Prime Intellect memory / recursive models. I treated auto-caption wording cautiously, kept only details that are explicitly present in the segment transcript, and avoided importing claims from adjacent speakers or from the overall conference description.