/refine failures

Describe the bug

Session Diagnosis

Root cause found. At  06:55:33Z , the  /refine  command failed with a 400 Bad Request:

"reasoning_effort "medium" was provided, but model gpt-4o-mini-2024-07-18 does not support reasoning effort"

What happened:

1.  /refine  internally invokes  gpt-4o-mini  (a lightweight utility model) to rewrite your prompt into    tags.
2. The request incorrectly included  reasoningEffort: "medium"  as a parameter.
3.  gpt-4o-mini-2024-07-18  doesn't support the  reasoning_effort  parameter at all (only reasoning-capable models like o1/o3 do) — Azure OpenAI rejected the call outright with  invalid_reasoning_effort .
4. The call failed in 545ms,  turn_failed  fired, and the CLI silently fell back to "Your text was left unchanged" instead of surfacing the real error.

This is a CLI-side bug, not an environment/proxy/auth issue: the refine feature is passing a reasoning-effort setting to a model that categorically rejects it. It's unrelated to the Blue Coat proxy or credentials — the request reached the API fine and got a clean structured rejection.

Affected version

1.0.83

Steps to reproduce the behavior

No response

Expected behavior

No response

Additional context

No response

从 /refine 命令开始，跟踪其对 gpt-4o-mini 的内部请求，重点关注 reasoningEffort 是如何添加的，以及 turn_failed 是如何处理的。完成的标准是请求不再发送不受支持的设置，并且显示实际的失败，而不是静默地报告文本未发生变化。