Repository navigation
feat: align the default chat view's work log with Narrative - #2101
Merged
Merged
Conversation
Douglasymlai
force-pushed
the
feat/legacy-work-log
branch
4 times, most recently
from
October 24, 2026 15:23
3b5a46e to
11fd6c7
Compare
Douglasymlai
marked this pull request as ready for review
October 24, 2026 16:44
Douglasymlai
force-pushed
the
feat/narrative-task-log
branch
from
October 25, 2026 11:57
c5adc16 to
9bf901a
Compare
Douglasymlai
force-pushed
the
feat/legacy-work-log
branch
from
October 25, 2026 11:57
11fd6c7 to
0d732c8
Compare
1 of 3 tasks
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.
Split out of #1958. Stacked on #2100: please merge after #2100, then retarget this PR to
main.Problem
In the default chat view, the work log under each task described tool calls differently from the Narrative view. Rows read like
Browser Toolkit · Browser visit page · 2 eventsor showed the raw argument text, they had no icon, and the agent and work-log chevrons were always visible. The final answer's text also sat flush against the edge while the rest of the conversation was inset.Cause
The Narrative view's row titles, subjects and icons were only used by the event-based timeline. The default chat view still built its own
Toolkit · Methodtitles.Fix
Known limit: the default chat view only knows whether a call is running or done. A call that failed, or was cut short when a task was stopped, still reads as done here. Narrative shows those states.
Testing
In the app (macOS, default chat view), with Tasks that used the terminal, web search, a web fetch, file writes and Stop:
Automated:
TaskWorkLogAccordionand the new live-language test: all pass. New tests cover:npm run type-check,npm run check:i18n,npm run check:design-tokens, ESLint and Prettier: pass.main(after feat: add the Narrative task log and Information density / Dev mode controls #2100 merges).Testing Evidence