Skip to content

Preserve provider ordinary-tool history options in native adapter - #18

Merged
Brian Krabach (bkrabach) merged 1 commit into
mainfrom
fix/native-history-options-20261021
Oct 21, 2026
Merged

Brian Krabach (bkrabach) merged 1 commit into
mainfrom
fix/native-history-options-20261021

Conversation

@bkrabach

Copy link
Copy Markdown
Collaborator

The current OpenAI provider passes ordinary_names into native history projection, but the optional CLI adapter rejects that keyword before sending a request. Accept the provider's classification and preserve ordinary computer-shaped tool results in both adapter paths; native screenshot failure handling stays in place.

Validation against current provider df44a798: 10 failing-before cases, 52 affected checks passing after, plus independent review with two full fake-wire ordinary-tool cases. Tests cover original call/result identity, unchanged canonical history, native cancellation and attribution, and default native screenshot refusal. The new regressions run in the optional-provider CI lane. No live model calls or provider protocol fields changed.

@bkrabach
Brian Krabach (bkrabach) merged commit 7aea6df into main Oct 21, 2026
6 checks passed
@bkrabach

Brian Krabach (bkrabach) commented Oct 21, 2026 •

Copy link
Copy Markdown
Collaborator Author

Included in #17, merged as 7607382. GitHub also marked this PR merged because its exact commit is included in that ancestry.

The adapter implementation and its regressions are unchanged from this independently reviewed candidate. The combined #17 candidate passed all four Linux/macOS Python jobs, the dedicated native-adapter job, wheel builds and isolated package-import checks. Consolidating the two related corrections preserved the exact tested source while avoiding a duplicate dependency-setup wait. No adapter changes or regression coverage were dropped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant