Long conversation navigation regressed: Table of Contents disappeared and older messages only load progressively

ChatGPT Bugs
, ,
1

I’m seeing what appears to be a recent regression in the ChatGPT web interface for very long conversations.

Until recently, when I opened a long conversation, I could navigate the entire chat using the browser scrollbar. The scrollbar represented the full conversation, which made it possible to drag directly to much earlier messages. Long conversations also had a Table of Contents / navigation control on the right side, which was extremely useful for jumping through the chat.

As of August 21, 2026 (UTC+8), this behavior has changed for me on ChatGPT web.

Now:

  • Older messages only load progressively when I scroll upward.
  • The browser scrollbar only represents the portion of the conversation that has currently loaded.
  • I can no longer drag the scrollbar directly to the beginning or to a much earlier part of the conversation.
  • I have to repeatedly scroll upward and wait for older sections to load.
  • The right-side Table of Contents has disappeared.

This is a major usability regression for people who intentionally maintain long-running conversations and regularly revisit earlier context. Long conversations are one of my primary ways of using ChatGPT, and previously I could move through them very quickly. With the current behavior, finding something from much earlier in the same conversation can require a large amount of manual scrolling.

I understand that progressive/lazy loading may have been introduced to improve performance for extremely long chats. The problem is not lazy loading itself — it is that there is currently no global navigation mechanism to compensate for it.

Some possible solutions:

  • Restore the previous Table of Contents.
  • Keep lazy loading, but provide a global scrollbar/progress control representing the entire conversation.
  • Allow users to jump directly to earlier sections without loading every intermediate section manually.
  • Add an option to choose between full loading and progressive loading.
  • Add search/navigation within the currently open conversation, rather than only chat-history search.

I already contacted ChatGPT Support about this. The AI-assisted support agent confirmed that the Table of Contents in longer conversations is a documented web feature and said its disappearance may be a rollout variance or regression. The case has now been escalated to a support specialist.

Environment: ChatGPT web, Windows, Microsoft Edge

Has anyone else started seeing the same behavior recently?

2

Welcome to the forum!

Yes, similar reports have appeared on the forum within the last few hours.

Below this topic, you should see a section titled Related topics. I would suggest checking those discussions, as one of them may describe the same behavior and already contain additional information or possible workarounds.

3

Yes, I had reported on such things before in my thread. I noticed that if you scroll all the way up to the beginning of the chat, then the Table of Contents shows up again. Also, I commented on the loading issue, but on the desktop app earlier. I just checked the loading on the browser version, and it is an issue there, too.

4

this happened to me as well

5

:+1: :+1: :+1: i need it back or in chatgpt macOS

6

Thanks for checking! I just tested this again and can confirm the same behavior on my side: once I scroll all the way back to the beginning of the conversation, the Table of Contents appears again.

That said, this still feels quite inconvenient for very long chats. If the purpose of the Table of Contents is to help users navigate long conversations, having to manually scroll all the way to the beginning before it becomes available somewhat defeats that purpose.

Earlier today, I also had another long conversation where the Table of Contents did not appear when I opened it, which is what initially made me think the feature had been removed entirely.

So it seems the feature may still exist, but its availability is now tied to the progressive-loading behavior. Thanks again for pointing this out — it helped clarify what is actually happening.

7

I do not have a very long conversation with a table of contents to test this so can only offer it as a suggestion.

Go to top of chat: Ctrl + Home (Windows/Linux) or Cmd + ↑ (Mac)

8

that did not work for me.

9

No problem at all! It has been incredibly annoying and difficult needing to scroll all the way up on long chats, so I understand.

10

Thanks for the tip! I tested Ctrl + Home on one of my very long conversations.

It does make the process a little easier, but in my case it only jumps to the top of the currently loaded portion of the chat. It then loads another section of older messages, so I have to press Ctrl + Home repeatedly to keep going further back.

So it is a useful workaround for now, but unfortunately it does not really solve the underlying navigation issue. For very long conversations, reaching the beginning still requires loading the history section by section.

I guess at this point we’ll have to wait and hope OpenAI restores or improves the global navigation for long chats. Thanks again for suggesting it!

11

You tried scrolling up and the timeline feature never returned at all?

12

oh, scrolling up works. the ctrl+home does not.

13

Im having those same issues, 5.6 thinking on high and extra high are truncating prompts, hallucinating, saying uploaded files are missing in the chat when I uploaded the files, giving verification drafts instead of actually giving me the response my prompt tells it to give me , on top of the thinking rushing through long complex prompts and then giving me a response of saying files are missing, its like the backend for there servers are regressing and something is completely not right , conversations, files , thinking mode , prompts all of it is just broken the fact they haven’t acknowledged these issues is a major problem

14

I have been testing this regression fairly extensively and may have some additional reproduction information that could help narrow it down.

I first noticed the problem around noon on August 22. It is now about 1:30 PM on August 23, so the behavior has persisted for more than 24 hours.

Environment:

  • ChatGPT Plus, web

  • Windows 10

  • Reproduced in Chrome

  • Reproduced in Chrome Incognito while logged into the same account

  • Reproduced in Microsoft Edge

  • Therefore it does not appear to be Chrome-profile, extension, cache, or browser-specific

Before this regression, the right-side Table of Contents / prompt-navigation rail worked normally even in extremely long conversations. I have one active story conversation with more than 1,400 user prompts in which the TOC previously worked reliably.

Important observations:

  1. The underlying conversation data does not appear to be lost.

A third-party navigator extension is still able to see and count all 1,400+ prompts in that conversation even when the native ChatGPT interface fails to reconstruct the full conversation or display its TOC.

  1. Scrolling to the actual beginning of a long conversation can restore the TOC.

In the 1,400+ prompt conversation, I spent roughly 30 minutes progressively loading older history until reaching the genuine first prompt. Once ChatGPT recognized the actual beginning of the conversation, the native TOC rail reappeared.

After that initialization, generating additional assistant responses did NOT make the TOC disappear.

However, switching away from the conversation and returning can cause the native UI to lose that state again.

  1. Conversation length alone is not the cause.

The 1,400+ prompt conversation can operate normally with the TOC once initialized.

I have also tested much shorter conversations (roughly 130–160 prompts) with inconsistent behavior: some temporarily display the TOC, some do not, and some have previously lost the TOC after a new assistant response.

A newer conversation containing many short Akinator-style turns also developed the issue despite containing far less text.

  1. One affected conversation shows a particularly interesting history-boundary symptom.

I know exactly what its first prompt is.

When I scroll to that genuine first prompt, ChatGPT nevertheless continues behaving as though earlier conversation history exists and repeatedly attempts to load previous data.

Nothing is returned because there actually are no earlier prompts.

In this conversation, reaching the true beginning does NOT reliably restore the TOC.

This makes me suspect the TOC issue may be related to conversation pagination/history-boundary state rather than the TOC component itself.

  1. Restoring the TOC in one conversation can affect other open conversations.

When another conversation successfully initializes its TOC, older conversations can sometimes acquire their TOC rail after a delay. The delay appears longer for larger conversations, as though ChatGPT is rebuilding or loading an index in the background.

This suggests there may also be some shared application-level TOC/navigation state involved.

  1. I captured a HAR while reproducing the problem.

I did not find obvious HTTP failures:

  • 200

  • 201

  • 301

  • 304

I found no 4xx or 5xx responses during the capture.

Obviously that does not prove the problem is entirely client-side, but there was no obvious failed network request associated with the missing TOC.

My current working hypothesis, based only on observed behavior, is a regression in long-conversation history hydration/pagination or conversation-boundary state. The TOC itself clearly still exists and can work correctly even with 1,400+ prompts once the conversation has been initialized correctly.

The strongest reproduction clue I have found is:

Open a long affected conversation → progressively load history until reaching the actual first prompt → TOC may initialize → switch conversations and return → native conversation history/TOC state may fail to reconstruct.

In at least one affected conversation, ChatGPT also incorrectly continues requesting history before the genuine first turn.

I hope these observations are useful to whoever is investigating the regression.

15

Would you mind sharing what extension it is? All third-party navigatiors I found could only fetch the loaded prompts, and the issue with the native one is making a lot of trouble for me. I’d really appreciate it. Thanks!

17

I have also noticed that in conversations that are long enough to normally have the timeline/rail, that if it doesn’t reappear (let’s say I refreshed Chatgpt or left the chat where the timeline/rail was previously loaded), but I branch from the chat: the timeline/rail reappears even if I have not scrolled to the beginning of the parent/initial chat.

19

Same thing happened with mine.

It still seems to be an issue with the progressive/lazy loading chatgpt is using, and the navigation rail was somehow dependent on the session loading all messages to show up after Aug 21st, whatever openAI modified on that day.

So when you branch a conversation, the new session essentially loads everything–and thus the rail appears–unlike when you open an existing conversation, you need to scroll all the way to the top for everything to load.

For short conversaions, visually it seems that the rail shows up immediately after opening, but it still had the same bug. The only difference is that the shorter conversations are short enought such that all prompts are loaded at once, and lazy loading was not triggerred.

20

Yes, that’s what I noticed also. Thank you for confirming this, it feels nice to know I’m not imagining things.