Skip to main content
Open Settings → Sidekick → Local Execution to control whether threads can run on member machines instead of the cloud. Cloud is always the default placement for a thread. Running on a member’s computer is the governed axis: it stays off until you turn it on, and even then it’s opt in per session for the member running it.

​
The two toggles

1

Run sessions on member machines

Off by default. Turning this on makes This computer available as a placement choice in the composer, so a member can opt in to running a session on their own machine. It doesn’t move any existing thread; it only makes the option available going forward.
2

Allow folder grants

Controls whether a member running a session locally can grant it access to a folder on their machine. With this off, a local session can still run, but it can’t be pointed at local files or directories.
A session running on a member’s computer can read and write files and call tools on that device, within whatever folder access was granted. Turn on folder grants only for workspaces where that trade-off is acceptable.

​
Where to go next

On your computer

What running a thread locally looks like for the person doing it, including the liveness bar and folder grants.