[Bug]: Claude losing earlier messages / not compacting correctly

[benjaminalgreen]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

1. Begin thread with Claude 4.7 on 200K Extra High
2. Send Claude off to do some things
3. Claude reaches max context window
4. Enter new prompt
5. Claude confused because there's no context of previous conversation

Expected behavior

Expected behavior is that when Claude reaches context limit, automatic compaction takes place and Claude continues with compressed context from earlier conversation.

Actual behavior

Claude apparently gets a fresh empty context window, and has no context on earlier conversation.

Impact

Blocks work completely

Version or commit

Latest

Environment

MacOS

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

[JeremieLeblanc]

I can confirm the behaviour also happens on Windows. Both in Opus 4.6 and 4.7
After writing a plan I wrote "Yes, good plan" immediately after it gave it to me and this is the interaction:

10:29:48 AM • 1m 48s Claude: I've written the plan to C:\Users\JeremieLeblanc.claude\plans\i-have-made-changes-peaceful-feigenbaum.md and submitted it for approval. Here's a quick summary of what it proposes: (...)

10:30:11 AM • 22s Me: Yes, good plan

10:35:58 AM Claude: I don't have any prior plan or task context from you yet — your message "Yes, good plan" appears to be affirming something, but there's no plan in this conversation to respond to. Let me ask for clarification.

[elkhoudiry]

I have same issue, but not even a long execution or long sessions, my expreience is:
1- I ask claude to read one documentation file as a prompt
2- I ask it to do something but before doing it, it need to give me execution plan
3- if i take so long and forget about this conversation for an hour or two (it should be still fresh) and tell it to proceed or execute, then claude tells me sorry i don't have context this is a fresh conversation

[matty]

Ahh! I thought I was going insane... this is happening for me also.

[sean35mm]

Yes, experiencing the same thing for me

[JuanTrujilloAlternova]

Happening the same on Mac OS with Opus 4.7.

[benjaminalgreen]

I can confirm the behaviour also happens on Windows. Both in Opus 4.6 and 4.7 After writing a plan I wrote "Yes, good plan" immediately after it gave it to me and this is the interaction:

10:29:48 AM • 1m 48s Claude: I've written the plan to C:\Users\JeremieLeblanc.claude\plans\i-have-made-changes-peaceful-feigenbaum.md and submitted it for approval. Here's a quick summary of what it proposes: (...)

10:30:11 AM • 22s Me: Yes, good plan

10:35:58 AM Claude: I don't have any prior plan or task context from you yet — your message "Yes, good plan" appears to be affirming something, but there's no plan in this conversation to respond to. Let me ask for clarification.

So it seems like it's not even a compacting issue (my original assumption). I assume no one is experiencing this in CC via terminal?

[akarabach]

Probably we need to add extract markdown button, or a button which will "fork" the session - it will be workaround for such kind of cases, not saying that we dont need to fix it

[RaeesBhatti]

Is this an issue with Claude Code or T3Code? I'd rather not go back to Conductor

[matty]

I can confirm the behaviour also happens on Windows. Both in Opus 4.6 and 4.7 After writing a plan I wrote "Yes, good plan" immediately after it gave it to me and this is the interaction:
10:29:48 AM • 1m 48s Claude: I've written the plan to C:\Users\JeremieLeblanc.claude\plans\i-have-made-changes-peaceful-feigenbaum.md and submitted it for approval. Here's a quick summary of what it proposes: (...)
10:30:11 AM • 22s Me: Yes, good plan
10:35:58 AM Claude: I don't have any prior plan or task context from you yet — your message "Yes, good plan" appears to be affirming something, but there's no plan in this conversation to respond to. Let me ask for clarification.

So it seems like it's not even a compacting issue (my original assumption). I assume no one is experiencing this in CC via terminal?

Works fine in CC via terminal for me, I went back to that for now.