[Bug]: Session context get's lost/forgotten if i leave it for a while

[jnortheastfilms]

Before submitting

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

Area

apps/web

Steps to reproduce

1. Create and use a session (claude Opus 4.7)
2. After a while of not using that session (1hr +) i go back and send another prompt and it seems to of lost all the previous history of that session, even though i can see all the previous chat history

Expected behavior

Remember my session by reading all the chat history if it goes stale for a while

Actual behavior

Reponse after I prompt it:

"I don't have context from a prior session — this conversation just started..."

Impact

Major degradation or frequent failure

Version or commit

0.0.20

Environment

Windows

Screenshots, recordings, or supporting files

Workaround

Ask the model to read this current chat.

[SPOOKEXE]

Same issue but ~20 minutes using AppImage (Linux Mint)

[shardmods]

Same on MacOS just barely and happens repeatedly.

[shardmods]

another example

[davidyosefdayan]

I have this same issue (MacOS). When I checked the Claude Code VS Code Extension, I see that the last massages where created in an entirely new chat thread.

In T3 Code, its one thread:

In Claude Code Extension, it started a whole separate chat thread:

[juliusmarminge]

hmm so it's an issue in claude code itself? this commit (721b6b4) should have fixed all t3code related issue with session reaping removing the bindings. so it seems like this has now escalated to a bug in claude code that even if we pass the same session id it removes the session?

[emmapowers]

I'm running into this issue probably five or six times a day, it seems to be a regression from 0.17.0 (could also be a claude code upgrade). The conversation files still exist, and you can ask the model to go and find them, but you usually have to tell it to go search the conversations in the current worktree.

The last time this happened I had the model do some digging and produce a summary: https://gist.github.com/emmapowers/ae21cfd1e68d17fce86c1e189244356c

Hopefully that's helpful.

[shardmods]

this was fixed for me when i asked opus 4.7 why it happened, i don't know if i just haven't ran into it yet. what i did was i built t3.code from source since there was a pr (#2125) which fixes this, but claude told me that it's not in the latest build / update yet.

[hwanseoc]

related to #2121

[shardmods]

related to #2121

yes, that's solved by the pr, but (at least according to claude,) the fix for that isn't in the latest build version

[shardmods]

the pr was merged 4 days ago, while the last build is 5 days ago.

[zayenz]

For me, the "lost sessions" (codex, macOS, t3 code version 0.20) generally happens after a "Checkpoint capture failed" error has been shown.

[maxktz]

this bug really makes it unusable for me

if you do claude --resume in the terminal, you can see that single t3 code session gets split into 2 claude chats, new one with no context, and the old one that has your whole conversation

result.mp4

T3 Code: 0.0.20 (b2cca674dfdf)
OS: macOS Tahoe 26.3 (25D125) arm64
Kernel: Darwin 25.3.0

[RyKaT07]

Same issue on my side.

The agent asked whether I wanted it to fix an image copy ordering bug and manifest path. I confirmed with "yes, please." Instead of proceeding with that fix, the agent pivoted entirely and configured a Caveman statusline (reading and editing ~/.claude/settings.json).

After the wrong task completed, I asked the agent: "can you read the current chat?" It confirmed it could, but then provided an incomplete/incorrect summary. It omitted the original bug-fix request entirely, only acknowledging my confirmation message and the statusline configuration it had just performed.

T3 Code: 0.0.20 (b2cca674dfdf)
OS: macOS 26.4.1 (25E253) arm64
Kernel: Darwin 25.4.0