fix(mobile): recover from screen render failures - #768
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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 branch was successfully deployed
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.
A render exception in a mobile route, sidebar, conversation feed, or inspector could replace the whole view with an unrecoverable error. This adds bounded error views with Try again, Copy details, and route exit actions. Navigation identity and workspace changes reset a failed subtree; feed failure leaves the composer mounted. The New Task flow keeps its provider and draft selection mounted when a child screen fails, while an outer boundary can still catch provider-level errors.
Adapted from T3 commit
23c7ab901afa66dc8e791a3873b600726a6ba8c7(#13197). Pylon-specific integration keeps its blur host, rollback props, and existing native button styling. RootStackLayout providers remain outside these per-screen boundaries; this PR covers route, sidebar, feed, and inspector render failures.Validation: two React renderer regressions passed (retry preserves a sibling/draft host; route identity reset), mobile typecheck, scoped lint and format checks passed, and independent source review cleared the final patch. Lint reports existing warnings in affected large components. No device UI verification was performed 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.