Repository navigation
Refactor chat history into a dated thread archive - #504
Merged
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.
Design
The previous sidebar gave New thread and Project workspace equal billing and clipped conversation titles to a single line. This change gives the history panel an illustrated cover based on the Cortex aperture, a prominent New thread button, and a fixed footer for the workspace. The cover uses an original 74 KiB local WebP and system typefaces.
Custom groups appear first. Unfiled threads follow in month and year sections, with localized dates and room for two-line titles. Search shows its match count and reveals results in collapsed groups. Legacy conversations with unreadable dates remain accessible. On short screens the move menu opens toward the available space and scrolls internally.
Verification
npm run typecheckandnpm run buildpassed.npm run lintcompleted with the same two existing warnings inuseModelJobs.tsseen on the base revision.npm test -- --maxWorkers=4passed all 1,236 tests across 93 files.npm run e2e -- --workers=1 --retries=1passed all 44 Chromium tests on their first attempt.Compatibility and rollback
All grouping and date formatting happen in the frontend. Existing chat and group records, navigation, and API calls retain their current contracts. Reverting the commit restores the previous panel without a data migration.