codex - 💡(How to fix) Fix Feature request: block-level thread navigation in Codex Desktop (jump to start of latest assistant response) [1 comments, 2 participants]

What feature would you like to see?

I'd like Codex Desktop to support block-level navigation for long chat threads, especially long assistant replies.

Today, there is a convenient way to jump to the bottom of the thread, but there is no equally efficient way to jump to the beginning of the latest assistant response. In long conversations with large replies, this makes it unnecessarily hard to re-read the start of the most recent answer.

Problem

In long threads, users often need to:

• jump to the latest message,
• then move back to the start of that latest assistant response,
• then re-read it from the top.

Right now this requires manual scrolling and visually searching for the response boundary, which becomes slow and frustrating when:

• the thread is long,
• the latest answer is long,
• older messages are also large.

This is not just a generic scrolling issue. It is specifically a missing navigation primitive for message blocks / response boundaries.

Proposed solution

Please add one or more of these:

1. Jump to start of latest assistant response

• A button near the existing "jump to bottom" affordance
• Or a command in the command palette / menu
• Or a keyboard shortcut

1. Previous / next assistant response navigation

• Move between assistant messages as blocks, not by pixel scrolling

1. Optional collapse for older long responses

• Let users collapse previous long assistant answers to reduce scrolling noise

1. Optional visible response boundaries

• Make the start of each assistant response easier to identify visually
• Example: sticky header, clearer separator, or hover anchor

Why this matters

The current UI supports navigation along the full thread timeline, but long-thread usability really needs navigation along message blocks.

For long coding sessions, "jump to latest" is only half the story. Users also need "jump to start of latest response".

Acceptance criteria

A good minimal version would be:

• user can jump to the latest assistant response start in one action,
• action works reliably in long threads,
• action does not require manual scrolling to locate the response boundary.

A stronger version would also include:

• previous/next assistant message navigation,
• collapse/expand for older assistant responses.

Related items

This is related to, but distinct from, existing scrolling/search issues:

• #17193
• #17169
• #17114
• #3020
• Discussion #2503

Those are mostly about scroll bugs, search, or generic message collapsing. This request is specifically about block-level navigation to the latest assistant response.