feat: add processing activity timeline - #38
Merged
Conversation
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.
Summary
Why
Windy's existing tool events were individually accessible but difficult to follow as one processing flow. The transcript did not provide a prominent running state or a compact completion summary, and newly completed turns did not persist their elapsed time.
The new presentation uses the structured events Windy already receives. It does not make an additional model request and does not consume extra model tokens to summarize activity.
User impact
Working…activity sectionRan npm test,Edited src/ui/MessageListRenderer.ts, andSearched the web for ...Worked for 1m 42sValidation
npm run typechecknpm test— 94 tests passednpm run buildScreenshots
Pending in this draft. The active local Obsidian installation currently includes the unmerged pasted-image work from PR #36, so this branch was not deployed over it with a main-based build.
Closes #37