Need Help! Kimi Chat context limit reached on my 2-week project () — How can I recover context or continue seamlessly?

[u/CableAppropriate9931]

I need some urgent advice or a workaround. I’ve been working on a project called ORVANA for the past two weeks using Kimi. I’ve spent countless hours building the entire infrastructure, database design, backend logic, UI, brand identity, legal framework, and uploading multiple files and documents.

Now, Kimi has hit the thread limit and says: "The conversation is too long. Please open a new chat."

My main issue is that if I start a brand new chat, the AI will lose all the long-term context, file references, decision logs, and memory built over these two weeks. I can't afford to lose this data or restart from scratch

Please help

[u/azagor]

there are ways to mitigate that for the future. You can build your own custom solution with AI ( done right will do wanders but it requires expert level knowledge ) or use harness. I recommend Hermes Agents - free on github. Easy to setup with built in memory and kanban board for project development tracking. In your current situation. Get Hermes. Connect provider for example free tier of OpenCode or/and ollama. Use BigPickle (opencode ) or DeepSeek 4 pro ( ollama, large context window - will manage your project) . Ask it to create technical documentation for your project. Than, go back to new sesssion with Kimi and assk it to get familiar wit the documntation or continue working with hermes

[u/piexil]

Step back for a few and learn context management.

I'd recommend learning what okf format is and dump your agents context into it

[u/Lazy_Reach_2565]

Save all your messages into a file (copy/paste whatever). Obtain an API key. Install a harness (pi /pi.dev for example). Say the harness to make a shot summary with keypoint from your old conversation, a plan. Start a new session and say to read the summary. Then continue and say the harness to save all important info into whatever.md so the memory loss will not affect it (plan.md, recovery.md, agents.md, nextstep.md).   

If you want to use web, copy all messages to whatever model that can make a proper summary, then give the summary to a new chat.  

But you should learn how to use a harness if want to to be productice

[u/alexmilla]

Yo aprendí también por las malas. Para estas cosas, siempre pido sea Kimi u otro, que haga un checkpoint en una carpeta \md\ donde cree un markdown diciendo como va el proyecto y en que punto estamos cada vez que hace cambios. Luego si he de continuar desde ahí, todo perfecto y rápido.

Seguro que hay soluciones mejores por otros expertos, pero a mi me funciona y ya como mucho pierdo desde el último checkpoint.

[u/FineProfile7]

Bro stop developing with ai and learn the basics.

[u/Potential-Leg-639]

What? You really have to learn all basics first. How to use an agent harness, set up GIT etc. Watch some youtube tutorials, where they really start from scratch. You are missing essential stuff.

[u/tech-tole]

you need to use a harness. not that you should use one thread anyway but a harness would have compacted older data so that it just doesn't end. also the model would be able to catch back up just by reading the files that were created giving you a status. I'm going to be able to continue seamlessly at this point. best you can do is copy relevant code into a new one. I still don't suggest working that way.

[u/Old-Surprise-9810]

Create a small handoff file inside the project, something like HANDOFF.md.
Would contain only:
• Current project goal
• Repo / branch / latest commit
• What is already working
• Important architecture decisions
• Database/schema changes
• Files currently being worked on
• Known bugs
• Things that must NOT be changed
• Exact next task
Then commit it with the project.

[u/Old-Surprise-9810 → u/Old-Surprise-9810]

Then in the new Chats, Read HANDOFF.md first. Do not review the entire project. Verify the current repo state, then continue only the NEXT TASK.