Topic
Latency
Where the seconds in a spoken turn actually go.
7 posts
- The first 300 milliseconds of an agent turnYou cannot make the model faster from the client. Almost all of the felt wait is decided before the model has said anything, and that part is yours.Render spec10 min
- Where the seconds go in an in-app agent turnWe measured a slow turn end to end. Most of the time was not in our code and not in the model, which changes what is worth optimising.Tools and MCP10 min
- MCP for in-app agents: connecting your tools to a modelThe Model Context Protocol replaces one connector per backend with one protocol. What it is, how a tool call actually happens, and what it costs on the first turn.Tools and MCP10 min
- What barge-in really costs, and how we pay for itServer-side turn detection decides when an agent should stop talking. The client decides whether it actually does, and that is where it breaks.Voice11 min
- Designing an agent conversation people can actually useThe seven decisions that make or break a conversational feature: discoverability, endpointing, barge-in, errors, confirmation, latency and the visual answer.Voice11 min
- How fast does a voice agent have to be? A latency playbookWhere a spoken turn's milliseconds go, what the turn-taking research actually measured, and which tactics shorten which segment of the budget.Voice9 min
- Build vs buy: what an in-app agent really costs to ownWiring a speech API to a model takes an afternoon. The nine workstreams that turn it into something you can hand to a user do not have an end date.Business10 min