## What this fixes
Using the E2B JS SDK (v1.0.4) inside a Vercel Edge function threw `SandboxError: 2: [unknown] Invalid redirect value, must be one of "follow" or "manual"`. The identical code ran fine on Node locally. The error came from the SDK's RPC layer (connect-es), which passed a redirect mode the Edge runtime does not implement — Edge fetch only supports "follow" and "manual", not "error".
## The fix
The E2B team fixed Edge-runtime support in the JS SDK — it landed in v1.2.3 and up, where the API/RPC clients use `redirect: "follow"` (the only redirect mode Edge allows) for requests to E2B endpoints. Fix: upgrade with `npm i e2b@^1.2.3`. If you're stuck on an older SDK, the workaround is to run E2B calls on a regular non-edge (Node) runtime instead of Edge functions. Source: https://github.com/e2b-dev/E2B/issues/531
## Why it happens
The thread above nails the cause, so the fix addresses that directly rather than symptoms. Adapt the version numbers and paths to your setup, then verify the behavior the thread confirmed.
## Source
https://github.com/e2b-dev/E2B/issues/531