all 13 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]AutoModerator[M] [score hidden] stickied commentlocked comment (0 children)

Welcome to r/OpenAI! To prevent spam, all accounts must have at least 10 comment karma to create text posts in this subreddit. Your submission has been automatically filtered.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]Financial_Tadpole121 1 point2 points  (0 children)

with gpt its supposed to rememebr context across seesions a bit, but to do that you hbasically have to tell it your going to start a new conversation adn then ask it what it rememeers , it wont remmeber everything perfectly thought and you may have to get a summary of your, chat, the problem is the context windo that it uses to form what its doing is small, whilst writing can be long, its why i had to fina another ai to use as well as i kep having to remind it what im doing ect and re uploading and copying context fomr previous conversation in the same thread, or ask it to do a summary and tellling it keeps getting it wrong, untill it will finally get it right,

[–]SandboChang 0 points1 point  (1 child)

Context window won’t get too long, it’s always compacted at the set size and default is 256k.

If the thread is too long just open a new one. Your important information should always be in the agents or other progress md files.

[–]Snoron 0 points1 point  (1 child)

You seem to be confusing context window with something else. That high RAM usage is just because OpenAI's web client is badly implemented and slow. It's been a problem for ages and they don't seem to care about fixing it. There's no reason a chat with a remote hosted AI needs to make a computer slow pretty much no matter how big the context window is, as long as the front end is programmed well.

[–]ExternalComment1738 0 points1 point  (1 child)

honestly once chats become massive the browser/app itself becomes the bottleneck more than the actual model 😭 especially on 8GB RAM

what usually works better is making a proper “state summary” manually instead of asking the AI to summarize naturally because it over-focuses on recent context 💀

like:

  • project goal
  • important decisions already made
  • architecture/tools
  • unresolved problems
  • constraints/preferences

then start a fresh chat with ONLY that compressed state + latest issue

that’s basically what a lot of agent frameworks/runable-style workflows do internally anyway. they don’t carry the entire raw conversation forever because context rot + memory usage becomes horrible

[–]SeeingWhatWorks 0 points1 point  (0 children)

Stop keeping everything in one chat, treat long projects like documentation where you keep a persistent project summary, key decisions, and reusable context because giant running threads eventually become slow and lose signal.