[Bug]: STT feature (provided by groq) does not work at all.

[hightman]

OpenACP Version

2026.403.3

Messaging Platform

Telegram

AI Agent

opencode

Bug Description

I’ve confirmed that STT is configured correctly, but when I send a voice message via Telegram, it isn’t converted into text and forwarded to the agent.

Here are your current settings snapshot:

- Default agent: opencode
- Workspace base: ~/
- Run mode: daemon (auto-start: on)
- API: 127.0.0.1:21420
- Security: session timeout 60 min, max concurrent sessions 20
- STT: provider groq (configured)
- TTS: not configured
- Logging: level info, retention 30 days

I checked the logs and found that the message-transformer was not triggered. Instead, a custom Python 3 script called tools such as Whisper for conversion, and in the end it reported that the conversion failed.

I still can’t transcribe .wav audio directly in this environment.

If you want, run this locally and paste the text here, then I’ll summarize/respond immediately:

Steps to Reproduce

1. Start openacp
2. Send a voice message to a session via Telegram.

Expected Behavior

Trigger the message-transformer to convert the voice message into text, and then pass it to backend agentopencode.

Logs / Error Output

Configuration

# config.json
  "speech": {
    "stt": {
      "provider": "groq",
      "providers": {
        "groq": {
          "apiKey": "gsk_..."
        }
      }
    },
    "tts": {
      "provider": null,
      "providers": {}
    }
  }

# @openacp/speech/settings.json 
{
  "sttProvider": "groq"
}

Operating System

ubuntu 22.04

Node.js Version

v24.14.0

Additional Context

No response

[hightman]

After reviewing and comparing the source code, I found that it’s a configuration issue—adding groqApiKey in settings.json should fix it. @0xmrpeter

This project is great, with features evolving rapidly, but the documentation is struggling to keep up.