Skip to content

chore(agent): update the T3 provider runtime to upstream main - #2586

Merged
vite-hub[bot] merged 2 commits into
mainfrom
chore/t3code-sync-20261017
Oct 17, 2026
Merged

vite-hub[bot] merged 2 commits into
mainfrom
chore/t3code-sync-20261017

Conversation

@onmax

@onmax onmax commented Oct 17, 2026

Copy link
Copy Markdown
Member

The T3 provider runtime that Provider Agents use was 1082 upstream commits behind. The fork's daily sync had failed on merge conflicts since at least 2026-10-13.

The fork now has upstream main merged, with the embedded runtime ported to upstream's new provider-core package (vite-hub/t3code#12). This PR moves the @t3tools/provider-runtime pin to that build. The runtime now uses Effect 4.0.5, so the lockfile drops Effect 4.0.1. I edited the lockfile entries by hand: 2 changed URLs, 2 new integrities, and the Effect version.

The fork sync also fixes one problem: the runtime loaded the Claude SDK when a Codex-only host imported it.

This is a stopgap. The pin is still a pkg.pr.new URL, which pnpm 12 rejects. The real fix for #2545 is in a follow-up PR.

Verified

  • pnpm install --frozen-lockfile
  • Live smoke on the new runtime for Codex and Claude Code: a reply, then a new runtime that resumes the thread from the turn's resumeCursor and recalls the earlier turn.
  • provider-agent, box, and nuxt-runtime-output tests give the same results as on main.
  • Tests that fail on both pins: providers.test.ts (5 to 18 failures depending on machine load, a different set each run), babysitter-preset (8 to 13 per run, and it mocks the runtime), and nuxt-runtime-output (1 test).

🤖 Generated with Claude Code

Pin @t3tools/provider-runtime to the vite-hub/t3code sync of upstream main
(4a1a008). The runtime now uses Effect 4.0.5, so the lockfile drops 4.0.1.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 17, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-17T22:34:28.735596Z 5799dfc New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

This PR records an integrity hash that does not match the tarball currently served for the new @t3tools/contracts URL, so a clean frozen install fails before the workspace can install.

Reviewed changes

The dependency catalog and lockfile update for the T3 provider runtime, its contracts package, and the transitive Effect version were reviewed.

  • Provider runtime pin — moves @t3tools/provider-runtime and @t3tools/contracts to the 4a1a0087b30b479aa78871bc789ac9a766afffca pkg.pr.new build.
  • Effect resolution — replaces the runtime graph's effect@4.0.1 entry with effect@4.0.5, matching the existing workspace catalog.

Note: 1 inline comment(s) dropped because they did not anchor to lines inside the PR diff:

  • pnpm-lock.yaml:42-44 (RIGHT) — line 44 (RIGHT) is not inside a diff hunk

Pullfrog  | Fix it ➔ | View workflow run | Using gpt-5.6-sol | 𝕏

@vite-hub

vite-hub Bot commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor
Session Status Started Duration
Pending Completed Not started —
View session Waiting 2026-10-17T23:20:24.363Z 4m 53s
View session Failed 2026-10-17T23:13:12.305Z 2m 8s
View session Starting Not started —

Latest result

Pull request merged.

Final answers

Session

Pull request merged.

Session

Waiting for GitHub merge request 98bfe400-5d58-40cf-a2ef-7e55facb8fd5.

View session

Verified current HEAD and both recent Pullfrog reviews. The initial Pullfrog P1 contracts integrity finding was fixed in 5799dfc and the follow-up review confirms frozen install consistency; no valid P0/P1 findings remain. Focused lint passed with existing warnings, typecheck was attempted, and no repair is needed.

pkg.pr.new rebuilt the fork's 4a1a008 packages when that commit reached the
fork's main. The contracts tarball changed bytes, so CI rejected the old
integrity.
@pkg-pr-new

pkg-pr-new Bot commented Oct 17, 2026

Copy link
Copy Markdown

Open in StackBlitz

@vite-hub/agent

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/agent@2586

@vite-hub/auth

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/auth@2586

@vite-hub/blob

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/blob@2586

@vite-hub/browser

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/browser@2586

@vite-hub/channels

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/channels@2586

@vite-hub/cli

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/cli@2586

@vite-hub/connections

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/connections@2586

@vite-hub/content

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/content@2586

@vite-hub/database

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/database@2586

@vite-hub/email

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/email@2586

@vite-hub/env

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/env@2586

@vite-hub/forge

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/forge@2586

@vite-hub/kv

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/kv@2586

@vite-hub/markdown-template

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/markdown-template@2586

@vite-hub/presets

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/presets@2586

@vite-hub/queue

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/queue@2586

@vite-hub/rate-limit

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/rate-limit@2586

@vite-hub/realtime

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/realtime@2586

@vite-hub/runtime

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/runtime@2586

@vite-hub/sandbox

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/sandbox@2586

@vite-hub/sandbox-task

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/sandbox-task@2586

@vite-hub/schedule

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/schedule@2586

@vite-hub/shell

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/shell@2586

@vite-hub/source

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/source@2586

@vite-hub/ui

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/ui@2586

vite-hub

pnpm add https://pkg.pr.new/vite-hub/vitehub/vite-hub@2586

@vite-hub/workflow

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/workflow@2586

@vite-hub/workspace

pnpm add https://pkg.pr.new/vite-hub/vitehub/@vite-hub/workspace@2586

commit: 5799dfc

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes

The incremental change since the prior Pullfrog review updates the contracts tarball integrity and was validated with a clean frozen install.

  • Corrected contracts integrity — replaced the stale @t3tools/contracts hash with the integrity for the republished tarball at the existing 4a1a0087b30b479aa78871bc789ac9a766afffca URL.
  • Confirmed lockfile consistency — corepack pnpm install --frozen-lockfile now completes successfully without modifying the lockfile.

Pullfrog  | View workflow run | Using gpt-5.6-sol | 𝕏

@vite-hub
vite-hub Bot merged commit 46469cc into main Oct 17, 2026
17 checks passed
@onmax
onmax deleted the chore/t3code-sync-20261017 branch November 1, 2026 11:25
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