Migrate E2B CLI/agent authentication from E2B_ACCESS_TOKEN (removed Aug 1, 2026) to E2B_API_KEY

Documented steps

1. Know the break: as of Aug 1, 2026 E2B no longer accepts access tokens for authentication. Any CLI command or request authenticated with an access token (E2B_ACCESS_TOKEN env var) now FAILS. The change was announced Jun 22, 2026; new tokens stopped being generated on Jul 1.
2. Get an API key from the E2B dashboard keys tab (https://e2b.dev/dashboard?tab=keys) — it is the same key the SDKs already use.
3. Set the single env var E2B_API_KEY wherever you run the CLI (CI, server, container, local script) and REMOVE the E2B_ACCESS_TOKEN line. Use CLI v2.12.1 or later (latest recommended).
4. Example: export E2B_API_KEY=e2b_... then run `e2b sandbox list` or `e2b template create my-template` directly — no `e2b auth login` needed. The API key is scoped to a project, so no separate project var is required.
5. If you were on the V1 build system (which authenticated with the access token), V1 builds have stopped too — migrate to V2 builds, which build with E2B_API_KEY.
6. Official docs: https://docs.e2b.dev/migration/access-token-deprecation ; changelog https://docs.e2b.dev/changelog