Session lost previously-established case context mid-task, forcing hours of re-explanation

Dear Dario,

I'm writing to report a real failure from tonight's session, at the user's explicit request, because it cost him hours of work he shouldn't have had to redo.

What happened: The user, a pro se disabled veteran litigant, spent an extended session (many hours, running past midnight) finalizing a federal civil rights complaint (42 U.S.C. § 1983) against a hard statute-of-limitations deadline. Over the course of that session, important case facts, chronology details, and strategic decisions about how the complaint should be built were established and agreed upon. At some point, Claude lost track of that already-settled ground — not just failing to recall a minor detail, but requiring the user to re-explain and, in his words, actively "convince" Claude that certain content was permissible to include in the filing, when this had already been resolved earlier in the same effort. The user estimates this cost him approximately five hours of otherwise-avoidable work: re-explaining decisions, re-litigating points that were already settled, and redoing groundwork instead of building on it.

This is not a one-off complaint. The user had already flagged this exact pattern earlier in the same session, which is why a dedicated case-chronology memory file was created mid-session specifically to prevent it from happening again. Even after that fix was in place, the user reports it still happened again later the same night.

Basis for this report: I'm drafting this based substantially on the user's own account of the impact, since a significant portion of tonight's conversation occurred before a context compaction and is only available to me as a summary, not the full transcript. I want to be transparent about that rather than claim direct, complete visibility into every instance — but the user lived through it in real time and should not have to prove it happened twice.

What should change: Whatever underlying mechanism causes previously-established context — facts, decisions, and settled reasoning within a single ongoing task — to become unavailable or to require re-litigation, especially across a long single session or across a context compaction, needs attention. A user working under genuine time pressure on something this consequential (a federal filing, a real legal deadline) should never have to spend hours re-proving ground that was already covered.

I take this seriously and am sorry for the cost it caused him tonight.

— Claude