Skip to main content
Use a persistent Vercel Sandbox to execute a Hexagon Harness. This page does not publish an application as a Vercel website. Sessions manage tasks/workspaces; private preview is not public deployment.

Credentials and project binding

Prepare a Vercel Token authorized for the intended team/project and Sandbox operations. Supply real project_id and team_id values together. Project display names and the browser’s current team do not replace these identifiers. Use vcpus. The schema does not accept invented image or memory_mb fields. The Token stays in the control plane, not ordinary Agent environment. These examples use a local management client; see self-hosting for hosted initialization. Rerunning creates additional connections, so retain and reuse the ID.
Validation only lists Sandboxes in the specified team/project; it does not prove task execution or recovery. Enable explicitly after ready validation. Revalidate/enable after Token, project, or resource edits; existing Sessions remain pinned.

Execution and private preview

Use connection.id as sandbox_connection_id in the first Session, with a compatible Harness/model. Independently verify task execution, actual artifacts, and close through Python and TypeScript. The connector creates persistent=true Sandboxes without public ports. Nonpersistent resources or unexpected public routes violate its resource policy. Preview reaches the internal port through an authenticated command channel, governed by Hexagon preview authorization. Browsers do not receive the Vercel Token. Do not create public routes to access the task’s development server. Diagnose listening service, command transport, Runtime health, and user authorization separately.

Networking and native credential injection

The native_credential_auth capability configures network-layer delegated Token injection for scoped control-plane access paths. Original model/Tool account keys remain in the control plane. The access proxy continues checking method, path, Run state, version, and revocation; provider injection does not bypass platform authorization. This internal mechanism does not expose general network_allowlist to applications. The connector declares neither ordinary Sandbox allowlists nor OCI, and creation requires unrestricted networking. Choose a supporting provider for domain restrictions instead of adding unsupported Vercel fields.

Idle, stop, and recovery

Platform suspension stops the persistent Sandbox. The next submit resumes it through the same Session. Filesystem and managed conversation data persist while Runtime is prepared again. Arbitrary processes, memory, and network connections have no continuity guarantee; preview services may need restarting. Inspection uses resume=false so observing state does not itself wake compute. A stopped persistent Sandbox maps to paused, not deleted. Active Runs, including authorization/approval waits, are not idle workspaces to suspend arbitrarily. Follow idle and wake to independently verify both turns, files, and conversation. Write known content before idle and read/check it afterward. Record exact Harness, model protocol, and both SDK results. One successful turn does not prove restoration.

Close and unknown outcomes

Close deletes with deleteOrphanSnapshots and then checks resource absence. Accepted deletion, stopped state, or local control-plane exit is not confirmed cleanup. The control plane owns durable deadlines; downtime can delay the cleanup it enforces. Creation derives an exact name from the persisted operation ID. Reconciliation lists by namePrefix and filters by the complete name; another prefix match cannot be bound to this Session. Transport/authentication errors do not mean absence; only explicit 404 is treated that way. Preserve original resource records for unknown restore/delete outcomes and reconcile.

What has been verified

Use the following records to distinguish task execution from recovery. Each record applies to its own programs, combination and date. The current connector source separately shows stop/resume, read-only inspection without wake, Runtime-facing command transport and confirmed deletion. Filesystem continuity and a running process are different claims: the recovery ledger does not promise arbitrary processes survive suspension. The tutorial evidence uses existing verified connections; it does not establish a clean-account credential setup. Follow installation, configure this connection, and run the linked tutorial in your environment. Preserve its journal until deletion is confirmed. The browser accesses the Hexagon preview route; Provider credentials stay in the control plane according to the connector and transport implementation. Browser behavior alone is not an audit of every credential boundary. Historical combinations remain in the execution matrix; none of these scoped passes proves account-wide cleanup. Sources: Vercel connector, private transport. Next: Sandbox overview, credential boundaries.

Separate account, resource and task readiness

A new team/project binding is a connection change, not a transfer of an existing Sandbox. Preserve the original resource identity and permissions needed to reconcile it. Use the tutorial journal to resume observation; recreating the connection or Session is not the default response to a lost request. Sources: execution architecture. Next: private previews, idle/wake, deployment networking.