pls cehck its close multiple time since yesterday last version

Issues/warpdotdev/warp/#16584

pls cehck its close multiple time since yesterday last version

Open

alifailyopened 9d ago

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

pls cehck its close multiple time since yesterday last version

To reproduce

open warp .start claude sessioin then wait some minute its will close by it self

Expected behavior

No response

Screenshots, videos, and logs

No response

Operating system (OS)

Windows

Operating system and version

10.0.26300

Shell Version

No response

Current Warp version

v0.2026.10.14.08.27.stable_01

Regression

Yes, this bug started recently or with an X Warp version

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

No response

Activity

warp-for-oss[bot]9d ago

@alifaily

Here's what I found while triaging this issue:

Thanks for reporting this. This looks like a recent Windows regression involving Claude sessions in Warp, but we need one more piece of evidence to tell whether Warp is crashing, the terminal/session is closing, or Claude Code itself is exiting.

I have a few follow-up questions before I can narrow this down:

Can you attach a short screen recording showing what closes after you start the Claude session?
Can you attach Warp logs from immediately after one failed run, or an AI debugging ID if one is available?

Reply in-thread with those details and the triage workflow will automatically re-evaluate the issue and update the diagnosis, labels, and next steps.

Maintainer details

I concluded that windows stable regression where starting a Claude session in Warp reportedly closes by itself after a few minutes, but more evidence is needed to determine whether Warp crashes, the terminal session exits, or Claude Code terminates..

Triage summary

This looks like a Windows-specific agent/Claude Code bug report on stable v0.2026.10.14.08.27.stable_01. The reporter says that after opening Warp and starting a Claude session, it closes by itself after a few minutes, and marks the behavior as a recent regression that blocks daily use.

Because the issue does not include logs, a debugging ID, or visual evidence, the key ambiguity is what is actually closing: the whole Warp app, the terminal tab/pane, the Claude Code process, or the agent session UI. That distinction changes the likely owner and fix path.

Evidence reviewed

Reported OS: Windows 10.0.26300.
Reported Warp version: v0.2026.10.14.08.27.stable_01.
Reported regression: yes, started recently / with a Warp version.
No comments, logs, screenshots, videos, shell version, or AI debugging ID were provided.
Existing issue search found related Windows/Claude/agent crash or hang reports, including #9899, #8409, #14363, #16091, and #16580, but not two matching open issues with the same sparse reproduction path.

Likely area

The best current routing is area:agent with Windows priority. The relevant client surfaces appear to be CLI agent session tracking and Claude Code integration/plugin lifecycle, but root cause confidence is low until logs or a recording show whether this is a Warp crash, a terminal/session close, or a Claude Code exit.

Suggested next step

Ask the reporter for a short recording and logs/debugging ID from a failed run, then re-triage once the closing mode is clear.

Question reasoning

Can you attach a short screen recording showing what closes after you start the Claude session? — The report says it closes by itself, but a recording is needed to distinguish a full Warp crash from a tab/pane/session close or a Claude Code process exit.
Can you attach Warp logs from immediately after one failed run, or an AI debugging ID if one is available? — Logs or a debugging ID are needed to route the regression between Warp client crash/session handling and Claude Code or agent integration failures.

This is my automated analysis and may be incorrect. A maintainer will verify the details.