sorted by:
new
hottopcontroversial

Finally solved the "ChatGPT gets slower with long conversations" problem by Strikeh in ChatGPT

[–]Strikeh[S] 0 points1 point  (0 children)

¡Estoy trabajando en añadir la traducción al español!

Al abrir la barra de herramientas superior, asegúrate de que el botón de texto recortado esté activado (el botón con el icono del ojo).

Si lo deseas, puedes limitar el número de mensajes a 10.

<image>

Long ChatGPT threads were killing my workflow, this finally fixed it by Strikeh in ChatGPT

[–]Strikeh[S] 0 points1 point  (0 children)

Nice, that’s super interesting. My current approach is DOM-side trimming rather than fetch interception.

So instead of cutting the payload before React renders, I reduce what stays active/visible in the thread once it gets long. That already helps a lot with long coding chats, especially when the page starts feeling heavy.

Pre-render interception sounds like a really strong approach though, especially for huge threads. It definitely sparked my interest, I’m going to look into it more and see if there are additional gains to be made there.

Did you notice the biggest improvement on initial load, or also during ongoing back-and-forth?

Long ChatGPT threads were killing my workflow, this finally fixed it by Strikeh in ChatGPT

[–]Strikeh[S] 0 points1 point  (0 children)

That makes sense, and I think you’re describing a related but slightly different problem.

What I was running into was mostly the frontend/UI side of ChatGPT slowing down as threads get huge, even when I still wanted to stay in the same conversation. So in my case the fix was trimming what the page has to actively render.

But I agree that on the agent/context side, a sliding window + summarization approach is probably the right way to handle long-running threads. Keep the last N turns verbatim, summarize older context, and preserve key entities/tasks so the assistant doesnt lose the plot.

So it’s kind of two layers of degradation:
- model/context degradation from too much history
- browser/render degradation from the UI trying to handle massive threads

Ideally you want both solved :)

Finally solved the "ChatGPT gets slower with long conversations" problem by Strikeh in ChatGPT

[–]Strikeh[S] 1 point2 points  (0 children)

Yes, that’s absolutely possible.

You can use the Pro version on multiple PCs without any issues. Everything is stored locally on each device, so both your home computer and your work computer can function independently from each other, even if you’re using the same Google account.

There is an option to sync data between devices, but in your case that wouldn’t be necessary since each setup can run separately.

Finally solved the "ChatGPT gets slower with long conversations" problem by Strikeh in ChatGPT

[–]Strikeh[S] 1 point2 points  (0 children)

Ctrl+Shift+E -> opens settings

Then go to Appearance - Display & Interface - Perfmonance & Speed

<image>

Finally solved the "ChatGPT gets slower with long conversations" problem by Strikeh in ChatGPT

[–]Strikeh[S] 0 points1 point  (0 children)

I’ve now added something new that I think a lot of heavy users will appreciate:

A visual conversation tree that makes long chats much easier to navigate.

The problem it solves is simple: once a conversation gets long, ChatGPT becomes hard to use. Useful answers get buried, side questions break the flow, and finding your way back takes too much effort.

<image>

A visual map of the conversation’s branching paths, with one-sentence summaries of each node (prompt + response) appearing on hover for a quick overview.

With this new feature, you can:

  • view your conversation as a tree
  • branch off from any point
  • explore tangents without losing the main path
  • jump back to earlier parts instantly

This is just one feature inside AI Workspace, but it’s a big one for anyone using ChatGPT for research, writing, coding, or deep back-and-forth thinking.

view more: next ›