Perplexity AI Updates: October 15, 2026

1. Perplexity Details How SPACE Binds Agent Requests to a Specific Sandbox Execution

Perplexity. Perplexity described how SPACE, its sandbox platform for agents built on Firecracker microVMs, prevents requests from reaching the wrong sandbox or a stale incarnation of the right one after pauses, snapshot resumes, or moves between workers. After authorization, the control plane issues an Ed25519-signed capability valid for 120 seconds that names the sandbox, the execution generation, the placement, and (for service ports) the allowed port and protocol; the sandbox manager, the per-sandbox gateway, and the host bridge each compare it against locally persisted runtime state and reject mismatches even when the signature is valid. The request path runs from node-api through sbx-manager over a Unix socket to the spaced-host bridge, then over VSOCK into the guest, with checks on process identities and start times to catch reused PIDs, and terminal or file-watch streams are cancelled when an execution is replaced. Perplexity reports millions of executions per day with an error rate below 0.0002%, and compares the design with OpenShell, E2B, and CubeSandbox, noting that E2B’s proxy routes by sandbox and port without checking which execution it reaches. Source