Repository navigation
Conversation
3 tasks done
Contributor
|
Automated PR Cleanup Thank you for contributing to opencode. Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions. This PR was closed because it matched the following cleanup criteria:
PRs created within the last month are not affected by this cleanup. If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate. Thanks again for taking the time to contribute. |
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.
Issue for this PR
Closes #42498
Type of change
What does this PR do?
When the existing
/timestampstoggle (session.toggle.timestamps) is enabled, each message part now renders its own start timestamp alongside the message-level timestamp:Thought: plan migration · 2.3s · 3:41 PM$ npm run build, reads, greps): appends· 3:41 PMnext to the tool label, in both pending and completed states# Running in packages/tui · 3:41 PMParts already carry
time.startin the protocol, so this is a pure TUI rendering change. The time uses the existingLocale.todayTimeOrDateTimehelper (matches the message-level format: time for today, date+time otherwise).How did you verify your code works?
bun typecheckinpackages/tui(plus full monorepo turbo typecheck via pre-push hook)bun testinpackages/tui: 193 pass, 1 skip, 0 fail (incl. the 17inline-tool-wrap-snapshottests that renderInlineToolRowstandalone — the newtimeprop is optional and theme-free)Screenshots / recordings
N/A
Checklist