# DevContainer stuck at v0.327.0 (\>11 months old, \>10 release versions behind)

**URL:** <https://forum.cursor.com/t/devcontainer-stuck-at-v0-327-0-11-months-old-10-release-versions-behind/26491>\
**Category:** Bug Reports\
**Created:** [November 6, 2024, 1:21pm UTC](https://forum.cursor.com/t/devcontainer-stuck-at-v0-327-0-11-months-old-10-release-versions-behind/26491 "2024-11-06T13:21:50Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![mjnowen](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mjnowen/32/7815_2.png) [@mjnowen](https://forum.cursor.com/u/mjnowen)\
**Post date:** [June 24, 2025, 6:51am UTC](https://forum.cursor.com/t/devcontainer-stuck-at-v0-327-0-11-months-old-10-release-versions-behind/26491/16 "2025-06-24T06:51:20Z")

</div>

The single biggest issue is stability. The internet is a wasteland of PTY host issues with Cursor.

## Common Issues with PTY Host in Cursor

- **Timeouts and Disconnections:** Users have reported that after using features like Agent or Ask, all open terminals in Cursor may lose connection or timeout, especially in development container environments. This may be due to aggressive cleanup routines or process management bugs that terminate PTY sessions prematurely[5](https://forum.cursor.com/t/pty-host-on-terminals-crash-after-using-cursor-ask-agent/78920).

- **PTY Host Errors with Long Scripts:** Running long or resource-intensive scripts (notably in R) can trigger “pty host” errors, particularly on macOS. This interrupts analytical workflows and forces users to break tasks into smaller chunks[6](https://github.com/getcursor/cursor/issues/3094)[7](https://forum.cursor.com/t/pty-host-unresponsive/97576).

- **Unresponsive PTY Host:** When running multiple or large code blocks (e.g., loading/manipulating large dataframes in R), the PTY host can become unresponsive, especially on certain hardware or OS configurations[7](https://forum.cursor.com/t/pty-host-unresponsive/97576).

- **Orphaned Processes and High CPU Usage:** On remote connections (e.g., SSH to a server), Cursor may leave behind orphaned bash processes tied to the PTY host, causing high CPU usage even after the editor is closed. This indicates issues with process cleanup and resource management[4](https://www.reddit.com/r/cursor/comments/1k6uacb/cursor_cpu_usage_with_remote_ssh_to_a_ubuntu/).

---

_[View the full topic](https://forum.cursor.com/t/devcontainer-stuck-at-v0-327-0-11-months-old-10-release-versions-behind/26491)._
