Import Vercel Sandboxes into Bast and manage create, stop, resume, fork, and delete through the REST API.

The Sync tab (4) imports Vercel Sandboxes into Bast. Synced sandboxes show up in the host picker under Vercel. Bast talks to Vercel over the Sandbox REST API. There is no extra CLI to install for create, stop, resume, fork, or delete.

Connect is not OpenSSH. Vercel Sandboxes expose a WebSocket PTY, not an SSH daemon. Enter in Bast (or bast connect) opens that shell. ssh vercel_foo and SFTP will not work.

Requirements

A Vercel access token
The team ID (team_…)
The project ID or name (prj_…)
Network access to https://api.vercel.com

Hobby sandboxes time out after 45 minutes. Bast’s supported session timeout is 15m, 1h, or 5h. Vercel Pro/Enterprise can run up to 24 hours; Bast caps create at 5 hours.

Connect Vercel

Open Bast and press 4 for Sync.
Select Vercel Sandbox and press Enter.
Choose Connect. Paste the token, team ID, and project ID.

Bast writes the token to ~/.config/bast/vercel-token (mode 0600). Team and project stay in state.json. The token is not stored in SSH config or Vault. Disconnect leaves the token file in place.

You can also set VERCEL_TOKEN, VERCEL_TEAM_ID, and VERCEL_PROJECT_ID. The first successful sync copies the token into the local file.

CLI:

bast vercel token --team team_xxx --project prj_xxx
bast vercel token --token-file path --team team_xxx --project prj_xxx
bast sync vercel
bast sync status
bast sync disable vercel

If a token, team, and project are already stored, Bast auto-connects on TUI start and bast sync status, unless you previously chose Disconnect.

What gets created

Each sandbox becomes a picker host under:

~/.ssh/bast/sync/vercel/config

Host vercel_dev
    HostName vercel.sandbox.invalid

That hostname is a sentinel so the host appears in Bast. It is not a reachable SSH target. Connection settings, group, and label are owned by sync.

Stopped sandboxes with a snapshot stay in the Vercel group and are hidden from the host list until you press .. If no sandboxes are running, the group is hidden too; . brings it back when stopped sandboxes remain. Offline sandboxes without a snapshot cannot be resumed, so they stay off the host list. Cleanup on the Vercel Sync page (or bast vercel cleanup) deletes them after you confirm.

Lifecycle

Action	What Vercel does
New	`POST /v2/sandboxes` with runtime `node24`, vCPUs, timeout, optional name. Persistent by default
Stop (`o` / `bast vercel stop`)	Stops the current session and snapshots the filesystem
Resume (`r` / Enter on a stopped sandbox)	Starts a new session from the snapshot, then opens the shell
Fork (`n`)	Creates a new named sandbox from the current snapshot
Delete (`d`)	Destroys the named sandbox. Snapshots remain on Vercel
Cleanup	Deletes offline sandboxes with no snapshot (cannot be resumed)

Create options: vCPUs 1 / 2 / 4 (2 GB RAM each), timeout 15m / 1h / 5h, optional name, persistent (default on).

Host keys (Hosts tab)

With the Vercel group selected:

Key	Action
`n`	Create a new sandbox
`s`	Sync now
`.`	Show stopped sandboxes

With a Vercel host selected:

Key	Action
Enter	Connect (resume first if stopped)
`r`	Resume only (when stopped)
`o`	Stop (when running; confirms with `stop`)
`n`	Fork (confirms with `fork`)
`d`	Delete the remote sandbox (confirms with `delete`)

Files (F) is unavailable. Vercel Sandboxes are not OpenSSH, so SFTP does not apply.

CLI

bast vercel new [--name name] [--vcpus 1|2|4] [--timeout 15m|1h|5h] [--ephemeral]
bast vercel fork <host|id> [--name name]
bast vercel stop <host|id>
bast vercel resume <host|id>
bast vercel delete <host|id> [--yes]
bast vercel cleanup [--yes]
bast connect vercel_dev

Re-sync and cleanup

Press r on the Sync tab (or bast sync vercel) after you create, stop, or delete sandboxes outside Bast. Offline sandboxes with no snapshot show as N unrestorable on the Vercel page. Cleanup deletes those from Vercel after confirmation. Disconnecting Vercel removes the generated sync config. The token file stays until you delete ~/.config/bast/vercel-token.

Vercel Sandbox