HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
livekit
eot-bench
Python2026–2026
livekit / eot-bench

eot-bench

LiveKit End-of-Turn Benchmark

2Distinct people
2Mentions
0Explicit recommenders
73GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

LiveKit End-of-Turn Benchmark

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week2 dated mentions

Observed mentions: 2026-06-18 17:14:14 UTC to 2026-10-21 12:08:34 UTC. Weeks start Monday, UTC.

012026-06-15 00:00:00 UTC to 2026-06-22 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJun 152026-06-22 00:00:00 UTC to 2026-06-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-29 00:00:00 UTC to 2026-07-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-06 00:00:00 UTC to 2026-07-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-13 00:00:00 UTC to 2026-07-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-20 00:00:00 UTC to 2026-07-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-27 00:00:00 UTC to 2026-08-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-03 00:00:00 UTC to 2026-08-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-10 00:00:00 UTC to 2026-08-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-17 00:00:00 UTC to 2026-08-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 172026-08-24 00:00:00 UTC to 2026-08-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-31 00:00:00 UTC to 2026-09-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-07 00:00:00 UTC to 2026-09-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-14 00:00:00 UTC to 2026-09-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-21 00:00:00 UTC to 2026-09-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-28 00:00:00 UTC to 2026-10-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-05 00:00:00 UTC to 2026-10-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-12 00:00:00 UTC to 2026-10-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-19 00:00:00 UTC to 2026-10-26 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 19

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jun 152026-06-15 00:00:00 UTC2026-06-22 00:00:00 UTC110
Jun 222026-06-22 00:00:00 UTC2026-06-29 00:00:00 UTC000
Jun 292026-06-29 00:00:00 UTC2026-07-06 00:00:00 UTC000
Jul 62026-07-06 00:00:00 UTC2026-07-13 00:00:00 UTC000
Jul 132026-07-13 00:00:00 UTC2026-07-20 00:00:00 UTC000
Jul 202026-07-20 00:00:00 UTC2026-07-27 00:00:00 UTC000
Jul 272026-07-27 00:00:00 UTC2026-08-03 00:00:00 UTC000
Aug 32026-08-03 00:00:00 UTC2026-08-10 00:00:00 UTC000
Aug 102026-08-10 00:00:00 UTC2026-08-17 00:00:00 UTC000
Aug 172026-08-17 00:00:00 UTC2026-08-24 00:00:00 UTC000
Aug 242026-08-24 00:00:00 UTC2026-08-31 00:00:00 UTC000
Aug 312026-08-31 00:00:00 UTC2026-09-07 00:00:00 UTC000
Sep 72026-09-07 00:00:00 UTC2026-09-14 00:00:00 UTC000
Sep 142026-09-14 00:00:00 UTC2026-09-21 00:00:00 UTC000
Sep 212026-09-21 00:00:00 UTC2026-09-28 00:00:00 UTC000
Sep 282026-09-28 00:00:00 UTC2026-10-05 00:00:00 UTC000
Oct 52026-10-05 00:00:00 UTC2026-10-12 00:00:00 UTC000
Oct 122026-10-12 00:00:00 UTC2026-10-19 00:00:00 UTC000
Oct 192026-10-19 00:00:00 UTC2026-10-26 00:00:00 UTC101

What Hacker News says

2 sources
Hi HN, I’m Kajo, co-founder of KugelAudio (YC P26). We build voice models focusing on customer support. One of the main issues our customers are having right now is calls that drift into endless spelling loops and lots of false interruptions, especially in non-English languages. A classic example would be the name “Philipp” or “Philip”. The customer says their name on the phone and the bot either doesn't know about the ambiguity or lets users spell everything letter by letter, which is extremely annoying and prone to error or interruption mid-spelling. This is why we built Kugel Ear. When it isn't sure, it returns other spellings with probabilities, so the bot can ask one targeted question: “Philipp with two P’s?” Kugel Ear also comes with integrated context-aware EOT (end-of-turn) detection so the voicebot knows the user is mid-spelling
Read the rest
and doesn't interrupt. We score 1st on LiveKit EOT bench, 1st on AppTek’s call-center dialogues, 1st on calls over phone lines, and 2nd on VoiceCodeBench behind OpenAI, with a median latency of 72 ms from end of speech to final transcript. We don’t win everything: on Earnings22 (long earnings calls) ElevenLabs Scribe beats us (4.0% vs 4.4% WER), and on VoiceCodeBench OpenAI writes code and numbers slightly more accurately (83.1% vs 81.9%). False cut-off rate (pauses taken as end of turn at 300 ms average wait, lower is better, next best = best published model): German: 5.9% (next best: 11.8%) Spanish: 3.8% (next best: 15.5%) French: 5.0% (next best: 12.7%) Italian: 5.8% (next best: 16.9%) Dutch: 4.7% (next best: 12.5%) Portuguese: 5.6% (next best: 19.3%) English: 7.4% (next best: 9.9%) It costs €0.48 per audio hour (about $0.55). You can try it out at https://kugelaudio.com/kugel-ear-1 I’d love to hear where it breaks for you, especially calls where it still cuts someone off or misses a spelling. I’ll be in the thread all day answering questions. Datasets: - Support calls: 280 turns from AppTek’s call-center dialogues, 20 per accent across 14 accents, median WER. https://huggingface.co/datasets/apptek-com/apptek_callcenter... - Phone line: the same 280 turns through a simulated G.711 line (8 kHz, mu-law, noise, dropouts). - German names/addresses: 800 synthetic German calls we generated, half through the same phone line. - Codes and numbers: VoiceCodeBench, scored with deterministic exact match instead of its LLM verifier. https://huggingface.co/datasets/besimple-ai/voice-code-bench - Earnings22: Artificial Analysis’ cleaned version. https://huggingface.co/datasets/ArtificialAnalysis/Earnings2... - End of turn: LiveKit’s eot-bench. https://github.com/livekit/eot-bench and https://huggingface.co/datasets/livekit/eot-bench-data
In KugelAudio (YC P26) – Voice models that don't get stuck in spelling loops

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.