Cursor CLI should support native persistent remote sessions without tmux/screen

Ideas Feature Requests
, ,
1

Feature request for product/service

Cursor CLI

Describe the request

Problem:
Cursor CLI works poorly for long-running agent work on remote machines.

Current behavior:

  1. If I run Cursor CLI directly in a terminal/SSH session, execution can become blocked or unreliable when the local page, computer, or terminal session becomes inactive.
  2. Running Cursor CLI inside tmux, screen, or zellij helps because the process survives independently, but it adds friction:
    • scrolling is awkward unless tmux mouse mode is configured
    • keybindings can conflict with Cursor CLI
    • cursor rendering/focus behavior can be confusing in tmux panes
    • every remote machine needs extra setup

Expected behavior:
Cursor CLI should support native persistent sessions, similar to Claude Code, where the agent can keep running reliably in the terminal without requiring tmux/screen/zellij.

Why this matters:
For many engineers, the remote machine is not an optional convenience. It is the primary or only viable development environment.

This is especially common in backend development, infrastructure work, ML infra, distributed systems, and large-codebase workflows where the required services, datasets, build environment, GPUs, internal network access, or production-like dependencies only exist on remote servers.

In these workflows, agent tasks are naturally long-running: builds, tests, log inspection, debugging, benchmark runs, service restarts, and iterative code changes. Requiring tmux/screen/zellij is workable, but it adds operational friction and makes Cursor CLI feel less native than Claude Code for serious remote/server development.

A first-class persistent Cursor CLI session would make remote development much more reliable:

  • the agent can keep running even if SSH disconnects or the local terminal becomes inactive
  • users can reconnect cleanly to an existing session
  • scrollback/logs remain accessible without tmux-specific setup
  • remote development feels like a supported Cursor workflow rather than a workaround

Related forum threads:

Other related thread titles:

  • Cursor CLI’s Ctrl+O doesn’t work in tmux
  • Agent guidance for long-running terminal commands

Operating System (if it applies)

Linux