AI Terminal Lost Interactive Support - Broke My Workflow

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hey Cursor team,

I’ve been using the AI assistant’s terminal to test my installation scripts, and something changed that’s really frustrating. My interactive installer script used to work perfectly through the AI terminal, but now it’s completely broken.

What’s happening:

  • My script has read -p "Enter choice (1, 2, or 3): " prompts for user input
  • Before: I could run this through AI terminal and it would wait for input, let me respond, everything worked great
  • Now: The AI terminal immediately returns empty strings for ANY read command, causing infinite loops and massive spam

Technical details I found:

  • TERM=dumb (this seems to be the culprit)
  • tty returns “not a tty”
  • Shell shows non-interactive flags
  • Parent process shows it’s running through the extension host

The real problem:
This completely disrupted my development workflow. I was able to iterate and test installation scripts directly with the AI assistant before, which was incredibly convenient. Now I have to constantly switch between the AI terminal and the real terminal (⌘+`) just to test basic interactive scripts.

Either bring back the interactive support or at least document this limitation clearly so developers know what to expect.

Thanks!

Steps to Reproduce

Simple reproduction:

read -p "Type something: " test
echo "You typed: '$test'"
# Result: Infinite loop printing "You typed: ''"

Expected Behavior

an echo of what was typed by the user

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.45
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

Sonnet 4

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like
2

Is anyone from the Cursor team reading these bug reports?

3

Hey, please update to version 1.7 and let me know if the issue still persists.

4

Thanks! I’m now running v1.7.12 and the issue persists.

1 Like
5

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