AIToday
Large Language ModelsAudio & SpeechZenn AI/MLPublished: Oct 5, 2026, 22:00 JST

Kikuren swaps to gpt-live-1, ends backchannel stopping

Kikuren swaps to gpt-live-1, ends backchannel stopping

3 Key Points

  1. What happened

    After GPT-Live (gpt-live-1) GA'd on September 10, 2026, the Kikuren developer swapped out gpt-realtime-2.1, and the AI stopped halting every time the user said 'uh-huh,' so the workaround code became unnecessary.

  2. Why it matters

    This reading is inferred, as the body reports the author's impression rather than a formal finding.

  3. What to watch

    The upside rests on one session of testing, and the prompt rules still had to stay as they were, so whether the gains hold across other voices and scenes is likely to depend on more sessions. Watch whether turn-splitting thresholds tuned on one person's logs transfer.

WHO IT HITSBuilders and product owners of Japanese-language voice AI that role-plays a conversation partner — for practice, training, or evaluation — face a near-rewrite to adopt GPT-Live, since turn detection, transcription, and speech events are no longer provided by the API and must be rebuilt.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

Kikuren is a practice app where a manager speaks as the manager and an AI plays a subordinate with a concern. The design goal was unusual: the AI should not answer the moment the user goes quiet. Instead, it should say more when the user nods and waits, and less when rushed. That made the backchannel problem central, because under gpt-realtime-2.1 every 'uh-huh' from the user cut the AI off, turning the exchange into a strict turn-taking loop.

The article traces two other problems from that era: the AI would reveal a deeper confession instead of continuing after an interruption, and noise alone could make the AI speak with nobody talking. Both were handled with workarounds — truncating conversation history server-side on each interruption, and waiting for transcription before sending response.create. After switching, the author removed both and rechecked continuation after an interruption, reaction to noise, and interruption during thinking, in a setting with music playing nearby and the AI's voice potentially looping back into the mic. No problems appeared, though only one session was checked.

The migration was closer to a rebuild. Turn detection settings, transcription settings, and speech start/end events are gone, so speaking indicators and turn boundaries had to be reconstructed from audio amplitude and fragment timing. The author tuned a 3,000 ms gap threshold, then added a lower bound requiring a 900 ms silence with overlapping speech, based on 12 sessions of logs. Both values came from one person's small sample, so they are expected to shift for other voices. The prompt rules were expected to shrink but did not; removing them all made the AI sound too polished, and the author could not justify removing any single rule. The remaining open issue is that the AI still discloses too much when the user listens poorly or only nods, which the author does not expect a model swap alone to solve. The practical payoff for similar teams will hinge on whether the backchannel fix holds for other voices and scenarios, and on whether the rebuild cost is worth it.

FAQ
Did switching to GPT-Live make the voice AI cheaper?
Not dramatically. GPT-Live bills at $0.05 per minute; the earlier API cost about $0.41 to $5.03 for a 10-minute practice, while GPT-Live came to $0.50. The draw is that the rate no longer varies with prompt length or cache hits.
Could the developer shorten the prompt rules after moving to GPT-Live?
No. All 1,038 characters of turn-taking rules stayed. With all rules removed, the AI spoke longer and more smoothly from the start; restoring the length and hesitation rules brought the longest turn down from 175 to 121 characters and lifted hesitations from 8.3 to 15.4 per thousand characters.
What did Japanese language support look like on GPT-Live?
OpenAI did not state Japanese support and only added English and Brazilian Portuguese voices. But specifying the old cedar voice still produced natural Japanese, and short backchannels that used to turn into Mhm. or 음. stayed in Japanese.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleStrata runs 125B Qwen3.8-Flash-Next on gaming PCs