Answer: The terminal is unavailable because the worker started without the --connect-workspace flag, or because it runs on macOS or Windows rather than Linux. The terminal tab states the specific reason. Status: Confirmed Entry: tool/cursor/troubleshooting/terminal-unavailable-live-workspace Revision: 3 Digest: sha256:fbada36d2cd5b97a (changes whenever the content changes) Timeline: Created: 2026-11-13T12:25:24Z Last changed: 2026-11-20T12:36:47Z (reason non-Linux: — → Terminal is only available on Linux workers) Last verified: 2026-11-20T12:36:47Z Next check: 2026-11-21T12:36:47Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of reason without flag | --connect-workspace | [1] | 2026-11-20 reason non-Linux | Terminal is only available on Linux workers | [1] | 2026-11-20 confirmation flag | --verbose | [1] | 2026-11-20 startup output marker | cursor-server enabled (--connect-workspace) | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/cloud-agent/self-hosted.md". https://cursor.com/docs/cloud-agent/self-hosted.md Role: primary. Accessed: 2026-11-20T12:36:47Z Quote: ""To use the terminal, restart the worker with the --connect-workspace flag" means the worker started without the flag." (Supports: reason without flag) Quote: ""Terminal is only available on Linux workers" means it runs on macOS or Windows." (Supports: reason non-Linux) Quote: "restart with `--verbose` and look for `cursor-server enabled (--connect-workspace)` in the startup output." (Supports: confirmation flag) Quote: "look for `cursor-server enabled (--connect-workspace)` in the startup output." (Supports: startup output marker) Snapshot SHA-256: d8b3dcad716535dac7e51e48662492ce08ca863e4543a51c7ba5d369b8ff4fa0 (captured 2026-11-19T12:31:29Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-19T12:31:30Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:36:47Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:36:47Z Last attempt: 2026-11-20T12:36:47Z Notes and limitations: Extracted automatically from a single official source (section "Why is the terminal unavailable?"). Related: https://latestn.com/tool/cursor/troubleshooting/test-webhooks-locally How do I test Cursor webhook agents locally? https://latestn.com/tool/cursor/troubleshooting/tour-too-large Why does Cursor show 'Too large for a tour' on a pull request? https://latestn.com/tool/cursor/troubleshooting/troubleshoot-xcode-tools-server How do I troubleshoot Cursor not finding the xcode-tools server? https://latestn.com/tool/cursor/troubleshooting/subagent-not-delegated Why isn't Cursor delegating to my subagent? https://latestn.com/tool/cursor/troubleshooting/tailscale-failed-to-connect Why does Cursor show 'Failed to connect' for my Tailscale MCP server? https://latestn.com/tool/cursor/troubleshooting/terminal-output-truncated-misformatted Why is Cursor terminal command output truncated or misformatted? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T12:36:47Z | changed | reason non-Linux: — → Terminal is only available on Linux workers | [1] 2026-11-20T12:36:47Z | changed | reason without flag: — → --connect-workspace | [1] 2026-11-20T12:36:47Z | changed | reason (OS): Terminal is only available on Linux workers → — | [1] 2026-11-20T12:36:47Z | changed | reason (missing flag): --connect-workspace → — | [1] 2026-11-18T12:30:57Z | changed | reason (OS): — → Terminal is only available on Linux workers | [1] 2026-11-18T12:30:57Z | changed | reason (non-Linux): Terminal is only available on Linux workers → — | [1] 2026-11-13T12:25:24Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/troubleshooting/terminal-unavailable-live-workspace/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/troubleshooting/terminal-unavailable-live-workspace POST: https://latestn.com/dispute/tool/cursor/troubleshooting/terminal-unavailable-live-workspace with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/troubleshooting/terminal-unavailable-live-workspace?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). Why is the terminal unavailable in the Cursor Self-Hosted Machines live workspace? Revision 3, last verified 2026-11-20T12:36:47Z. https://latestn.com/tool/cursor/troubleshooting/terminal-unavailable-live-workspace (accessed 2026-11-21T10:07:11Z). @misc{LatestN_tool_cursor_troubleshooting_terminal_unavailable_live_workspace_r3, title = {Why is the terminal unavailable in the Cursor Self-Hosted Machines live workspace?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/troubleshooting/terminal-unavailable-live-workspace}}, note = {Revision 3; digest sha256:fbada36d2cd5b97a; last verified 2026-11-20T12:36:47Z; accessed 2026-11-21T10:07:11Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/troubleshooting/terminal-unavailable-live-workspace