Vercel
How Mogplex uses Vercel Sandbox for agent compute, how to configure a repo's runtime and environment variables, and which Vercel features are not available.
Mogplex runs every agent sandbox on Vercel Sandbox, inside Mogplex's own Vercel project. You do not need a Vercel account. Sandbox usage bills through your Mogplex plan.
Not available yet
Mogplex cannot yet bill sandboxes to your own Vercel account or import environment variables from your Vercel projects. Both features need an API-capable Vercel integration that does not exist yet. "Sign in with Vercel" is an identity grant only and cannot read projects or env vars. Add sandbox variables by hand, as described below.
Configure a repo's runtime
Open the repo in Projects and edit its settings. These settings control how a sandbox installs and starts your app:
| Setting | Use it when |
|---|---|
| Launch Branch | Sandboxes should start from a branch other than the default. |
| Runtime | Auto-detection picks the wrong runtime. |
| Root Directory | The app lives in a subfolder of a monorepo, such as apps/web. |
| Install Command | The default install command for the package manager is wrong. |
| Dev Command | The preview needs a specific start command. |
| Dev Port | The dev server does not use the auto-detected port. |
| Env Mapping | Sandbox only passes only your variables. Sandbox + preview conventions also sets Vercel preview variables (VERCEL=1, VERCEL_ENV=preview, VERCEL_URL, NEXT_PUBLIC_APP_URL, and similar) unless you define them yourself. |
| Environment Variables | The app needs env vars. Paste .env-style KEY=value lines. Surrounding quotes are removed. |
| Sandbox Billing | Always Mogplex billing. |
Preview and sandbox troubleshooting
Start from the surface that owns the failure:
- Repo configuration problem: Projects
- The sandbox exists but looks stuck: Sandboxes
- You need the call or job trail behind the sandbox: Observability
- The account cannot launch sandboxes: Plans & Billing
Common failures:
- Sandbox launch says access is unavailable: the plan or balance does not include sandbox compute yet.
- Preview opens the wrong app: set Root Directory, Install Command, Dev Command, and Dev Port explicitly.
- Env values are missing: add them under Environment Variables in the repo settings. Mogplex does not read them from a Vercel project.
- The workspace opens the wrong sandbox: open it from Sandboxes, so that it binds to that exact sandbox.
Self-hosting
A self-hosted deployment runs sandboxes on your Vercel team, through the
PLATFORM_VERCEL_* variables. See
Sandboxes and models.