Repository navigation
refactor(provider-core): add the provider client contract package - #17282
Closed
juliusmarminge wants to merge 1 commit into
Closed
juliusmarminge wants to merge 1 commit into
juliusmarminge wants to merge 1 commit into
Conversation
Provider client metadata (label, settings schema, environment fields, badge) lived in a web-only table. Move its shape into a new @t3tools/provider-core package as ProviderClientDefinition plus a small registry, so provider packages can export their client half against a shared interface. The web settings UI now reads the registry; the definitions themselves still live in web until each provider moves out. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
juliusmarminge
added this pull request to stack #17289
October 8, 2026 19:33
This was referenced Oct 8, 2026
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
This was referenced Oct 8, 2026
Member
Author
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.
Provider client metadata (label, settings schema, environment fields, badge) lived in a web-only table, so there was no shared interface a provider package could export its client half against.
This adds
@t3tools/provider-corewith a./cliententry:ProviderClientDefinition, plus a small registry that looks definitions up by driver kind (and returnsundefinedfor drivers a client does not ship, such as a fork's). The web settings, onboarding, and usage code now read that registry. The definitions themselves stay in web until each provider moves into its own package.No behavior change.
Part of the provider-packages stack: #17282 → #17283 → #17284 → #17285 → #17286 → #17287 → #17288.
Done by Claude Opus 5.5 in Claude Code.
🤖 Generated with Claude Code