Pre-submit Checks
Describe the bug
Warp Agent Mode - Critical Memory Loss Bug Report
Date: 2025-10-09 14:52:53Z
Severity: Critical
Impact: High - Disrupts active development work
Issue Description
Agent Mode is experiencing complete loss of conversation context mid-conversation, causing the agent to forget previous work and context within the same session.
Reproduction Steps
- Start a conversation with Agent Mode
- Work on a specific task or issue with the agent
- Continue the conversation - agent suddenly loses all memory of previous exchanges
- Agent claims conversation "started" with the most recent message, ignoring all prior context
Expected Behavior
Agent should maintain full conversation context throughout the entire session, remembering all previous exchanges, work performed, and context established.
Actual Behavior
Agent completely loses access to earlier parts of the conversation mid-session, claiming the conversation "began" with recent messages and having no memory of prior work or context. This happens much before reaching context window, sometimes 4 commands into a simple session with no external data loaded.
User Impact
- Severe workflow disruption: Forces users to re-explain context repeatedly
- Lost productivity: Work progress is interrupted and must be restarted
- User frustration: Creates unreliable development experience
- Trust erosion: Users cannot rely on the agent to maintain context
Technical Details
- Platform: macOS
- Shell: zsh 5.9
- Frequency: User reports this "happens often"
Specific Instance
In this session, user was working on a PostgreSQL-related issue with the agent. Mid-conversation, agent lost all memory of the prior work and claimed the conversation started with "did you fix the issue with postgresql?" when there had been significant prior context and work.
Recommended Actions
- Immediate investigation of conversation context management system
- Review session state persistence mechanisms
- Implement safeguards to prevent mid-conversation memory loss
- Add logging to track when and why context is lost
- User notification system if context loss is detected
Priority
This should be treated as a P0/Critical bug as it fundamentally breaks the core functionality of maintaining conversational context, severely impacting user experience and productivity.
To reproduce
use agent mode
Expected behavior
agent remembers conversation
Screenshots, videos, and logs
No response
Operating system (OS)
macOS
Operating system and version
15.6.0
Shell Version
zsh
Current Warp version
v0.2025.10.01.08.12.stable_02
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None
Pre-submit Checks
Describe the bug
Warp Agent Mode - Critical Memory Loss Bug Report
Date: 2025-10-09 14:52:53Z
Severity: Critical
Impact: High - Disrupts active development work
Issue Description
Agent Mode is experiencing complete loss of conversation context mid-conversation, causing the agent to forget previous work and context within the same session.
Reproduction Steps
Expected Behavior
Agent should maintain full conversation context throughout the entire session, remembering all previous exchanges, work performed, and context established.
Actual Behavior
Agent completely loses access to earlier parts of the conversation mid-session, claiming the conversation "began" with recent messages and having no memory of prior work or context. This happens much before reaching context window, sometimes 4 commands into a simple session with no external data loaded.
User Impact
Technical Details
Specific Instance
In this session, user was working on a PostgreSQL-related issue with the agent. Mid-conversation, agent lost all memory of the prior work and claimed the conversation started with "did you fix the issue with postgresql?" when there had been significant prior context and work.
Recommended Actions
Priority
This should be treated as a P0/Critical bug as it fundamentally breaks the core functionality of maintaining conversational context, severely impacting user experience and productivity.
To reproduce
use agent mode
Expected behavior
agent remembers conversation
Screenshots, videos, and logs
No response
Operating system (OS)
macOS
Operating system and version
15.6.0
Shell Version
zsh
Current Warp version
v0.2025.10.01.08.12.stable_02
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None