main.js · part 237

60 text occurrences from desktop/Cursor.app/Contents/Resources/app/extensions/cursor-agent-host/dist/main.js, part 237. Every entry preserves the shipped literal and its saved verdict or selection reason.

File contents and all parts · All files

tmux -f /exec-daemon/tmux.portal.conf

On this self-hosted machine, invoke tmux without `-f`. If `tmux` is not installed (`command -v tmux` prints nothing), run long-lived commands in the background with this tool instead.

On the VM, invoke tmux with `-f /exec-daemon/tmux.portal.conf`. If that config path is unavailable, fall back to the same command without `-f`.

SESSION_NAME="${r}"; ${n} has-session -t "=$SESSION_NAME" 2>/dev/null || ${n} new-session -d -s "$SESSION_NAME" -c "$PWD" -- "${SHELL:-zsh}" -l

tmux is the required mechanism for shell work that may outlive a single command. If you need an interactive shell, any background command (such as starting dev servers), a long-running process, follow-up input, later inspection, or a shared session that you or the user may reconnect to later, you MUST use tmux. Do NOT launch those workflows as one-shot background processes. If you are planning to set block_until_ms to 0, you should ALWAYS back this session with tmux.

There is one canonical shared tmux session for most recurring shell work — `

`. Start or reuse that session before ordinary setup work, then use it for every install, build, migration, version check, and verification command. Only create a separate descriptively-named session (short kebab-case, e.g. `vite-dev-server`, `backend-tests`, `postgres`) for long-running side processes that must keep running after a single command finishes. Do NOT invent a new per-task session name for ordinary shell work — route it through `

Use a descriptive tmux session name for the task or command instead of a single global shared name. Prefer short kebab-case names such as `vite-dev-server`, `backend-tests`, or `db-migration`.

Start or reuse the appropriate session by running

Before creating a new session, list existing sessions with 

`${r} ls`

 and reuse an existing one when appropriate.

To inspect or continue work in an existing session, attach with

`${r} attach-session -t "$SESSION_NAME"`

To send input to a session without attaching, run

`${r} send-keys -t "$SESSION_NAME:0.0" 'your command here' C-m`

Optional list of permissions to request if the command needs them (full_network).

Optional list of permissions to request if the command needs them (full_network, all).

Optional list of permissions to request if the command needs them (full_network, all).

The sandbox includes network access for common package managers and version control providers (e.g. npm, pypi, crates.io, Maven Central, GitHub, etc.). Standard operations like package installs and fetching dependencies will work without requesting additional permissions.

Additionally, the

 sandbox includes network access for the following domains: 

. You do not need to request 'full_network' permissions for these domains.

For broader network access beyond the allowed domains, you may still need to request 'full_network' permissions.

Your commands will run in a readonly sandbox. The sandbox allows reads to the filesystem but does not allow any writes.

 Network access is disallowed by default but can be requested with the full_network permission.

The required_permissions argument is used to request additional permissions:

full_network: Grants unrestricted network access beyond the allowed domains.

full_network: Grants unrestricted network access.

By default, your commands will run in a sandbox. The sandbox allows most writes to the workspace and reads to the rest of the filesystem. Some other syscalls are also disallowed like access to USB devices. Syscalls that attempt forbidden operations will fail and not all programs will surface these errors in a useful way.

Files that are ignored by .cursorignore are not accessible to the command. If you need to access a file that is ignored, you will need to request "all" permissions to disable sandboxing.

The required_permissions argument is used to request additional permissions. If you know you will need a permission, request it. Requesting permissions will slow down the command execution as it will ask the user for approval. Do not hesitate to request permissions if you are certain you need them. For commands you know will need unrestricted network access, request the full_network permission rather than waiting for the command to fail and asking for it later.

The following permissions are supported:

full_network: Grants unrestricted network access to run a server or contact the internet. Needed for package installs, API calls, hosting servers and fetching dependencies.

full_network: Grants unrestricted network access. This is useful for any commands that need to contact the outside internet, outside of the allowed domains.

all: Disables the sandbox entirely. If all is requested the command will run outside of the sandbox.

If you think a command failed due to sandbox restrictions, run the command again with the required_permissions argument to request what you need.

Execute shell commands in the workspace.

The shell is stateful - cwd & env vars persist for subsequent calls.

Make efficient use of shell calls and minimize wasted tokens.

Batch related shell work together or run independent checks in parallel when safe. Make liberal use of `&&`, `;`, pipes, greps, and other efficient shell use.

Use targeted, output-limited terminal commands such as `rg`, `head`, `tail`, and `sed -n` when relevant to limit output.

NEVER use `set -x`; it breaks this tool. If it gets set, run `set +x` to fix the shell.

Optimize for overall cost, including cache reads, cache writes, and output tokens.

Use the 'Workspace Path' field in the `<user_info>` section to resolve the workspace path. It will likely NOT be at `/workspace`; don't waste time trying that.

Still do whatever validation is necessary to ensure the judgment is correct; efficiency means avoiding waste, not skipping verification.

This may still be a long-running investigation if correctness requires it, but do not spend tokens on status updates, progress narration, or UX niceties while judging.

Always quote paths that contain spaces.

Executes a given command in a shell session with optional foreground timeout.

IMPORTANT: Use this tool for terminal operations like git, npm, docker, etc. DO NOT use it for file operations (reading, writing, editing, searching, finding files

) - use the specialized tools for this instead.

 for file operations when applicable. If shell text search is necessary, use `rg`, not `grep` or `find`.

Do not truncate output with `head`, `tail`, or `sed -n` solely to limit its size; large output is saved to a terminal file.

Run independent commands as parallel Shell calls. Chain dependent commands with `&&`.

Use the `gh` command via the 

 tool for all GitHub-related tasks, including issues, pull requests, checks, and releases.

tmux-backed shell sessions

Executes a given command in a shell session with optional foreground timeout.

IMPORTANT: This tool is for terminal operations like git, npm, docker, etc. DO NOT use it for file operations (reading, writing, editing, searching, finding files

) - use the specialized tools for this instead.