Audio attachments look simple at the interface: attach a clip and ask a question. The routing decision behind that interaction is less simple. A model endpoint may accept text while rejecting audio, and even an audio-capable endpoint may expose a different wire format.
AIClaw 3.11.1 makes that decision from the selected model’s declared capability and service protocol. When native audio is unavailable or unknown, it uses the configured speech-to-text route instead of silently sending audio bytes to a text-only request.
The routing decision
The audio preparation code enables native input only when AudioInput is explicitly marked supported and the selected protocol is Chat Completions or Gemini. WAV and MP3 attachments can follow this path; other formats go through the transcription fallback.
That is a deliberately narrow claim. A provider being compatible with a protocol does not establish that every model or endpoint accepts audio. The capability setting needs to match the actual service.…