fix(mobile): wait for deep-link thread hydration - #764
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
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 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.
Opening a thread deep link could show "Thread unavailable" while that environment's shell and thread detail were still synchronizing. The route now waits for its own shell/detail state, while deleted threads and sync errors leave loading promptly. A deleted or missing thread returns to the thread list; connection failures can retry the environment; unknown environments open environment settings.
Adapted from T3 commit
caf8b5d798909780a7b197cb264e782888b919c1(#11502). The terminal recovery action is Pylon-specific: reconnecting cannot restore a deleted or missing thread. Existing shell-first thread rendering, drafts, and local/remote environment selection remain intact.Validation: 7 focused mobile/shared shell tests passed, mobile typecheck and scoped lint passed, and independent source review cleared the final patch. Lint reports pre-existing ThreadRouteScreen warnings. Browser/device verification was not run because AGENTS.md requires explicit approval.
Model: GPT-6 Sol (low). Harness: Codex in Pylon, with GPT-6 root oversight and independent review.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.