Document timeout behavior after sandbox auto-resume

docs/sandbox/auto-resume.mdx

@@ -54,6 +54,24 @@
 
 If you use `autoResume: false`, resume explicitly with [`Sandbox.connect()`](/docs/sandbox/connect).
 
+## Timeout after auto-resume
+
+When a sandbox auto-resumes, it starts a **new timeout equal to the original timeout set at creation**.
+The countdown begins from the moment the sandbox resumes, not from when it was first created.
+
+For example, if you create a sandbox with a 10-minute timeout:
+
+1. The sandbox runs for 10 minutes, then pauses.
+2. Activity arrives and the sandbox auto-resumes.
+3. A fresh 10-minute timeout starts.
+4. If no further activity resets the timeout, the sandbox pauses again after 10 minutes.
+
+This cycle repeats every time the sandbox auto-resumes — the lifecycle configuration (`onTimeout: "pause"` + `autoResume: true`) is persistent across pause/resume cycles.
+
+<Note>
+You can change the timeout after the sandbox resumes by calling `setTimeout`/`set_timeout`. See [Change sandbox timeout during runtime](/docs/sandbox#change-sandbox-timeout-during-runtime).
+</Note>
+
 ## What counts as activity
 
 Auto-resume is triggered by the sandbox activity - that's both HTTP traffic and controlling the sandbox from the SDK.
@@ -152,7 +170,7 @@
 
 await new Promise((resolve) => setTimeout(resolve, 1000))
 
 const previewHost = sandbox.getHost(3000)
 console.log(`Preview URL: https://${previewHost}`)
 
 console.log(`Status before pause: ${(await sandbox.getInfo()).state}`)
@@ -254,7 +272,7 @@
 ```js JavaScript & TypeScript
 import { Sandbox } from 'e2b'
 
 const userSandboxes = new Map() // userId → Sandbox
 
 async function getSandbox(userId) {
   let sandbox = userSandboxes.get(userId)
@@ -304,5 +322,6 @@
 
 ## Cleanup
 Auto-resume is persistent, meaning if your sandbox resumes and later times out again, it will pause again.
+Each time the sandbox resumes, the original timeout resets — so the sandbox keeps cycling between running and paused as long as activity arrives.
 
 If you call `.kill()`, the sandbox is permanently deleted and cannot be resumed.

docs/sandbox/persistence.mdx

@@ -76,7 +76,7 @@
 ```js JavaScript & TypeScript highlight={8-9}
 import { Sandbox } from '@e2b/code-interpreter'
 
 const sbx = await Sandbox.create()
 console.log('Sandbox created', sbx.sandboxId)
 
 // Pause the sandbox
@@ -106,7 +106,7 @@
 ```js JavaScript & TypeScript highlight={12-13}
 import { Sandbox } from '@e2b/code-interpreter'
 
 const sbx = await Sandbox.create()
 console.log('Sandbox created', sbx.sandboxId)
 
 // Pause the sandbox
@@ -115,7 +115,7 @@
 console.log('Sandbox paused', sbx.sandboxId)
 
 // Connect to the sandbox (it will automatically resume the sandbox, if paused)
 const sameSbx = await sbx.connect()
 console.log('Connected to the sandbox', sameSbx.sandboxId)
 ```
 ```python Python highlight={12-13}
@@ -144,7 +144,7 @@
 import { Sandbox, SandboxInfo } from '@e2b/code-interpreter'
 
 // List all paused sandboxes
 const paginator = Sandbox.list({ query: { state: ['paused'] } })
 
 // Get the first page of paused sandboxes
 const sandboxes = await paginator.nextItems()
@@ -179,7 +179,7 @@
 ```js JavaScript & TypeScript highlight={11,14}
 import { Sandbox } from '@e2b/code-interpreter'
 
 const sbx = await Sandbox.create()
 console.log('Sandbox created', sbx.sandboxId)
 
 // Pause the sandbox
@@ -209,13 +209,13 @@
 </CodeGroup>
 
 ## Sandbox's timeout
-When you connect to a sandbox, the inactivity timeout resets. The default is 5 minutes, but you can pass a custom timeout to the `Sandbox.connect()` method:
+When you connect to a sandbox (or it auto-resumes), the timeout resets to the value originally set at creation time. The default is 5 minutes, but you can pass a custom timeout to the `Sandbox.connect()` method:
 
 <CodeGroup>
 ```js JavaScript & TypeScript
 import { Sandbox } from '@e2b/code-interpreter'
 
 const sbx = await Sandbox.connect(sandboxId, { timeoutMs: 60 * 1000 }) // 60 seconds
 ```
 ```python Python
 from e2b_code_interpreter import Sandbox