Repository navigation
Use typed eager tools by default for v0.10.0 - #1
Merged
Merged
Conversation
idpfaff
marked this pull request as ready for review
November 8, 2026 16:49
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The default lazy dispatcher hid tool argument fields and completed 1/20 approval cases against 17/20 for eager schemas. This change makes every profile advertise named, typed tools, removes
--tool-discoverywith migration guidance, and retains the facade only behind a warned--experimental-lazyswitch. Roles and allowlists stay enforced.The ten-tool API function list drops from 1,485 to 998 bundled
o200k_basetokens; instructions grow from 155 to 239, so their combined subtotal drops from 1,640 to 1,237 (24.6%). These are offline serialization counts, not model or billed savings. A snapshot enforces the under-1,000 definition budget. Unknown/missing/type errors now return compact JSON with accepted fields, and SDK-decoded experimental arguments are authorized before execution.The planned evaluator compares the hash-pinned v0.9.2 eager interface, compact eager schemas, and experimental lazy with typed errors on the same 20 cases. All arms use current execution and identical full JSON/text-only replies; exact numeric grading and historical report publication are covered offline. The command defaults to plan-only and requires
--executefor paid calls.Validation: 1,023 offline tests passed on macOS/Python 3.13; Ruff lint and formatting passed; wheel and sdist built offline. Process-watchdog tests required execution outside the local sandbox. The eager recurring workflow passed 25/25 checks. All seven remote commit trees match their locally tested counterparts. Nothing under
benchmarks/results/or the release workflow was changed.The corrective v0.10.0 release proceeds through the existing exact-commit full-CI release gate. The eight-job CI matrix passed for the code changes; the final follow-up commit only reconciles release documentation. No paid model evaluation was run. Compact-eager completion and the planned control-minus-one model acceptance check remain unmeasured; this release is an explicit exception to that check, and subsequent default-profile changes must satisfy it.