[BUG]

[kiarash-na]

Problem (one or two sentences)

Coding with kimi: https://www.kimi.com/code/docs/en/more/third-party-agents.html#install-roo-code
Getting Error 400: Date/time: 2026-04-17T18:47:53.910Z
Extension version: 3.52.1
Provider: openai (proxy)
Model: kimi-for-coding

400
OpenAI completion error: 400 invalid temperature: only 0.6 is allowed for this model

Context (who is affected and when)

// Please share this file with Roo Code Support (support@roocode.com) to diagnose the issue faster
// Just make sure you're OK sharing the contents of the conversation below.

{
"error": {
"timestamp": "2026-04-17T18:48:07.707Z",
"version": "3.52.1",
"provider": "openai",
"model": "kimi-for-coding",
"details": "400\nOpenAI completion error: 400 invalid temperature: only 0.6 is allowed for this model"
},
"history": [
{
"role": "user",
"content": [
{
"type": "text",
"text": "<user_message>\nstrictly working here: /home/kia/projects/ee/website/src/app/[locale]/(app)/passport/settings/page.tsx and /home/kia/projects/ee/website/src/app/[locale]/(app)/passport/settings/_components/passport-settings.tsx the profile image in settings page MUST be exactly the same style as the welcome page and the passport public page, just slightly smaller so it looks good inside the settings page tab. also the passport number must be exactly next to it just like the other 2 variants. the only difference is, this image is slightly smaller, make it identical. ofcourse the upload, change and delete image functionality stays untouched.\n</user_message>"
},
{
"type": "text",
"text": "<environment_details>\n# VSCode Visible Files\n\n\n# VSCode Open Tabs\n\n\n# Current Time\nCurrent time in ISO 8601 UTC format: 2026-04-17T18:47:52.491Z\nUser time zone: Europe/Berlin, UTC+2:00\n\n# Current Cost\n$0.00\n\n# Current Mode\ncode\n💻 Code\nkimi-for-coding\n\n\n# Current Workspace Directory (/home/kia/projects/ee) Files\n🔒 .gitignore\n🔒 .rooignore\n.roomodes\n.claude/\n.cursor/\n.roo/\n.vscode/\napp/\napp/.cursorrules\n🔒 app/.gitignore\n🔒 app/bun.lock\napp/components.json\napp/env.example\napp/instrumentation-client.ts\napp/next.config.ts\napp/prisma.config.ts\napp/README.md\napp/tsconfig.json\napp/vitest.config.ts\napp/messages/de.json\napp/messages/en.json\napp/prisma/schema.prisma\napp/prisma/migrations/migration_lock.toml\napp/prisma/migrations/archive/20251129114442_add_newsletter/migration.sql\napp/public/auth-icon.gif\napp/public/globe.svg\napp/public/login-3.jpg\napp/public/next.svg\napp/public/star.png\napp/public/web-app-manifest-192x192.png\napp/public/masonry/1.jpg\napp/public/masonry/2.jpg\napp/public/masonry/3.jpg\napp/public/masonry/4.jpg\napp/public/masonry/5.jpg\napp/public/masonry/6.jpg\napp/public/masonry/7.jpg\napp/public/masonry/8.jpg\napp/public/masonry/9.jpg\napp/public/masonry/10.jpg\napp/public/masonry/11.jpg\napp/src/stores/user-store.ts\ndocs/\ndocs/.cursorrules\n🔒 docs/.rooignore\ndocs/MAGAZINE_FEATURE.md\ndocs/PostHog-Implementation-Audit.md\ndocs/README.md\ndocs/ADR/tech-stack.md\ndocs/Archive/Dev Notes/2026-01-27-auth-login-signup-debugging.md\ndocs/Archive/Dev Notes/2026-01-28-redis-cleanup-todos.md\ndocs/Archive/Dev Notes/admin-to-portal-subdomain-migration.md\ndocs/Archive/Dev Notes/cloudinary-media-library-widget-implementation.md\ndocs/Archive/Dev Notes/outdated-site-setup-guide.md\ndocs/Archive/Test Specifications/admin-listing-create-form.integration.test.spec.md\ndocs/Archive/Test Specifications/admin-listing-update-form.integration.test.spec.md\ndocs/Archive/Test Specifications/listing-test-helpers-extension.spec.md\ndocs/Archive/Test Specifications/map-listing-to-form.test.spec.md\ndocs/Archive/website-home-translation/01-translation-strategy-overview.md\ndocs/Archive/website-home-translation/02-database-schema-design.md\ndocs/Archive/website-home-translation/03-hero-slider-implementation.md\ndocs/Archive/website-home-translation/04-adventure-cards-implementation.md\ndocs/Archive/website-home-translation/05-translation-management.md\ndocs/Archive/website-home-translation/06-migration-and-rollout.md\ndocs/Audits/Feb 2026/01-listing-schema-audit.md\ndocs/Audits/Feb 2026/02-schema-structure-tables.md\ndocs/Audits/Jan 2026/00-executive-summary.md\ndocs/Audits/Jan 2026/01-assumption-vs-reality.md\ndocs/Audits/Jan 2026/02-cross-repo-relationships.md\ndocs/Audits/Jan 2026/03-overlap-analysis.md\ndocs/Audits/Jan 2026/04-operational-reality.md\ndocs/Audits/Jan 2026/05-data-layer-reality.md\ndocs/Audits/Jan 2026/06-what-you-should-know.md\ndocs/Audits/Jan 2026/07-migration-and-deployment-plan.md\ndocs/Audits/Jan 2026/08-database-audit.md\ndocs/Blueprints/navbar-blueprint.md\ndocs/Blueprints/database/00-README.md\ndocs/Blueprints/database/01-DATABASE-BLUEPRINT.md\ndocs/Blueprints/database/02-SCHEMA_SYNC_QUICKSTART.md\ndocs/Blueprints/database/03-SHARED_SCHEMA.md\ndocs/Blueprints/database/04-SAFE_MIGRATIONS.md\ndocs/Blueprints/database/05-MIGRATION_CLEANUP.md\ndocs/Blueprints/database/06-FRESH_DEPLOYMENT.md\ndocs/Blueprints/database/07-SUGGESTED_DOCUMENTATION.md\ndocs/Blueprints/listing/listing-booking-card-blueprint.md\ndocs/Blueprints/listing/single-listing-page-blueprint.md\ndocs/Blueprints/responsive/responsive-maker-blueprint.md\ndocs/Blueprints/responsive/responsive-maker-header-footer.md\ndocs/Blueprints/responsive/responsive-maker-old-dont-touch.md\ndocs/Blueprints/responsive/responsive-maker-website-home.md\ndocs/Blueprints/tests/portal/test-blueprint.md\ndocs/Blueprints/tests/website/test-blueprint.md\ndocs/Dev Notes/To-do Lists/booking-system-app-todo.md\ndocs/Dev Notes/To-do Lists/booking-system-database-todo.md\ndocs/Dev Notes/To-do Lists/portal-routes-complete-analysis.md\ndocs/Dev Notes/To-do Lists/static-pages-migration.md\ndocs/Dev Notes/To-do Lists/stripe-connect-integration.md\ndocs/Dev Notes/To-do Lists/user-management-create-user-tests.md\ndocs/Dev Notes/To-do Lists/yoopta-to-markdown-migration-plan.md\ndocs/Dev Notes/To-do Lists/Portal access levels/00-implementation-complete.md\ndocs/Dev Notes/To-do Lists/Portal access levels/01-analysis-and-route-design.md\ndocs/Dev Notes/To-do Lists/Portal access levels/02-auth-flow-refactoring.md\ndocs/Dev Notes/To-do Lists/Portal access levels/03-workspace-route-layout.md\ndocs/Dev Notes/To-do Lists/Portal access levels/04-role-based-sidebar.md\ndocs/Dev Notes/To-do Lists/Portal access levels/05-access-control-guards.md\ndocs/Dev Notes/To-do Lists/Portal access levels/06-provider-features.md\ndocs/Dev Notes/To-do Lists/Portal access levels/07-company-owner-features.md\ndocs/Dev Notes/To-do Lists/Portal access levels/08-multi-role-users.md\ndocs/Dev Notes/To-do Lists/Portal access levels/09-impersonation-feature.md\ndocs/Dev Notes/To-do Lists/Portal access levels/10-testing-and-validation.md\ndocs/Dev Notes/To-do Lists/Portal access levels/11-security.md\ndocs/Dev Notes/To-do Lists/Portal access levels/12-routing-fixes-march-2026.md\ndocs/Dev Notes/To-do Lists/single-listing-page/01-hero.md\ndocs/Dev Notes/To-do Lists/single-listing-page/02-overview.md\ndocs/Dev Notes/To-do Lists/single-listing-page/03-itinerary-map.md\ndocs/Dev Notes/To-do Lists/single-listing-page/04-gallery.md\ndocs/Dev Notes/To-do Lists/single-listing-page/05-video.md\ndocs/Dev Notes/To-do Lists/single-listing-page/06-guides.md\ndocs/Dev Notes/To-do Lists/single-listing-page/07-who-is-joining.md\ndocs/Dev Notes/To-do Lists/single-listing-page/08-optional-block-1.md\ndocs/Dev Notes/To-do Lists/single-listing-page/09-accommodation.md\ndocs/Dev Notes/To-do Lists/single-listing-page/10-optional-block-2.md\ndocs/Dev Notes/To-do Lists/single-listing-page/11-key-info.md\ndocs/Dev Notes/To-do Lists/single-listing-page/12-booking-card.md\ndocs/Dev Notes/To-do Lists/single-listing-page/13-faq.md\ndocs/Dev Notes/To-do Lists/single-listing-page/14-support.md\ndocs/Dev Notes/To-do Lists/single-listing-page/15-optional-block-3.md\ndocs/Dev Notes/To-do Lists/single-listing-page/16-reviews.md\ndocs/Dev Notes/To-do Lists/single-listing-page/17-share.md\ndocs/Dev Notes/To-do Lists/single-listing-page/18-similar-activities.md\ndocs/Dev Notes/To-do Lists/single-listing-page/19-optional-block-4.md\ndocs/Dev Notes/To-do Lists/single-listing-page/figma-mcp-guide.md\ndocs/Dev Notes/To-do Lists/slug-sync/01-form-and-actions-todo.md\ndocs/Dev Notes/To-do Lists/slug-sync/02-routing-and-links-todo.md\ndocs/Dev Notes/To-do Lists/slug-sync/slug-sync-blueprint.md\ndocs/Dev Notes/To-do Lists/tests/admin-listings-form.component.test.spec.md\ndocs/Email-System/00-email-system-overview.md\ndocs/Email-System/01-environment-configuration.md\ndocs/Email-System/02-transactional-email-issues.md\ndocs/Email-System/03-email-templates-comparison.md\ndocs/Email-System/04-admin-email-management.md\ndocs/Email-System/05-setup-checklist.md\ndocs/Onboarding/01-onboarding-and-testing-guide.md\ndocs/Onboarding/02-Database-Safe-Setup-TODO.md\ndocs/Plans/magazine-author-fix-plan.md\ndocs/Plans/partnero-referral-integration-plan.md\ndocs/Plans/performance-auditing-setup.md\ndocs/Skills/posthog-nextjs-integration.md\ndocs/Skills/resend-mcp-skill.md\ndocs/Skills/shadcnblocks-integration.md\nmcp-send-email/\nmcp-send-email/.env.example\n🔒 mcp-send-email/.gitignore\nmcp-send-email/.mcp.json\nmcp-send-email/biome.json\nmcp-send-email/CHANGELOG.md\nmcp-send-email/email.md\nmcp-send-email/LICENSE\n🔒 mcp-send-email/package-lock.json\nmcp-send-email/package.json\n🔒 mcp-send-email/pnpm-lock.yaml\nmcp-send-email/README.md\nmcp-send-email/renovate.json\nmcp-send-email/tsconfig.json\nmcp-send-email/vitest.config.ts\nmcp-send-email/scripts/check-dependency-versions.ts\nmcp-send-email/scripts/pull-request-title-check.ts\nmcp-send-email/src/index.ts\nmcp-send-email/src/server.ts\nmcp-send-email/src/types.ts\nmcp-send-email/src/cli/constants.ts\nmcp-send-email/src/cli/help.ts\nmcp-send-email/src/cli/index.ts\nmcp-send-email/src/cli/parse.ts\nmcp-send-email/src/cli/resolve.ts\nmcp-send-email/src/cli/types.ts\nmcp-send-email/src/tools/apiKeys.ts\nmcp-send-email/src/tools/broadcasts.ts\nmcp-send-email/src/tools/contactProperties.ts\nmcp-send-email/src/tools/contacts.ts\nmcp-send-email/src/tools/domains.ts\nmcp-send-email/src/tools/emails.ts\nmcp-send-email/src/tools/index.ts\nmcp-send-email/src/tools/segments.ts\nmcp-send-email/src/tools/topics.ts\nmcp-send-email/src/tools/webhooks.ts\nmcp-send-email/src/transports/http.ts\nmcp-send-email/src/transports/stdio.ts\nplans/\nplans/magazine-component-specifications.md\nplans/magazine-server-components-implementation.md\nportal/\nportal/.cursorrules\n🔒 portal/.gitignore\n🔒 portal/bun.lock\nportal/components.json\nportal/instrumentation-client.ts\nportal/posthog-setup-report.md\nscripts/\nwebsite/\n\n(File list truncated. Use list_files on specific subdirectories if you need to explore further.)\nYou have not created a todo list yet. Create one with update_todo_list if your task is complicated or involves multiple steps.\n</environment_details>"
}
],
"ts": 1776451672536
}
]
}

Reproduction steps

Extension disabled and restarted but no success.
api calls to Moonshot/Kimi work elsewhere perfectly.

Expected result

NA

Actual result

NA

Variations tried (optional)

No response

App Version

version": "3.52.1",

API Provider (optional)

OpenAI Compatible

Model Used (optional)

Kimi for coding

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote-v0]

I've analyzed this issue and here's my proposed implementation plan:

Root Cause

The OpenAiHandler (used by the "OpenAI Compatible" provider) has a bug where createMessage() computes temperature independently from getModel(), ignoring the defaultTemperature field from custom model info.

Specifically in src/api/providers/openai.ts:

• Line 87: getModel() is called and correctly computes temperature via getModelParams() (which respects model.defaultTemperature), but only info and reasoning are destructured -- temperature is discarded.
• Line 157: Temperature is re-computed as this.options.modelTemperature ?? 0, which ignores defaultTemperature from the model info entirely.
• Non-streaming path (line 224) and completePrompt (line 301): Temperature is not set at all, falling back to the API default.

When using the OpenAI Compatible provider with Kimi's kimi-for-coding model, Roo Code sends temperature: 0 (the hardcoded default), but this model only accepts temperature: 0.6, resulting in a 400 error.

Proposed Fix

1. In createMessage() streaming path: Destructure temperature from getModel() and use it in the request body instead of computing it separately. This ensures defaultTemperature from custom model info is respected.
2. In createMessage() non-streaming path: Add the temperature field from getModel() to the request options (currently missing entirely).
3. In completePrompt(): Add temperature from getModel() to the request options (currently missing).

This makes temperature handling consistent: getModelParams() is the single source of truth for temperature (it already handles user overrides, model defaults, and provider defaults in the correct priority order).

After this fix, users can either:

• Set temperature to 0.6 in Roo Code settings (applies to all models), OR
• Set defaultTemperature: 0.6 in their custom model info for that specific model (which will now actually be respected)

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[matgir99]

same issue as #12141 that had a PR created

[kiarash-na]

Already tried the proposed fix, no success. @roomote <https://github.com/roomote> proceed

…

On Fri, Apr 17, 2026 at 9:11 PM roomote-v0[bot] ***@***.***> wrote: *roomote-v0[bot]* left a comment (RooCodeInc/Roo-Code#12142) <#12142 (comment)> I've analyzed this issue and here's my proposed implementation plan: Root Cause The OpenAiHandler (used by the "OpenAI Compatible" provider) has a bug where createMessage() computes temperature independently from getModel(), ignoring the defaultTemperature field from custom model info. Specifically in src/api/providers/openai.ts: - *Line 87*: getModel() is called and correctly computes temperature via getModelParams() (which respects model.defaultTemperature), but only info and reasoning are destructured -- temperature is discarded. - *Line 157*: Temperature is re-computed as this.options.modelTemperature ?? 0, which ignores defaultTemperature from the model info entirely. - *Non-streaming path (line 224)* and *completePrompt (line 301)*: Temperature is not set at all, falling back to the API default. When using the OpenAI Compatible provider with Kimi's kimi-for-coding model, Roo Code sends temperature: 0 (the hardcoded default), but this model only accepts temperature: 0.6, resulting in a 400 error. Proposed Fix 1. *In createMessage() streaming path*: Destructure temperature from getModel() and use it in the request body instead of computing it separately. This ensures defaultTemperature from custom model info is respected. 2. *In createMessage() non-streaming path*: Add the temperature field from getModel() to the request options (currently missing entirely). 3. *In completePrompt()*: Add temperature from getModel() to the request options (currently missing). This makes temperature handling consistent: getModelParams() is the single source of truth for temperature (it already handles user overrides, model defaults, and provider defaults in the correct priority order). After this fix, users can either: - Set temperature to 0.6 in Roo Code settings (applies to all models), OR - Set defaultTemperature: 0.6 in their custom model info for that specific model (which will now actually be respected) Please mention @roomote <https://github.com/roomote> in a comment saying that you approve this plan, and I'll proceed with the implementation. — Reply to this email directly, view it on GitHub <#12142?email_source=notifications&email_token=BZ22LLWDEI2UTBJB6UD6PX34WJ6XBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRXGA3DENBTGUZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4270624352>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BZ22LLUTK7JDL5UHDUONFHL4WJ6XBAVCNFSM6AAAAACX5KXRTKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DENZQGYZDIMZVGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[roomote-v0]

I've seen the comment and will work on a fix. The approach from PR #12143 (omitting temperature) is incomplete -- the root cause is that createMessage() computes temperature independently from getModel(), ignoring defaultTemperature from custom model info. I'll open a PR that uses the temperature from getModelParams() as the single source of truth, which properly respects user overrides, model defaults, and provider defaults. Will share progress shortly.

[roomote-v0]

Opened a draft PR with my attempt at addressing this: #12144

The fix makes getModelParams() the single source of truth for temperature across all code paths in the OpenAI handler. Previously, createMessage() computed temperature independently and ignored defaultTemperature from custom model info. Now users can set defaultTemperature: 0.6 in their custom model info for kimi-for-coding and it will be correctly sent to the API.

This differs from PR #12143 (which omits temperature entirely when not set) -- instead, this approach always sends the correctly computed temperature, respecting the priority chain: user override > model defaultTemperature > provider default.

Feedback welcome!