claude-code - 💡(How to fix) Fix Claude forgets actions performed earlier in the same session (intra-session amnesia)

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Claude forgets actions and discoveries made earlier in the same conversation session (not across sessions — within the same context window).

Error Message

Category: logic-error

Root Cause

Claude forgets actions and discoveries made earlier in the same conversation session (not across sessions — within the same context window).

RAW_BUFFERClick to expand / collapse

Bug Report

Category: logic-error Severity: Major Claude Code Version: 2.1.84 OS: Windows 11 Pro

Description

Claude forgets actions and discoveries made earlier in the same conversation session (not across sessions — within the same context window).

Example (happened today)

  1. Claude discovered gh.exe was not in bash PATH
  2. Claude downloaded gh CLI zip (~50MB), extracted it, verified it works at /c/work/output/gh_cli/bin/gh.exe
  3. 10 minutes later in the same session, Claude tried to install gh again
  4. Only after a find command did it discover gh was already at C:\Program Files\GitHub CLI\gh.exe
  5. User: "asa memorie scurta ai?" ("such short memory?")

Expected Behavior

Within the same session, Claude should remember:

  • Tools it installed or discovered
  • Paths it verified
  • Configurations it set up
  • Errors it encountered and fixed

Actual Behavior

Claude loses track of earlier actions in the same conversation, especially when:

  • Multiple sub-agents are spawned (each agent has isolated context)
  • The conversation is long (1M context but attention may degrade)
  • The action was performed inside a sub-agent that "died" after completion

Impact

  • Duplicate work (reinstalling, re-downloading, re-discovering)
  • User frustration and loss of trust
  • Wasted tokens and time

Suggested Fix

  1. After any significant action (install, configure, discover), write a brief note to a scratch file or memory
  2. Before performing install/configure actions, check recent conversation context for similar actions
  3. Sub-agents should persist discoveries back to the parent context

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING