Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Provider API rejects audio/video content parts for multimodal models

Open
#906 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Domain
ai, api

Research direction

Start at the POST /provider/v1/chat/completions entry point and review the provider documentation describing accepted content parts. Confirm how input_audio and video_url data URLs are validated for the named models, then verify that valid audio and video requests are accepted without breaking existing text and image handling.

Written by the indexing model from the issue text.

Description

Feature Description

I’m trying to call these models through the Provider API:

meta/muse-spark-1.3-contributor
Qwen/Qwen3.8-Omni-Flash
using POST https://api.commandcode.ai/provider/v1/chat/completions.

I need to submit:

an MP3 as input_audio
an MP4 as video_url with a Base64 data URL
Both models return:

{
"error": {
"message": "Invalid input",
"type": "invalid_request_error",
"param": "messages.1.content"
}
}
Your provider documentation says “Text and images. Audio, file, and document parts are rejected by the schema,” but Qwen 3.8 Omni Flash is advertised as omni-modal and supports audio/video through its native OpenAI-compatible API.

Use Case

In the case of Qwen 3.8 Omni Flash, media understanding is its main feature. To not support media input would be an oversight. While the Command Code harness itself may not support media, there are a lot of applications that can.

Additional Context

No response

How important is this to you?

Important for my workflow

Dominant language
No language data
Stars
4k
Forks
350
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CommandCodeAI/command-code

All issues in CommandCodeAI/command-code

Similar issues

More AI Infra & Agents issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.