Repository navigation
fix(models): support max thinking effort - #309
Alan-TheGentleman merged 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe change adds ChangesThinking level support
Estimated code review effort: 2 (Simple) | ~10 minutes Mergeability Score: ⚪ Minimal · up to This localized change adds support for the max thinking effort and propagates it through generated profiles; no actionable merge-blocking risk remains after normal checks and review. Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
c0a96df
into
Gentleman-Programming:main
Closes #286
Summary
maxto the ordered thinking-effort vocabulary used by/gentle:models.thinking: "max"through normalization and emit it aseffort: "max"in generated subagent profiles.Changes
extensions/gentle-ai.tsmaxafterxhigh.tests/runtime-harness.mjsTest plan
pnpm run test:harnessnode --experimental-strip-types --test tests/gentle-ai.test.tsPR type
Contributor checklist
type:*label.Out of scope
Provider-specific effort filtering remains the runtime responsibility.
Summary by CodeRabbit
New Features
Bug Fixes