# Regression: Agent terminals no longer support sudo or interactive input

**URL:** <https://forum.cursor.com/t/regression-agent-terminals-no-longer-support-sudo-or-interactive-input/136719>\
**Category:** Bug Reports\
**Created:** [October 8, 2025, 8:26pm UTC](https://forum.cursor.com/t/regression-agent-terminals-no-longer-support-sudo-or-interactive-input/136719 "2025-10-08T20:26:59Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![BSchoolland](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/bschoolland/32/17865_2.png) [@BSchoolland](https://forum.cursor.com/u/BSchoolland)\
**Post date:** [October 8, 2025, 8:26pm UTC](https://forum.cursor.com/t/regression-agent-terminals-no-longer-support-sudo-or-interactive-input/136719/1 "2025-10-08T20:26:59Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

When the agent attempts to run sudo commands, it fails with the following error message:

```auto
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required

```

### Steps to Reproduce

Ask the agent to run any command requiring sudo or any command requiring user input, click allow if needed.

### Expected Behavior

The expected behavior is for the terminal to pause and await user input, I would manually enter my password for sudo, “y” for confirmation prompts, or any other required information. This was last working in 1.5

### Screenshots / Screen Recordings

 ![CopyQ.eYluto.png](https://us1.discourse-cdn.com/cursor1/original/3X/7/c/7ca3ea112e4bf6a4d254998195c21978de6cc380.png)

### Operating System

Linux

### Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.39  
VSCode Version: 1.99.3  
Commit: a9c77ceae65b77ff772d6adfe05f24d8ebcb2790  
Date: 2025-10-08T00:33:20.352Z  
Electron: 34.5.8  
Chromium: 132.0.6834.210  
Node.js: 20.19.1  
V8: 13.2.152.41-electron.0  
OS: Linux x64 5.15.0-157-generic

### Additional Information

I expect that this is closely related to this issue:

> [@Agents terminals are read only](https://forum.cursor.com/t/agents-terminals-are-read-only/133818?page=3&utm_source=chatgpt.com):
>
> Hi, I’ve noticed that the agent terminal is now read-only, and this has become a problem. Many times, the agent successfully starts a server, but it doesn’t kill the process when needed. Since I can’t run commands directly in the agent’s terminal anymore, I have to manually find the process running on the local port and kill it with kill. This workflow feels inefficient, and I don’t think it should be like this. Why is the agent terminal read-only now? Is this an intentional change?

An ideal fix would be to add a toggle to revert the terminal to pre-1.6 behavior.

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [October 9, 2025, 5:15am UTC](https://forum.cursor.com/t/regression-agent-terminals-no-longer-support-sudo-or-interactive-input/136719/2 "2025-10-09T05:15:32Z")

</div>

Hey, thanks for the report. Does enabling this option fix the issue?

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/0/d/0d4367b8467c177a09bf6261036cc49e370dbed9.png)

---

<div class="post-metadata">

**Author:** ![chand\_priyankara](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/chand_priyankara/32/82856_2.png) [@chand\_priyankara](https://forum.cursor.com/u/chand_priyankara)\
**Post date:** [October 12, 2025, 4:01am UTC](https://forum.cursor.com/t/regression-agent-terminals-no-longer-support-sudo-or-interactive-input/136719/3 "2025-10-12T04:01:47Z")

</div>

but why?

---

<div class="post-metadata">

**Author:** ![David\_Branca](https://avatars.discourse-cdn.com/v4/letter/d/e9c0ed/32.png) [@David\_Branca](https://forum.cursor.com/u/David_Branca)\
**Post date:** [October 12, 2025, 5:54pm UTC](https://forum.cursor.com/t/regression-agent-terminals-no-longer-support-sudo-or-interactive-input/136719/4 "2025-10-12T17:54:14Z")

</div>

I can confirm this does cause the terminal session to promtp for the sudo password, rather than skipping over it.

---

<div class="post-metadata">

**Author:** ![BSchoolland](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/bschoolland/32/17865_2.png) [@BSchoolland](https://forum.cursor.com/u/BSchoolland)\
**Post date:** [October 15, 2025, 9:13pm UTC](https://forum.cursor.com/t/regression-agent-terminals-no-longer-support-sudo-or-interactive-input/136719/5 "2025-10-15T21:13:04Z")

</div>

I didn’t see this option before, but this totally fixes it. Thanks!

---

<div class="post-metadata">

**Author:** ![Miguel\_Sedek](https://avatars.discourse-cdn.com/v4/letter/m/8797f3/32.png) [@Miguel\_Sedek](https://forum.cursor.com/u/Miguel_Sedek)\
**Post date:** [November 1, 2025, 1:13pm UTC](https://forum.cursor.com/t/regression-agent-terminals-no-longer-support-sudo-or-interactive-input/136719/6 "2025-11-01T13:13:44Z")

</div>

this does not solves anything

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [November 23, 2025, 1:14pm UTC](https://forum.cursor.com/t/regression-agent-terminals-no-longer-support-sudo-or-interactive-input/136719/7 "2025-11-23T13:14:01Z")

</div>

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.
