feat(cli): accept E2B_API_KEY in template list & create

[mishushakov]

Summary

E2B_ACCESS_TOKEN is deprecated, so CLI commands whose endpoints accept either credential now authenticate with E2B_API_KEY instead of requiring an access token.

• e2b template list now uses ensureAPIKey(). The underlying GET /templates endpoint accepts both ApiKeyAuth and AccessTokenAuth, and since the access token is deprecated we standardize on the API key.
• e2b template create no longer calls ensureAccessToken(). Its only API calls — POST /v3/templates and POST /v2/templates/{id}/builds/{bid} (via the SDK's Template.build) — accept only ApiKeyAuth, so requiring an access token locked out API-key-only environments for no reason.
• e2b template build is intentionally left as-is: its v1 endpoints and docker-registry login are access-token-only at the API level.
• Removed the now-unused ensureAccessTokenOrAPIKey() helper and the 'BOTH' variant of the auth-error box that an earlier iteration of this PR introduced.
• Adds a real backend-integration test in tests/commands/template/create.test.ts that mirrors the existing backend_integration.test.ts pattern: use the real E2B_DOMAIN and assert end-to-end that template create succeeds with only E2B_API_KEY set (no E2B_ACCESS_TOKEN). Uses a unique template name per run and cleans up the created template in afterAll.

Test plan

• pnpm --filter @e2b/cli run typecheck
• pnpm --filter @e2b/cli run lint
• pnpm --filter @e2b/cli run format
• pnpm --filter @e2b/cli run test (local, with real E2B_API_KEY — new test passes; create succeeds without E2B_ACCESS_TOKEN)

🤖 Generated with Claude Code

[changeset-bot]

🦋 Changeset detected

Latest commit: ab24582

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@e2b/cli	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[cursor]

PR Summary

Low Risk
CLI-only credential selection aligned with API-key-capable endpoints; no server or security-policy changes.

Overview
e2b template list and e2b template create now require E2B_API_KEY (via ensureAPIKey) instead of E2B_ACCESS_TOKEN, so API-key-only setups such as CI/CD can list and create templates without a personal access token. template create drops the upfront ensureAccessToken() call; listing swaps ensureAccessToken() for ensureAPIKey().

Shared authErrorBox in api.ts is tightened to a typed 'E2B_API_KEY' | 'E2B_ACCESS_TOKEN' helper with the same user-facing messaging. A changeset documents the behavior change, and a new backend integration test runs template create with only E2B_API_KEY in the child process env and asserts a successful build.

^{Reviewed by Cursor Bugbot for commit ab24582. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Package Artifacts

Built from efb2f73. Download artifacts from this workflow run.

JS SDK (e2b@2.27.2-mishushakov-cli-access-token-methods.0):

npm install ./e2b-2.27.2-mishushakov-cli-access-token-methods.0.tgz

CLI (@e2b/cli@2.10.3-mishushakov-cli-access-token-methods.0):

npm install ./e2b-cli-2.10.3-mishushakov-cli-access-token-methods.0.tgz

Python SDK (e2b==2.25.1+mishushakov-cli-access-token-methods):

pip install ./e2b-2.25.1+mishushakov.cli.access.token.methods-py3-none-any.whl

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ab24582. Configure here.}