openclaw - 💡(How to fix) Fix Deepgram: add native `utterances` support alongside `smartFormat` [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#77919Fetched 2026-05-06 06:19:26
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
2
Author
Timeline (top)
commented ×1

Root Cause

Zero-cost. Deepgram already returns utterances — it is simply discarded because the parameter is never passed. Unlocks agent cognition, voice analytics, and accessibility tooling.

Code Example

// buildDeepgramCompatQuery
if (typeof options.utterances === "boolean") query.utterances = options.utterances;

// normalizeDeepgramQueryKeys  
if ("utterances" in normalized) {
    // already snake_case, no rename needed
}

---

{ "providerOptions": { "deepgram": { "utterances": true } } }
RAW_BUFFERClick to expand / collapse

Problem

OpenClaw Deepgram integration supports smartFormat via providerOptions.deepgram.smartFormat, but there is no way to enable Deepgram utterances feature.

What utterances provides: Each audio is segmented into semantically meaningful units with per-word timestamps and confidence scores. Critical for:

  • Communication style profiles (confidence patterns, speech density, reformulation detection)
  • Companion/agent cognition systems
  • Downstream NLP needing temporal alignment

Current state

smartFormat already supported in compat layer (buildDeepgramCompatQuery + normalizeDeepgramQueryKeys). Adding utterances follows the exact same pattern.

Proposed change (2 lines)

// buildDeepgramCompatQuery
if (typeof options.utterances === "boolean") query.utterances = options.utterances;

// normalizeDeepgramQueryKeys  
if ("utterances" in normalized) {
    // already snake_case, no rename needed
}

Config:

{ "providerOptions": { "deepgram": { "utterances": true } } }

Impact

Zero-cost. Deepgram already returns utterances — it is simply discarded because the parameter is never passed. Unlocks agent cognition, voice analytics, and accessibility tooling.

Ref: https://developers.deepgram.com/docs/utterances

extent analysis

TL;DR

Enable the Deepgram utterances feature by adding a boolean utterances option to the providerOptions.deepgram configuration.

Guidance

  • Add the utterances option to the buildDeepgramCompatQuery function to include it in the query.
  • Update the normalizeDeepgramQueryKeys function to handle the utterances key.
  • Configure the utterances option to true in the providerOptions.deepgram configuration to enable the feature.
  • Verify that the utterances data is being returned and processed correctly by checking the response from the Deepgram API.

Example

// buildDeepgramCompatQuery
if (typeof options.utterances === "boolean") query.utterances = options.utterances;

// normalizeDeepgramQueryKeys  
if ("utterances" in normalized) {
    // already snake_case, no rename needed
}

Notes

The proposed change has zero cost and simply unlocks existing functionality provided by the Deepgram API.

Recommendation

Apply the proposed change to enable the utterances feature, as it provides valuable functionality for communication style profiles, companion/agent cognition systems, and downstream NLP tasks.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Deepgram: add native `utterances` support alongside `smartFormat` [1 comments, 2 participants]