Model loses context and misreads questions in long sessions

Status Fixed / completed
Maintainer reply None cached
Activity 3 comments · opened May 14, 2026 · closed May 14, 2026

Description

In long working sessions (this one was ~4 hours, many tool calls), the model begins misreading straightforward questions. Specific example:

User asked: "do you have access to the IG account?"

Context was clear — we had just discussed using Mima's Instagram photos (@mimasdelicafe) as source material for poster generation. The natural reading is: can we read that account's content?

Model instead checked posting credentials for @dudes.tribe and gave a detailed answer about write access — completely missing the question. Required the user to repeat themselves with frustration before getting a direct answer.

Pattern

  • Later in long sessions the model answers the question it expects rather than the one asked
  • Stops tracking conversational context accurately
  • User has to repeat or rephrase things they already said clearly

Expected behavior

Short, direct answer to the actual question asked, even late in a long session.

Environment

  • Claude Sonnet 4.6 via Claude Code VSCode extension
  • Long session with many tool calls (SSH, file edits, DB queries, deploys)

View original on GitHub ↗

3 Comments

github-actions[bot] · 5 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/48063
  2. https://github.com/anthropics/claude-code/issues/54991
  3. https://github.com/anthropics/claude-code/issues/48028

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

adamcanton · 5 months ago

Closing — filed in error. Internal tracking only.

github-actions[bot] · 3 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.