adjust reasoning level options based on models

[iceljc]

PR Type

Enhancement

---

Description

• Dynamically adjust reasoning level options based on selected model capabilities

• Add support for additional reasoning effort levels (none, xhigh)

• Update reasoning level label and automatically reset invalid selections

• Trigger model change handler when provider or model selection changes

---

Diagram Walkthrough

flowchart LR
  A["Model Selection"] -->|onModelChanged| B["Get Model Reasoning Config"]
  B -->|Extract EffortLevel Options| C["Update reasoningLevelOptions"]
  C -->|Validate Current Selection| D["Reset if Invalid"]
  D -->|Update UI| E["Reasoning Level Dropdown"]

Loading

File Walkthrough

Relevant files

Enhancement

chat-config.svelte Dynamic reasoning level options based on model                      src/routes/page/agent/[agentId]/agent-components/llm-configs/chat-config.svelte Renamed reasonLevelOptions to defaultReasonLevelOptions and made it a reactive variable reasoningLevelOptions Added onModelChanged() function to update reasoning level options when model changes Added getReasoningLevelOptions() function to extract model-specific reasoning effort levels from model configuration Call onModelChanged() in provider and model change handlers to dynamically update available options Changed label from "Reasoning effort" to "Reasoning level" Automatically reset reasoning effort level if current selection is invalid for new model +40/-4    enums.js Add none and xhigh reasoning effort levels                              src/lib/helpers/enums.js Added None: "none" option to reasoning effort levels Added XHigh: "xhigh" option to reasoning effort levels Expanded supported reasoning effort level range from 4 to 5 options +3/-1

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: No audit logging: The PR updates agent LLM configuration fields (provider/model/reasoning level) without any visible audit-trail logging, so it is unclear whether these potentially critical configuration changes are recorded with user/context elsewhere. Referred Code async function changeProvider(e) { const provider = e.target.value; config.provider = provider || null; if (!!!provider) { models = []; config.model = null; config.reasoning_effort_level = null; handleAgentChange(); return; } config.is_inherit = false; models = getLlmModels(provider); config.model = models[0]?.name; onModelChanged(config); handleAgentChange(); } /** @param {any} e */ function changeModel(e) { ... (clipped 48 lines) Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Logging not visible: This PR changes how model/provider/reasoning selections are applied but adds no visible structured logging, so it cannot be confirmed whether any emitted logs avoid sensitive data and follow structured logging standards. Referred Code async function changeProvider(e) { const provider = e.target.value; config.provider = provider || null; if (!!!provider) { models = []; config.model = null; config.reasoning_effort_level = null; handleAgentChange(); return; } config.is_inherit = false; models = getLlmModels(provider); config.model = models[0]?.name; onModelChanged(config); handleAgentChange(); } /** @param {any} e */ function changeModel(e) { ... (clipped 48 lines) Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Ensure configuration changes are always saved Call handleAgentChange() within the onModelChanged function to ensure any configuration modifications are consistently saved. src/routes/page/agent/[agentId]/agent-components/llm-configs/chat-config.svelte [136-143] function onModelChanged(config) { reasoningLevelOptions = getReasoningLevelOptions(config?.model); if (config && !reasoningLevelOptions.some(x => x.value === config.reasoning_effort_level)) { const defaultOption = reasoningLevelOptions.find(x => !!x.value)?.value || null; config.reasoning_effort_level = defaultOption; } + handleAgentChange(); } Apply / Chat Suggestion importance[1-10]: 8 __ Why: The suggestion correctly identifies a bug where configuration changes made on component initialization are not saved, leading to state inconsistency. Centralizing the handleAgentChange() call within onModelChanged is the right fix.	Medium
	Prevent crash from invalid model configuration Add an Array.isArray() check in getReasoningLevelOptions before mapping over defaultOptions to prevent potential crashes from invalid model configuration. src/routes/page/agent/[agentId]/agent-components/llm-configs/chat-config.svelte [146-163] function getReasoningLevelOptions(model) { let options = defaultReasonLevelOptions; const foundModel = models.find(x => x.name === model); if (foundModel?.reasoning == null) { return options; } const defaultOptions = foundModel?.reasoning?.parameters?.EffortLevel?.options; - if (defaultOptions?.length > 0) { + if (Array.isArray(defaultOptions) && defaultOptions.length > 0) { options = [ { value: '', label: '' }, // @ts-ignore ...defaultOptions.map(x => ({ value: x, label: x })) ]; } return options; } [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 7 __ Why: This is a good defensive programming suggestion that makes the component more robust by preventing a potential runtime error if the model configuration data is malformed, which is a valid concern.	Medium
More