You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: improved visual position indicator for subagent sessions #9989
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Problem
The header component facilitates navigation between subagent sessions but lacks visual context regarding the user's current position and the total number of sessions. Users cannot identify which specific subagent is active relative to others in the stack.
Proposed Solution
Enhance the header to include a position indicator and adjacent session metadata. This provides immediate orientation within the navigation cycle (Parent → Child 1 → Child 2 → Parent).
Technical Requirements
Modify the header component to derive the following state from existing session data:
Current Index:children().findIndex(s => s.id === route.sessionID) + 1
Total Count:children().length
Adjacent Metadata: Retrieve names for children[index - 1] and children[index + 1] to provide context for navigation buttons.
UI Specifications
Indicator: Insert a "Current/Total" (e.g., "2 / 5") text element or a horizontal dot-based indicator.
Placement: Position the indicator between the "Subagent session" label and the navigation buttons.
Contextual Labels: Display the names of the previous and next agents near the navigation controls to clarify the destination of the "back" and "forward" actions.
Activity
github-actions commentedon Jan 22, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
feat: add position indicator to subagent session header
adamcbrewer commentedon Feb 13, 2026
I've implemented this for the TUI here:https://github.com/adamcbrewer/opencode/tree/feat/9989-subagent-session-pagination. However I'm pretty new to opensource contributions and need a bit of hand holding submitting my first one to this project. Should my PR target the branch from my fork to this project's
dev?github-actions commentedon Apr 15, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.