Subshell Docs

Directory restrictions

Restrict where new subshells can launch on a node.

Before you start

The node's owner, or someone they gave Manage, can edit its directory allowlist. View and edit shares don't give anyone permission to widen the list.

Set the allowlist

  1. In the server dashboard's sidebar, choose Settings → Nodes, select the machine, and open its Overview page.
  2. In the Allowed directories card, select Add directory.
  3. Add absolute directories that exist on that machine.
  4. Select Add directory again to save the entry, then test a launch inside that directory.

A session can launch in an allowed directory or beneath it. The rules are checked by both the control plane and the node, including for restarts and directory browsing operations supported by the node.

Empty allowlist

An empty allowlist means unrestricted execution directories. Clearing every entry doesn't disable launches.

Limits

The allowlist restricts the initial working directory. It isn't an OS sandbox: an agent can still access files allowed by its execution account.

Rules use resolved paths, so symbolic links don't provide an alternative spelling that bypasses confinement. Existing running sessions aren't stopped by changing the allowlist.

Users who can see the node can also see its directory rules. Choose an execution account with appropriate filesystem permissions for stronger isolation.

Next steps

Read Share a node and Security model.

Edit on GitHub

Last updated on

On this page