FabricFabricHarness
EcosystemSandboxes

Sandboxes

Remote execution adapters that implement the common SandboxEnv contract.

Fabric owns the sandbox contract while applications own provider clients and credentials. The adapters below accept structural provider handles, so vendor SDKs remain optional peer dependencies.

pnpm add @fabric-harness/connectors
ProviderHelperRecipeLive validation
Databricks SQLdatabricksSqlSandbox()First-party packageWorkspace, Warehouse, and Unity Catalog gate.
boxdGeneric remoteSandbox()fh add boxdProject-owned adapter and live smoke.
Cloudflare Shell@fabric-harness/cloudflare/shellfh add cloudflare-shellWrangler/account gate.
Cloudflare Sandbox@fabric-harness/cloudflarefh add cloudflare-sandboxWrangler/account gate.
DaytonadaytonaSandbox()fh add daytonaFABRIC_DAYTONA_TEST=1
E2Be2bSandbox()fh add e2bFABRIC_E2B_TEST=1
exe.devGeneric remoteSandbox()fh add exedevProject-owned adapter and live smoke.
isloGeneric remoteSandbox()fh add isloProject-owned adapter and live smoke.
MirageGeneric remoteSandbox()fh add mirageProject-owned adapter and live smoke.
ModalmodalSdkSandbox()fh add modalFABRIC_MODAL_TEST=1 plus Modal tokens
VercelvercelSandbox()fh add vercelContract tests; run a provider smoke before production.
Kubernetes / AKSkubernetesSandbox()Package helperCluster-gated validation.
Any providerremoteSandbox() / remoteSandboxEnv()fh add <docs-url> --category sandboxProvider-specific.

All sandbox operations still pass through Fabric capability policy. Provider isolation does not replace filesystem, command, network, approval, timeout, or cleanup policy.