# Inaccurate Transcript Despite Correct Realtime Understanding

**URL:** <https://community.livekit.io/t/inaccurate-transcript-despite-correct-realtime-understanding/1829>\
**Category:** Agents\
**Tags:** agent-development, stt, realtime, agent-sdk-node-js, openai\
**Created:** [August 8, 2026, 10:04pm UTC](https://community.livekit.io/t/inaccurate-transcript-despite-correct-realtime-understanding/1829 "2026-08-08T22:04:56Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\
**Post date:** [August 24, 2026, 8:27am UTC](https://community.livekit.io/t/inaccurate-transcript-despite-correct-realtime-understanding/1829/21 "2026-08-24T08:27:59Z")

</div>

> [@royibernthal](#):
>
> Deepgram works for me in your test project, yet it still doesn’t work in mine, so I’m a bit confused.
> 
> Do you mind taking a look? Finding that difference might give us a clue as to why it’s not working in the main project either.

Looks like you are passing `deepgram/nova-3` as the model, but that is the model name for LiveKit Inference. For the deepgram plugin I would expect the model to be `nova-3`, [Deepgram STT | LiveKit Documentation](https://docs.livekit.io/agents/models/stt/deepgram/#nova-3-and-other-models)

---

<div class="post-metadata">

**Author:** ![royibernthal](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/royibernthal/32/2510_2.png) [@royibernthal](https://community.livekit.io/u/royibernthal)\
**Post date:** [August 27, 2026, 2:35pm UTC](https://community.livekit.io/t/inaccurate-transcript-despite-correct-realtime-understanding/1829/22 "2026-08-27T14:35:40Z")

</div>

Bingo, found the needle. 2 things left to address, let me know if it would make more sense to open separate threads for them:

1. Hebrew logging encoding/decoding

2. What’s the difference between what’s configured in `createAgent` (`AgentCreateOptions`) versus `AgentSession` (`AgentSessionOptions`)? Does the actual agent creation use a merged version of those configs? I imagine the former overrides the latter?

---

<div class="post-metadata">

**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\
**Post date:** [August 27, 2026, 3:44pm UTC](https://community.livekit.io/t/inaccurate-transcript-despite-correct-realtime-understanding/1829/23 "2026-08-27T15:44:19Z")

</div>

1. For Hebrew logging encoding / decoding, I think it would be best to create a new thread. This thread is a bit unmanageable now 🙂
2. AgentSession holds the session-wide defaults. You can have multiple agents within the session and any options you provide to the agent will override those defined in the AgentSession. For example, the agent can have a different STT provider. It’s not a total overlap however, you can’t override everything.

---

<div class="post-metadata">

**Author:** ![royibernthal](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/royibernthal/32/2510_2.png) [@royibernthal](https://community.livekit.io/u/royibernthal)\
**Post date:** [August 27, 2026, 3:48pm UTC](https://community.livekit.io/t/inaccurate-transcript-despite-correct-realtime-understanding/1829/24 "2026-08-27T15:48:14Z")

</div>

1. No problem, I’ll create a new one.
2. Got it, thanks for the answer 🙂

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/system/32/26_2.png) [@system](https://community.livekit.io/u/system)\
**Post date:** [August 29, 2026, 3:48pm UTC](https://community.livekit.io/t/inaccurate-transcript-despite-correct-realtime-understanding/1829/25 "2026-08-29T15:48:56Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.

[Previous page](https://community.livekit.io/t/inaccurate-transcript-despite-correct-realtime-understanding/1829.md?page=1)
