[Bug] GPT-5.6 Terra fails in Ask Mode
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- java
- Domain
- developer-experience
Research direction
Start by tracing the Ask Mode request path for GPT-5.6 Terra, focusing on how it selects /v1/chat/completions and includes tools or reasoning_effort when reasoning is set to None. Reproduce the issue with the listed steps, then verify that the request no longer triggers the reported 400 response.
Written by the indexing model from the issue text.
Description
Environment
- OS: Windows 11 Enterprise Version: 25H2 Build: 26200.8875 Resource Pack: 1000.26100.334.0 Language: PT-BR
- Eclipse Version: 2026-06 (4.40.0) (Build id: 20260604-0653)
- Plugin Version: 0.21.0.202608060743
Describe the bug
GPT-5.6 Terra fails in Ask Mode with reasoning set to None: plugin still sends incompatible tools/reasoning via /v1/chat/completions
To Reproduce
Steps to reproduce the behavior:
- Open a new Chat
- Set the Agent Mode to 'Ask'
- Set the model to GPT 5.6 - Terra
- While setting the model, hover over your model choice to show the Thinking Effort menu.
- Choose "None"
- Write some basic prompt like "Explain the difference between an abstract class and an interface in Java"
- See the error.
Expected behavior
Sorry, an error occurred while generating a response. Details: unhandled status from server: 400 { "error": { "message": "Function tools with reasoning_effort are not supported for gpt-5.6-terra in /v1/chat/completions. To use function tools, use /v1/responses or set reasoning_effort to 'none'.", "ty... Read more from logs.
- Dominant language
- Java
- Stars
- 125
- Forks
- 63
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/copilot-for-eclipse
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/copilot-for-eclipse#474 ·
Maintainers usually reply within 1 day
-
[Feature Request] Copilot CLI Quick Launcher (Just like Intellij) with WSL & Auto-Install SupportOpenenhancement
Difficulty 5/5 Over a week Newbie friendliness 42/100
microsoft/copilot-for-eclipse#473 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/copilot-for-eclipse#472 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/copilot-for-eclipse#465 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/copilot-for-eclipse#458 ·
Maintainers usually reply within 1 day
All issues in microsoft/copilot-for-eclipse
Similar issues
-
[destination-snowflake] Custom domains rejected unlike source connectionsPossibly taken @kuza55 claimed this today. Openautoteam community connectors/destination/snowflake team/use
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
area-dashboard
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
component/operate kind/feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Forge coverage prompts carry text the agent cannot act onPossibly taken @graalvmbot claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
oracle/graalvm-reachability-metadata#10572 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
IBM/sample-app-mod#55 ·