Searching another user's home dir

[spudtrooper]

Pre-submit Checks

• I have searched Warp bugs and there are no duplicates
• I have searched Warp known issues page and my issue is not there
• I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
• I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions

Describe the bug

While making a request to an agent, they appear to have tried to search an unknown user's home dir -- /Users/joshmedeski/repos/guitar-height/. Seems like it could be a privacy issue.

To reproduce

Don't know

Expected behavior

Shouldn't leak private information to other users

Screenshots, videos, and logs

Operating system (OS)

macOS

Operating system and version

26.3.0

Shell Version

zsh 5.9 (arm64-apple-darwin25.0)

Current Warp version

v0.2026.02.18.08.22.stable_02

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

feb 22

Additional context

No response

Does this block you from using Warp daily?

No

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

[szgupta]

Hey @spudtrooper, thanks for reporting this. We've seen LLMs hallucinate directories before and I think that might be happening here. To be sure though, can you share the conversation ID for this interaction? You can find the conversation in the left panel conversation list view

[spudtrooper]

https://app.warp.dev/conversation/c4dd90c0-c865-443f-a9e2-3f1d613c38a6

[szgupta]

@spudtrooper confirmed that this was indeed a hallucination; your conversation's context was not polluted with someone else's context. What happened here was that the context window was summarized and the subsequent request post-summarization did not include your environment context (e.g. current working directory). We have a fix in-flight for that. Sorry for the scare.

[spudtrooper]

Thanks for the explanation. Definitely not the first time I’ve had to chalk up the scary and unexplained to a hallucination: sure it won’t be the last. Jeffrey Palm --> http://jeffpalm.com

…

On Mon, Mar 2, 2026 at 10:24 PM Suraj Gupta ***@***.***> wrote: *szgupta* left a comment (warpdotdev/Warp#8757) <#8757 (comment)> @spudtrooper <https://github.com/spudtrooper> confirmed that this was indeed a hallucination; your conversation's context was not polluted with someone else's context. What happened here was that the context window was summarized and the subsequent request post-summarization did not include your environment context (e.g. current working directory). We have a fix in-flight for that. Sorry for the scare. — Reply to this email directly, view it on GitHub <#8757 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADYRQEXRG5QDWOWWU22KFD4OZF5VAVCNFSM6AAAAACV56GRP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSOBYGM4TONJWGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>