Repository navigation
chore(sync): merge pingdotgg/t3code main - #270
Merged
Merged
Conversation
… setting (pingdotgg#22841) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…nstall (pingdotgg#22855) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.
Cause
The Fork Sync run 39604718103 stopped on a merge conflict. Upstream added 3 commits. The main one is pingdotgg#22790, "send selected held messages when a thread is stopped". It adds a "Send now" action and a
queued-run.startcommand.Conflict and how it is resolved
apps/web/src/components/chat/QueuedRunsControl.tsx, steer tooltip: upstream's new text ("Start a turn with this message" or "Send as a steer instead") replaces the old text. The forkShortcutHintstays, and it now shows for the first row whencanSendis true. The fork removed thesteerShortcutLabelprop, so upstream's label suffix is not used.Upstream changes in fork areas
QueuedRunsControl.tsx: upstream added a secondresumecommand atom. The fork already hasresumeQueueand a localresumehandler, so the web typecheck failed. "Send now" now usesresumeQueue.queued-run.starton a usage-limited queue, the same asqueue.resume. On the web, "Send now" now continues the limited thread first, as "Resume queue" does. On mobile, "Send now" stays disabled under a usage limit. The paused-queue row already explains why. A new browser test covers the web behaviour. The README fork line is updated.threadWorkflows.test.ts: upstream's new test fixture had noturnItems. The forkheldByUsageLimitreads them, so the fixture now hasturnItems: [].apps/server/src/cli/pair.ts(fix(server): t3 pair in a worktree no longer falls back to the live install pingdotgg/t3code#22855): in a linked worktree,t3 pairno longer falls back to the shared home. The fork tunnel pairing URL inresolveDirectPairingBaseUrlis not affected.ClaudeAdapterV2.ts(fix(server): delegated Claude children follow your subagent cache TTL setting pingdotgg/t3code#22841),Orchestrator.ts, contracts and client-runtime: these merged without conflicts and did not affect fork code.Checks
vp run typecheck: the only failure was the duplicateresumedeclaration, and it is fixed. Web and mobile typecheck pass after the fix.pair.test.ts,ClaudeAdapterV2.test.ts,keybindings.test.ts,threadWorkflows.test.ts(21) andQueuedRunsControl.browser.test.tsx(2) pass.