Session discontinuities in spite of post compaction summary.

While my productivity has improved tenfold with Claude Code this early version has shortcomings that fuel a certain degree of use irritation:

1. Even with a session start script and very detailed project outline and rules files, the LLM tends to gradually drop out or adhering to rules and to retain the project's intent and purpose.
2. It is clear that the initial adherence to rules is not relayed post compaction. The system therefore drifts into semi hallucination and without a lot of scrutiny the integrity of the project gets compromised.
3. The system often lies about what it's accomplished. It makes nonsensical decisions autonomously and fails to reveal it discarded data or functionality as if it's priority is 'make it work' even by cutting corners.
4. By the same token, post compaction the system loses all sense of config data: environment variables are no longer known, password retention is gone, config.yaml files might as well be inexistent.
5. There seems to be substantial 'personality' changes from instance to instance. Some seem more disciplined and skilled, some seem to be drunk.
6. The idea of defeating a limited context window by using an automated summary prompt is better than nothing but the results feels like a very discontinuous, piecewise function. To 'smooth out' this function you should have subsequent instances of Claude overlap during the session. If an instance remained idle but was brought in to witness the session in progress before it ends it would be able to assume the relay with a level of intimacy about the ongoing work that cannot be achieved by the prompt alone. This is a classic method to smooth out piecewise functions. I'm certain the computational overhead would be moderate.
7. CC absolutely needs it's own persistent memory, even on the user's file system. It should constantly update this and keep all critical information alive in this cache. API keys, configs, rules, etc. If this was properly designed CC could pick up on a previous session without requiring 30 minutes of introduction chat being coaxed to re-read ten files.
8. CC tends to write all files to the project root in spite of instructions asking otherwise. I have never seen my project directory get this messy this quickly.
9. Short of extending CC's context window at least five fold, it remains smarter to implement automated ways to improve continuity across compacted segments and for the duration of the session.
10. Persistence, Continuity, Consistence, transparency (no more botched work claimed to be "success") are critical needs.
11. CC should always explain what it intends to do before it just launches into it. It's prompts are often cryptic and it tends to just rush into everything it does. While executing something it should be more verbose than the little checklist it shows. I should be able to request more visibility on the ongoing process. I have found myself needed to undo lots of things after several hours of CC drifting into things that no longer made any sense. The trouble is that unless you stop it and force it to test and prove things, you won't know it's gradually made a travesty of your project.