[ENHANCEMENT] Sticky sub tasks

[lmtr0]

Problem (one or two sentences)

When you continue the current task in roo code, and need to scroll up to see previous user messages, you often have to scroll a lot.

Context (who is affected and when)

Users who interact with the Roo interface and work together with the agent.

Desired behavior (conceptual, not technical)

Make the last message stick to the top:

And when you click it, it will scroll the UI to that message and pin the other last message to the top.

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote]

I've analyzed this issue and here's my proposed implementation plan:

Problem Understanding

When working with long conversations or subtasks in Roo Code, users have to scroll a lot to navigate between their messages. The request is to add a sticky navigation element that helps users quickly jump back to recent user messages.

Proposed Implementation

1. Create a new StickyUserMessageNav component

• A lightweight sticky banner at the top of the chat view (below TaskHeader)
• Shows when user scrolls up past the most recent user message
• Displays a truncated preview of the last user message with a click-to-scroll action
• Clicking scrolls the view to that message and updates to show the next previous user message

2. Modify ChatView.tsx

• Track user message positions during rendering
• Detect scroll position relative to user messages
• Show/hide the sticky nav based on scroll state
• Implement smooth scroll-to-message functionality using Virtuoso's scrollToIndex

3. Add subtask context awareness

• When in a subtask (task with parentTaskId), optionally show parent task info
• This helps users understand the context hierarchy

Technical Approach

• Use react-virtuoso's scroll tracking APIs to detect when user scrolls past messages
• Store an array of user message indices for quick lookup
• The sticky nav would be conditionally rendered above the Virtuoso list
• Use CSS position: sticky or fixed positioning for the nav element

Files to Modify

• webview-ui/src/components/chat/ChatView.tsx - Add scroll tracking and sticky nav integration
• Create new webview-ui/src/components/chat/StickyUserMessageNav.tsx - The sticky navigation component
• webview-ui/src/i18n/locales/en/chat.json - Add translation strings

Benefits

• Minimal performance impact since we're only tracking a subset of messages
• Works for both regular tasks and subtasks
• Non-intrusive UI that only appears when needed

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[lmtr0]

@roomote Looks promising; go ahead! Approved.

[roomote]

Thanks for the approval! Starting implementation now. I'll open a draft PR to share progress shortly.

[roomote]

Opened a draft PR with my attempt at implementing the sticky user message navigation: #10693

The implementation includes:

• A new StickyUserMessageNav component that appears when scrolling up past user messages
• Integration with Virtuoso's rangeChanged callback for scroll tracking
• Smooth scroll-to-message functionality when clicking the banner
• i18n translation strings for accessibility

Feedback welcome!

[M-Kepler]

they will always: closed as no plan
there is less and less people contribute to this repository

so， i have switch to kilocode，it has the feature you wante

[lmtr0]

@M-Kepler This comment makes no sense. Sure, it might be a bit delayed, but there are people working in this repo. Plus it's Roo that's doing all the work. Are you just spamming for us to move to a Roo code's fork, or are you genuine?

[M-Kepler]

they kill lots of good idea, including this issue (whic i have put long ago)

[lmtr0]

@M-Kepler Hm, strange. I'll take a look at kilo code then, thank you!

For any future users, I searched his Issue: #7721