CLI resets the timeout to 5 minutes after connecting to a running Sandbox

[mishushakov]

Describe the bug

CLI overrides the Sandbox timeout to 5 minutes after calling e2b sbx connect <sandbox id>.

To Reproduce

1. I launch a sandbox via the API with 30 minutes timeout - works great
2. I don't do anything else on the sandbox via the API
3. I log in to the sandbox using the E2B CLI
4. The sandbox is killed exactly 5 minutes after I logged in via the CLI.

Expected behavior
The timeout should be kept as is.

Terminal commands & output

Before connecting via CLI (30 min timeout):

icavd7j6rub8vi6fczr7x  rki5dems9wqfm4r03t7g  base   12/22/2025, 2:06:31 PM  12/22/2025, 2:36:31 PM  Running  2      512      0.4.3         {}

After connecting via CLI (5 min timeout):

icavd7j6rub8vi6fczr7x  rki5dems9wqfm4r03t7g  base   12/22/2025, 2:06:31 PM  12/22/2025, 2:11:45 PM  Running  2      512      0.4.3         {}

Additional context
CLI version: 2.3.1

[linear]

ENG-3403