Silo

Type Alias: Permission ​

ts
type Permission = "fs:read" | "fs:write" | "process" | "network" | "webview" | "agents";

Defined in: packages/sdk/src/permissions.ts:39

A capability an extension declares in its manifest (silo.permissions) to request access beyond the open workspace. With none declared, an extension's FileService / ProcessService access is confined to the workspace folder(s); each permission lifts one part of that confinement, and the user consents to the set at install.

  • fs:read — read files outside the workspace.
  • fs:write — write files outside the workspace.
  • process — run commands with a working directory outside the workspace.
  • network — make outbound network requests. Declarative consent only until sandboxed execution lands (in-process code can reach the network directly); declare it so the capability is reviewable and shown at install.
  • webview — use ExtensionContext.webview to get real DOM access, script execution, and native pixel capture inside an iframe you own, including cross-origin content. Declare it because this reaches into arbitrary embedded pages, not because it touches the filesystem/network directly.
  • agents — use AgentSessionsService (ctx.agents.sessions) to start a Chat session: the host spawns the process named by a user-authored Chat Agent Profile and speaks the Agent Client Protocol to it. connect() throws without this, the way FileService throws PathDeniedError without fs:read. Distinct from process: the child is spawned by the host from a profile the user wrote, not by the extension through ExtensionContext.process. Trusted (built-in) extensions are exempt, the same way they're exempt from declaring fs:*/process — a narrower grant than either, since it only launches a profile the user already authored.