langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 12:36:14 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Missing Audio configuration in the app configuration UI #15139

New Issue
Closed
opened 2026-02-21 19:20:22 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 19:20:22 -05:00
Owner
Copy Link
Copy Source

Originally created by @marcelodiaz558 on GitHub (Jul 5, 2025).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Problem Description

Currently, when creating an Agent application, users can only configure two file upload options in the app settings:

  • Vision (for image uploads)
  • Document (for document uploads)

However, there is no Audio configuration option available, even when the selected model supports audio input processing. This limitation prevents users from creating agents that can accept audio file uploads, such as for transcription, analysis, or other audio-processing workflows.

Current Behavior

  • App configuration UI only shows Vision and Document toggles
  • Audio file uploads are rejected with error messages like "File extension not supported audio/wav"
  • Users cannot enable audio uploads through the UI, even with audio-capable models

Expected Behavior

  • An Audio configuration toggle should be available in the app settings
  • When enabled, it should allow users to upload audio files (MP3, WAV, M4A, etc.)
  • The setting should appear below the existing Vision and Document options
  • It should only be visible when the selected model supports audio processing

Use Cases

  • Creating agents with speech-to-text capabilities
  • Audio analysis and transcription workflows
  • Multi-modal applications that combine text, images, and audio

Proposed Solution

Add an Audio configuration component similar to the existing Vision and Document components, that:

  1. Shows only when the model supports audio features
  2. Allows users to toggle audio file upload capability
  3. Integrates with the existing file upload system
  4. Supports standard audio formats (MP3, WAV, M4A, AMR, MPGA)

Additional Context

The backend system already supports audio file types and processing, but the frontend configuration UI lacks the option to enable this functionality for end users.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @marcelodiaz558 on GitHub (Jul 5, 2025). ### Self Checks - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. ### Problem Description Currently, when creating an Agent application, users can only configure two file upload options in the app settings: - **Vision** (for image uploads) - **Document** (for document uploads) However, there is no **Audio** configuration option available, even when the selected model supports audio input processing. This limitation prevents users from creating agents that can accept audio file uploads, such as for transcription, analysis, or other audio-processing workflows. ### Current Behavior - App configuration UI only shows Vision and Document toggles - Audio file uploads are rejected with error messages like "File extension not supported audio/wav" - Users cannot enable audio uploads through the UI, even with audio-capable models ### Expected Behavior - An **Audio** configuration toggle should be available in the app settings - When enabled, it should allow users to upload audio files (MP3, WAV, M4A, etc.) - The setting should appear below the existing Vision and Document options - It should only be visible when the selected model supports audio processing ### Use Cases - Creating agents with speech-to-text capabilities - Audio analysis and transcription workflows - Multi-modal applications that combine text, images, and audio ### Proposed Solution Add an Audio configuration component similar to the existing Vision and Document components, that: 1. Shows only when the model supports audio features 2. Allows users to toggle audio file upload capability 3. Integrates with the existing file upload system 4. Supports standard audio formats (MP3, WAV, M4A, AMR, MPGA) ### Additional Context The backend system already supports audio file types and processing, but the frontend configuration UI lacks the option to enable this functionality for end users. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 19:20:22 -05:00
yindo closed this issue 2026-02-21 19:20:22 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#15139
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?