fix: change subagent navigation order to newest-to-oldest#5680
Merged
rekram1-node merged 1 commit intoanomalyco:devfrom Dec 17, 2025
Merged
Conversation
terakael
pushed a commit
to terakael/opencode
that referenced
this pull request
Dec 23, 2025
- Add [current/total] indicator in session header to show position among siblings - Extract sibling-finding logic into sync.session.siblings() helper - Use descending sort (chronological order: main, sub1, sub2, ...) - Navigation: shift-right goes main → sub1 → sub2 → main - Display: main shows [1/N], first subagent [2/N], etc. This reverts the navigation order change from PR anomalyco#5680 (commit 1b39199) which had reversed subagent navigation to newest-to-oldest. The original chronological ordering is more intuitive for tracking subagent hierarchy.
rekram1-node
pushed a commit
that referenced
this pull request
Dec 27, 2025
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
2 participants
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
When a subagent spawns and you want to navigate to it to view it's progress, the natural intuition is to go to "the next subagent" at least for me - this ends up in me going to the oldest subagent which feels weird
Swaps the ordering so newest is first, and also removes localCompare as it's not needed for the ID comparison