Question for users of such tools: can't you ask the LLM at the end of the session to choose the most important parts of the context, compress it using your favourite tool, then decompress at the beginning of the next session?
Question for users of such tools: can't you ask the LLM at the end of the session to choose the most important parts of the context, compress it using your favourite tool, then decompress at the beginning of the next session?
This is basically what the OP is doing - just think of this of the cursor rule as a summary (aka a compression) of the session.
I did something similar for a small vibe-coded app. After a few back and forths to develop the first working version, I asked the LLM summarize the requirements and state of the app so far. I saved that summary into a `description.md` file, and can include it in a fresh conversation.
I was using simonw's llm so adding a new feature or making a change looks like:
`llm -f description.md -f code.py "Instructions for making another change."`