Sandbox

The sandbox runs any program so that it changes only the folders you give it, reaches only what you allow, and never reads Local Link's settings. Link Agents use the sandbox by default, and you can use it for your own commands. A Sandbox Spec says what the sandbox allows, as a file or as flags.

Check the Sandbox on This Machine

Check whether the sandbox can run on this machine, and install any support it needs. Machine setup lists the requirements for each platform.

lnk sandbox check --ready

Run a Program in the Sandbox

Run a program with only the folders you give it, or write all of its permissions down in a file. Running a program covers the complete workflow. For agents, your grants combine with the access a harness asks for, as Permissions explains.

lnk sandbox run --commands.toolchains shell --files.write . -- bash

Test What the Sandbox Blocks

Check from inside the sandbox that disallowed access is blocked. The check uses the same permissions as a run.

lnk sandbox check --files.write .

Answer a Sandbox Request

Approve or deny a pending sandbox request with the code the sandbox prints. Replace k7m2pq with that code. Each approval surface works the same way.

lnk sandbox answer k7m2pq yes

Choose What a Program Can Reach

Choose What the Sandbox Can Reach names every permission group. Features compares what the sandbox can open and close, and Tools and Asking covers the tools that run outside the sandbox and the owner's approval. Security states what every sandbox guarantees, and Gaps and Limits lists what stays open.

Find Saved State and Fix Failures

Configuration locates saved policies and runtime records. Troubleshooting fixes the common failures, and Decisions explains why the sandbox works as it does. A box controller confines remote logins with sandboxed SSH sessions and refreshes its launcher through worker controller maintenance.

Build on the Sandbox

The sandbox confines each program with the operating system's own tools and filters its network traffic through a proxy that runs outside the sandbox. Callers and implementers share four boundaries: the Sandbox Contract, the Client Interface, Bridges, and Routes. More gathers these references in one place.