What a plugin’s programs can reach
Every program a plugin runs (a language server or an MCP server) starts inside a sandbox Jacker sets up from the plugin’s manifest. This page says what that sandbox allows, so you can declare what your program needs and nothing more. Users see the same rules, in plain words, before they install.
No sandbox, no program
Jacker uses sandbox-exec on macOS and bubblewrap on Linux. On a machine where neither works, plugin programs don’t start, and the plugin shows “Cannot run safely on this machine”. Plugins that only add colouring and code map queries still work there, because they run no program.
Files
A program can read files on the computer, except protected folders. The protected folders include Jacker’s own data folder (other than your plugin’s folder), ~/.ssh, ~/.gnupg, ~/.aws, ~/.azure, ~/.kube, ~/.docker, ~/.config/gcloud, ~/.config/gh, ~/.netrc, ~/.npmrc, ~/.git-credentials, the folders of the agent CLIs (~/.claude*, ~/.codex*, ~/.kimi*), ~/Library/Keychains, and browser profiles. The full list is protectedReadRoots in apps/orchestrator/src/plugins/plugin-process.ts.
A program can write to:
- The project, only if
permissions.filesystemisproject-write. - Its own cache folder, which Jacker creates for each plugin.
- The toolchain caches listed in
permissions.cacheDirs. - The temp folder.
Network
If permissions.network is empty, a program has no network. Any entry switches the network on. Jacker doesn’t limit connections to the hosts you list; they tell the user what the network is for.
Environment
A program doesn’t inherit Jacker’s environment. It gets the few variables listed in Environment and the ones its env sets. It never gets Jacker’s API keys, its connection token, or stored secrets other than its own config.
Projects that aren’t trusted
Plugin programs don’t run for an imported project the user hasn’t trusted. In such a project, a language pack’s colouring still applies; its language server and tool servers don’t start.
What users see
On the install sheet and on the Installed tab, a plugin’s access reads, for example:
- Can read files on this computer outside protected folders.
- Can change files in this project.
- Can write to
~/go/pkg/mod. - Can use the network. Says it is for proxy.golang.org (not enforced).
- While an agent runs with an API key, it could read that key. Signing in with a subscription avoids this.
- Asks you for: GitHub token.
The line about API keys appears for every plugin with network access. An agent CLI that Jacker starts with an API key holds that key where other programs of the same user can read it, and the sandbox can’t prevent that.
Ask for as little as you can: each line you add is one more reason for a user not to install.