Databricks model services silently ignore thinking effort
- Dominant language
- Rust
- Stars
- 54.2k
- Forks
- 6.2k
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 240
Description
**Bug:** Goose accepts thinking-effort changes for Claude model services, but Off/Low/Medium/High/Max produce identical MLflow requests with no reasoning configuration.
**Reproduce:** Select a fully qualified Claude model under databricks_v2, change thinking effort, and inspect outgoing requests.
**Expected:** Apply supported effort settings, or disable the control when unsupported.
Contributor guide
Research direction
Look for the Databricks model service integration code, likely in a module like `src/services/databricks_v2.rs`. Find where thinking-effort settings are processed for Claude models and where MLflow requests are constructed. The bug is that the effort setting is ignored in the request. Check if the Databricks API supports a reasoning configuration field. The fix is to map the effort levels to the correct API parameter or disable the UI control if unsupported.
Written by the indexing model from the issue text.
Assessment
- Domain
- ai-infra-agents
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 65/100