continuedev / continuedev/continue
The temperature field will be automatically injected even if it is not set.
Open
Nobody has claimed this yet.
area:configuration
kind:bug
- Dominant language
- TypeScript
- Stars
- 36k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Before submitting your bug report
- I've tried finding an answer on the Continue docs site
- I'm not able to find an open issue that reports the same bug
- I've seen the troubleshooting guide on the Continue Docs
Relevant environment info
- OS:
- Continue version:
- IDE version:
- Model:
- config:
OR link to agent in Continue hub:
Description
I didn't add the temperature field, and continue would automatically inject it; however, the PackyCode I'm using doesn't support this field.
To reproduce
No response
Log output
{"message":"Unsupported parameter: temperature","type":"bad_response_status_code","param":"","code":"bad_response_status_code"}
Contributor 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.
Research direction
Start with the Continue configuration and request path, using the reported PackyCode model and the log message about the unsupported temperature parameter. Reproduce the request with temperature omitted, then verify that the parameter is no longer sent unless it is explicitly configured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend-api-design
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100