Cursor Glass / CLI and WSL2 environment

Support Help
, , ,
1

Hello,
I have a few questions regarding the following:

  1. In Cursor Glass, I would like to be able to read chat histories like tmux sessions, and enable communication between different projects so they can exchange messages and integrate via APIs. Is this possible? Or if not, could you recommend a terminal or tool to use with WSL2 instead?

  2. I am currently using the multitasking features in the Cursor Glass app. When running via CLI in tmux, is it possible to access similar multitasking capabilities as in Cursor Glass directly from the CLI?

3-1. When using CLI, the output keeps accumulating, resulting in endless scrolling. Is there any way to hide or fold code modification outputs to reduce scrolling, similar to the collapsible view in Cursor Glass?

3-2. When using tmux with CLI, after switching to another tab or pane and returning, the output scrolls back from the top, causing persistent infinite scrolling. When using WSL2, are there any recommended alternatives to tmux? Or is this not a tmux limitation but rather a structural limitation of Cursor CLI, making it unavoidable?

  1. I am wondering whether it is possible to install the Cursor app on a mobile phone and use it for coding, similar to apps like Codex or Claude.

Please answer questions that can be answered number quickly first.

Thank you

5

Hey, thanks for the questions. I’ll go in order.

  1. Chat history and sharing across projects. In Glass, chat history is stored per project and available from the history panel. In the CLI, sessions are also saved. You can come back via /resume <chat> in the TUI or cursor-agent resume, cursor-agent ls, or cursor-agent --resume <id>. Important: CLI history and IDE history are stored separately and don’t sync yet, so there’s no “continue a CLI chat inside the IDE” flow right now. This is a requested feature, tracking here: Add chat history to the cursor CLI's. There’s also no built-in API “bus” for projects to talk to each other. For integrations, use MCP servers. For scripts and automation, use the CLI headless mode with -p --output-format json.

  2. Multitask from the CLI. Glass can run multiple agents in parallel. The CLI is one interactive agent per terminal. To work in parallel, run multiple cursor-agent instances, like separate tmux panes or isolated git worktrees via --worktree, or send tasks to a cloud or background agent with the & prefix and monitor them on cursor.com/agents or from your phone. There’s no single multi-agent dashboard inside the CLI right now.

3-1. Collapsing output. The CLI is a terminal TUI, so it doesn’t have collapsible diffs like Glass. If you want to hide intermediate output and keep only the final answer, run non-interactive: cursor-agent -p --output-format text "<prompt>".

3-2. tmux scroll and infinite scroll. This is a known CLI rendering bug in tmux, it fully re-renders history when you switch or zoom a pane. It’s not a structural CLI limit and it’s not tmux’s fault. The issue is on our side, it’s known, but there’s no clear ETA yet. Workarounds for now: avoid tmux zoom-toggle, keep the CLI in a dedicated pane, and enable mouse mode in tmux for scrolling.

  1. Mobile app. Two options:
  • Cursor for iOS: a native app in public beta, available on all paid plans. It’s a companion for Cloud Agents. You can start and monitor agents, use Live Activities, review diffs and demos, and merge PRs from your phone. It’s not a full mobile IDE.
  • Web or PWA on cursor.com/agents works in a browser on any device and can be installed as a PWA on iOS and Android. Announcement: Introducing Cursor on Web & Mobile.

Let me know if you want a deeper dive on any point.