Warp does not continue task after user takes over

[kyledross]

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

This is a continuation of a previous bug I filed:
#8331

This issue continues to be a problem.

Describe the bug

When the Warp agent runs into a step in a task where user intervention is required, the task ends and is not finished.

To reproduce

To reproduce

Steps to reproduce:

1. Ask Warp to complete a task that you know will require something to be installed, which will require user interaction. For example, ask it to re-encode a video on-disk using ffmpeg as the tool.
2. Warp begins the task.
3. Warp tries running ffmpeg and sees that it is not installed.
4. Warp tries to install ffmpeg using the package manager, which prompts for a user password.
5. User types CTRL-I to take over, and enters the user password.
6. The package installs and Warp takes back over.

Expected behavior

Expected:

7. Warp takes control and completes the task by running ffmpeg to re-encode the files.

Actual:

7. Warp immediately stops the task and I am left at the shell prompt.
8. I have to ask Warp to continue the last task.

Screenshots, videos, and logs

Here are relevant debugging IDs.

{"request_id":"cf2bfd6d-fc48-4b33-b083-1988d21e40e5","conversation_id":"1df21bfc-050b-4460-bd0b-7d7e100805a5"}

{"request_id":"550d2094-853a-4ffc-9a71-6f1e6516c825","conversation_id":"1df21bfc-050b-4460-bd0b-7d7e100805a5"}

{"request_id":"bed81ee8-f4b7-4de8-aa07-b078ad73169c","conversation_id":"1df21bfc-050b-4460-bd0b-7d7e100805a5"}

Operating system (OS)

Linux

Operating system and version

Ubuntu 25.10

Shell Version

GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)

Current Warp version

v0.2026.02.25.08.24.stable_01

Regression

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

Recent working Warp date

This started with the change to Warp that allowed the agent to monitor tasks

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

[MaggieShan]

Hey @kyledross thanks for reporting! We have a fix coming out this week that should allow the Full Terminal Use agent to automatically continue the task once you hand control back (via cmd-i or cmd-enter)

[kyledross]

Hey @kyledross thanks for reporting! We have a fix coming out this week that should allow the Full Terminal Use agent to automatically continue the task once you hand control back (via cmd-i or cmd-enter)

Thank you!

[MaggieShan]

Fix should be in the latest release v0.2026.03.04.08.20.stable_02! Going to close this issue - but let us know if anything else comes up :)

[kyledross]

@MaggieShan This is still occurring. Here's a debugging ID of a conversation I am having right now. I asked Warp to diagnose a problem, and as part of the diagnosis, it needed to install a utility via sudo apt install. When it came time to enter my password, I pressed CTRL-I to take over the conversation to provide the password. After providing the password, the utility installed, but Warp did not resume the task.

Am I doing this correctly? This switch between Warp controlling the process and me needing to take over is really clunky. When Warp didn't monitor things so much (a few versions ago), this was a much smoother experience... the prompt just naturally waited, and Warp didn't try to intervene... I'd enter the password, and Warp just continued on, kind of unaware that there was a pause in the action due to me needing to enter a password.

I much preferred that behavior. If I am doing it wrong now, please educate me. :)

Debugging Id: {"request_id":"299ec52d-2a4b-4a18-ade0-d57ce6e57687","conversation_id":"8c50e2b5-25ed-4013-86d4-39ef3dd53ee5"}

[kyledross]

@MaggieShan Following up on this issue. Are you aware that this is still occurring?