← Back to Opportunity Radar
GUIDED VALIDATION BRIEF

[Bug]: `qwen3.5-35b-a3b` with a `structured_model` raise `openai.BadRequestError`

Evidence observed in agentscope-ai/agentscope, a General AI project.

11 comments0 positive reactions186 days openProject Radar 92
Start free validation sprint4 guided steps · private notes · cloud sync
DEMAND CONFIDENCE

REPEATED ACROSS 10 PROJECTS

Related friction appears in 10 independent repositories. This is stronger than one backlog item, but still requires direct user validation.

Project strength and demand confidence are measured separately.
SOURCE EVIDENCE

Start with what users actually said

Reporter context: Describe the bug By calling an agent in the following common pattern with a : When the is set to , a conflict about thinking mode and tool choice emerges: To Reproduce Design any and pass it to a vanilla agent, whose model should be set to . Expected behavior The parameter can be used with without throwing exceptions.…Excerpted from the public Issue. Read the complete thread before interpreting it.

Read original GitHub Issue ↗
GENERAL AI VALIDATION LENS

Recruit: Recruit people who can show a recent, concrete example of the problem.

Guardrail: Measure behavior in the real workflow and keep a human review step for consequential actions.

01 · Provider interoperability

Write the problem hypothesis

For [operator], the workflow fails during [condition], forcing [recovery work] and costing [time, money or trust].

You can name one user, one situation and one measurable consequence without proposing a feature.
02 · EVIDENCE INTERVIEW

Interview five people affected by this workflow

  • Show me the last failure and its logs.
  • What triggered it and how often does it recur?
  • How do you detect it today?
  • What does recovery require?
  • What would a safe failure look like?
At least three people independently describe the same painful workflow with recent examples.
03 · MINIMUM TEST

Run the smallest experiment

Add one narrow guardrail, retry or recovery path around the failing step. Replay three real failure cases and compare recovery time.

The same failure is recovered faster in three real cases without creating a new incident.Measure behavior in the real workflow and keep a human review step for consequential actions.
04 · DECISION GATE

Make a build decision

  • Build: repeated pain and active commitment
  • Narrow: pain is real but the audience or job differs
  • Stop: weak frequency or no behavioral proof
Do not let GitHub engagement replace direct validation.

Why this brief exists

Information has value only when it changes action. This page turns one public signal into a bounded validation exercise. It is a research aid, not proof of demand, investment advice or a product recommendation.