Files

T

Mish Ushakov 2defe39bd7 feat(cli): rename team to project in ~/.e2b/config.json (#1570 )

Bumps `~/.e2b/config.json` to `version: 2` and renames
`teamName`/`teamId`/`teamApiKey` to
`projectName`/`projectId`/`projectApiKey`. The rename is internal to the
config file format — all user-facing CLI output, flags (`--team`), and
env vars (`E2B_TEAM_ID`) still say "team", and API `teamID` parameters
are unchanged.

Existing v1 configs keep working: they are converted to the new format
in memory on read, and the file on disk is left untouched — the v2
format is only persisted through paths that write the config anyway
(login, `e2b auth configure`, token refresh), so older CLI versions can
still read the file in the meantime. Unrecognized configs are no longer
deleted either; the CLI treats them as signed out and `e2b auth login`
overwrites them. Tools that read the config file directly must handle
the new field names once the file is written in the v2 format.

## Usage

```jsonc
// ~/.e2b/config.json (fresh login, or any config write after upgrading)
{
  "version": 2,
  "projectName": "default",
  "projectId": "team-id",
  "projectApiKey": "e2b_...",
  // identity, oauth, tokens, last_refresh unchanged
}
```

CLI output is unchanged:

```bash
$ e2b auth info
You are logged in as user@example.com,
Selected team: default (team-id)
```

## Testing

`user_config_migration.test.ts` covers in-memory v1→v2 migration, v2
pass-through, and unrecognized configs being treated as signed out
without deleting the file; existing config-permissions and backend
integration tests updated to the new fields. `format`, `lint`,
`typecheck`, `build`, and `pnpm run test` pass (backend integration
suites are environment-gated on credentials).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

2026-07-23 14:22:31 +02:00

src

feat(cli): rename team to project in ~/.e2b/config.json (#1570 )

2026-07-23 14:22:31 +02:00

testground/demo-basic

New infra (#212 )

2023-11-06 15:07:09 +01:00

tests

feat(cli): rename team to project in ~/.e2b/config.json (#1570 )

2026-07-23 14:22:31 +02:00

.envrc

Ensure that httpx transport is reused across calls by default (#997 )

2025-11-14 16:48:29 -08:00

.gitignore

feat: add template migration to CLI (#880 )

2025-09-19 17:41:28 +02:00

.prettierignore

feat: add template init for new template SDK (#881 )

2025-09-26 06:40:58 -07:00

LICENSE

Added license sources to SDKs (#761 )

2025-06-05 07:10:07 -07:00

package.json

[skip ci] Release new versions

2026-07-23 11:03:38 +00:00

README.md

docs: fix duplicate logo on NPM/PyPI by switching to <picture> element (#1466 )

2026-06-19 19:26:46 +00:00

tsconfig.json

chore(js-sdk,cli): modernize tsconfig and adopt TypeScript 7 (side-by-side) (#1536 )

2026-07-09 18:35:15 +00:00

tsdown.config.ts

build: switch from tsup to tsdown (#1515 )

2026-07-09 19:04:03 +02:00

vitest.config.ts

fix: CLI tests setup (#969 )

2025-10-17 05:03:18 -07:00

README.md

E2B CLI

This CLI tool allows you to build manager your running E2B sandbox and sandbox templates. Learn more in our documentation.

1. Install the CLI

Using Homebrew (on macOS)

brew install e2b

Using NPM

npm install -g @e2b/cli

2. Authenticate

e2b auth login

Note

To authenticate without the ability to open the browser, provide E2B_ACCESS_TOKEN as an environment variable. You can find your token in Account Settings under the Team selector at e2b.dev/dashboard. Then use the CLI like this: E2B_ACCESS_TOKEN=sk_e2b_... e2b template create.

Important

Note the distinction between E2B_ACCESS_TOKEN and E2B_API_KEY.

3. Check out docs

Visit our CLI documentation to learn more.