Repository navigation
refactor(provider-pi): move Pi into its own provider package - #17288
Closed
juliusmarminge wants to merge 1 commit into
Closed
juliusmarminge wants to merge 1 commit into
juliusmarminge wants to merge 1 commit into
Conversation
Pi is the first provider to live in its own package, @t3tools/provider-pi, following the convention the other drivers will use: - ./settings: the instance settings schema (moved out of contracts). - ./client: the client definition with label, settings form, and a plain-data icon. Web and mobile render the icon from the package instead of a hand-drawn Pi branch. - ./server: the driver and adapter driver the server registers. Pi's server code imports only provider-core, contracts, and shared, and reaches the server through ProviderHost. The managed status provider, its snapshot settings source, and the context handoff budget move into provider-core so the package can use them. The adding-a-provider checklist now describes the package layout. Co-Authored-By: Claude Opus 5.5 <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: unavailable · PR result: 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.
Pi is the first provider in its own package,
@t3tools/provider-pi, following the convention the other drivers will use:./settings: the instance settings schema, moved out of contracts../client: the client definition with label, settings form, and a plain-data icon (no React). Web and mobile render the icon from the package instead of hand-drawn Pi branches../server: the driver and adapter driver the server registers.Pi's server code now imports only provider-core, contracts, and shared, and reaches the server through
ProviderHost. The managed status provider, its snapshot-settings source, the context handoff budget, and provider continuation requests move into provider-core so the package can use them. The adding-a-provider checklist now describes the package layout.Not checked in a running client: the Pi icon should look identical in light and dark mode on web and mobile.
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