gpt-6-astra agents with actions fail: Azure Chat Completions rejects function tools at every reasoning effort
维护者通常 1 天内回复
@paullizer 已经在做这个了。
开始于 2026年10月2日。
评估
这个 Issue 还没有评估数据。
描述
Issue
Local (Semantic Kernel) agents with actions fail on gpt-6-astra. SimpleChat sends agent tool calls through Chat Completions, and Azure rejects function tools for this model on Chat Completions at every reasoning effort the model accepts. Any agent or scheduled workflow that uses actions with a gpt-6-astra deployment fails with a 400 before it does any work.
gpt-6-sol has the same rule as GPT-5.6: tools work on Chat Completions only with reasoning_effort: none. gpt-6-sol isn't in the model catalog, so SimpleChat doesn't apply the existing toolReasoningEfforts rule, and a gpt-6-sol agent with actions fails unless its Reasoning Effort is explicitly set to None.
Observed on a SimpleChat POC deployment running the React V2 branch (0.261.219) with Azure OpenAI deployments gpt-6-astra (2026-09-03) and gpt-6-sol (2026-09-22). The model endpoint uses api-version 2024-05-01-preview.
Steps to Reproduce
- Deploy
gpt-6-astrain Azure OpenAI and add it to a model endpoint. - Create a local agent on
gpt-6-astrawith at least one action (for example, the SimpleChat action). - Chat with the agent, or run a workflow that uses it.
- Set the agent's Reasoning Effort to None and repeat.
Expected Behavior
The agent runs through an API that supports tools for this model. If that isn't possible, SimpleChat blocks the configuration up front with a clear message that this model can't use actions through Chat Completions.
Actual Behavior
| Model | Reasoning effort | Result |
|---|---|---|
gpt-6-astra |
Not set (model default) | 400: Function tools with reasoning_effort are not supported for gpt-6-astra in /v1/chat/completions. To use function tools, use /v1/responses or set reasoning_effort to 'none'. |
gpt-6-astra |
low |
400: same Function tools with reasoning_effort are not supported for gpt-6-astra error |
gpt-6-astra |
none |
400: Unsupported value: 'reasoning_effort' does not support 'none' with this model. Supported values are: 'low', 'medium', 'high', and 'xhigh'. |
gpt-6-sol |
Not set (model default) | 400: Function tools with reasoning_effort are not supported for gpt-6-sol in /v1/chat/completions. To use function tools, use /v1/responses or set reasoning_effort to 'none'. |
gpt-6-sol |
none |
Works |
In a workflow, the run shows only the generic task error (The task could not complete. Review its input, model availability, and run activity.). The provider error appears only in Application Insights.
Impact
gpt-6-astracan't be used for any agent with actions, including scheduled workflows.gpt-6-solagents with actions fail unless the admin knows to set Reasoning Effort to None.- The cause isn't visible to the user or admin who sees the failure.
Notes
- Local agents always use Chat Completions (
AzureChatCompletioninsemantic_kernel_loader.pyandfunctions_model_endpoint_runtime.py). The Responses API is used only for Foundry agents and image generation. - The documentation doesn't describe this rule for GPT-6. Azure's model table lists Chat Completions and "Functions, tools, and parallel tool calling" for
gpt-6-astraandgpt-6-sol, without the GPT-5.6 note that tools on Chat Completions requirereasoning_effort: none. OpenAI'sgpt-6-astrapage lists reasoning efforts low, medium, high, xhigh and max, with no none, which matches the rejection above. - The errors name
/v1/chat/completionsand give the fix (/v1/responsesornone), so this looks like a model-level rule rather than an effect of the older api-version. A newer api-version wasn't tested. - A model catalog update on the React V2 branch (0.261.220) records
gpt-6-astra's verified token limits, its reasoning efforts, and this restriction as notes. The currenttoolReasoningEffortsfield can't express "no effort supports tools", so the runtime still sends the request. - Related: #1605 (GPT-6 models sent
max_tokens).
Suggested Fix
- Add a catalog record for
gpt-6-solwith an Azure Chat CompletionstoolReasoningEfforts: ["none"]profile, so SimpleChat sendsnoneautomatically when tools are present, as it does for GPT-5.6. Addgpt-6-lunaonce its behavior is verified. Done on the React V2 branch in 0.261.221 (#1608). - Let the catalog mark a model and protocol as not supporting function tools (for example, Azure Chat Completions for
gpt-6-astra). Fail early with a clear message in the agent editor and at run time instead of a provider 400. - Run local agents with tools through the Responses API for models that require it. This may need its own issue.
- Show a safe, specific reason in the workflow task error instead of the generic message.
- Add functional tests for the catalog rules and the early failure.
- 主要语言
- Python
- 星标
- 157
- 派生
- 117
- 平均合并
- 3 小时 6 分钟
- 30 天内合并 PR
- 219
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
microsoft/simplechat 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 84/100
microsoft/simplechat#1491 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
microsoft/simplechat#1370 ·
维护者通常 1 天内回复
-
Fix mixed-source chat excerpt truncation, default system prompt suppression, bracketed citations, and Semantic Ranker quota fallback可能已有人在做 @paullizer 于 4 天前认领。 未关闭bug P1
microsoft/simplechat#1855 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Add support for extracting comments from Word documents (.docx, .docm, .doc, .dotx)可能已有人在做 @paullizer 于 5 天前认领。 未关闭enhancement P2
microsoft/simplechat#1850 · 已指派 1 人 ·
维护者通常 1 天内回复
-
V2: Preserve explicit reasoning None across existing tool paths可能已有人在做 @paullizer 于 5 天前认领。 未关闭bug P1
microsoft/simplechat#1846 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 microsoft/simplechat 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
pytest-dev/pyfakefs#1367 · 1 条评论 ·
维护者通常 2 天内回复
-
IFEvalG exclude_word_harder misses the keyword next to punctuation, at the start or end of the text, and in other letter case可能已有人在做 @damienen 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
allenai/open-instruct#2151 ·
维护者通常 1 天内回复
-
feat(plan): support convertorLabels and convertorAffinity in Plan resource可能已有人在做 @AmenB 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
RedHatQE/openshift-python-wrapper#2849 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 25 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
libnativeapi/nativeapi#21 ·