Instruct field missing from generate UI for cloned Qwen3-TTS profiles

Open Beginner friendly
#1,104 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Start in the generate box UI and trace the condition that controls the instruct textarea or slider for selected profiles. Compare the existing Qwen CustomVoice condition with cloned profiles using the "qwen" engine, then verify the field appears for both profile types and that generation still sends instruct through POST /generate.

Written by the indexing model from the issue text.

Description

The instruct parameter (natural-language delivery control) works correctly
via the API for Qwen3-TTS cloned profiles — I confirmed this by calling
POST /generate directly with "engine": "qwen" and an instruct string, and
it worked exactly as expected.

However, the generate box in the app only shows the instruct textarea/slider
when a Qwen CustomVoice profile is selected. It does not appear for cloned
profiles using the Qwen3-TTS engine, even though the backend fully supports
it for that engine too.

Steps to reproduce:

  1. Create a cloned voice profile using the Qwen3-TTS engine
  2. Select that profile in the generate box
  3. Notice there's no instruct/delivery-instructions field available

Expected: the instruct field should appear for any profile using the "qwen"
engine (both CustomVoice and cloned Qwen3-TTS), not just CustomVoice.

Workaround: calling POST /generate directly with "engine": "qwen" and an
instruct field works fine — this looks like a UI gating issue rather than
a backend limitation.

Dominant language
TypeScript
Stars
56.4k
Forks
7k
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 jamiepine/voicebox

All issues in jamiepine/voicebox

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.