fix(web): render working state as turn header - #105
Merged
Conversation
Align the Working row with the active-turn header placement adopted from upstream. Remove the obsolete live-tail marker and padding, and cover the rendered row order and header surface.
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.
Problem
Pylon adopted upstream's active-turn header ordering but kept its older live-tail Working marker and composer-clearance padding. The animated marker therefore appeared in the middle of streamed assistant output and made the timeline look out of order.
Fix
user → Working → assistantorder and header stylingThe timeline derivation and intentional subagent launch anchors are unchanged.
Verification
vp test run --dir apps/web/src/components/chat MessagesTimeline.test.tsx MessagesTimeline.logic.test.ts— 80 passedvp run -F @t3tools/web typecheckvp fmt --check apps/web/src/components/chat/MessagesTimeline.tsx apps/web/src/components/chat/MessagesTimeline.test.tsxvp lint— no errors; one existing unused-import warningEvidence
Before
After
Model:
openai-codex/gpt-5.6-solHarness: Prime Agent
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.