Document timeout behavior after sandbox auto-resume (#174)

* Document timeout behavior after sandbox auto-resume

- Add new 'Timeout after auto-resume' section to auto-resume.mdx explaining
  that the original timeout resets from the moment the sandbox resumes
- Include a step-by-step example of the pause/resume/timeout cycle
- Note that setTimeout/set_timeout can override the timeout after resume
- Update cleanup section to reinforce the timeout reset behavior
- Update persistence.mdx timeout section to mention auto-resume resets

Co-authored-by: Vasek Mlejnsky <vasek.mlejnsky@gmail.com>

* Fix auto-resume timeout docs: sandbox gets default 5min, not creation timeout

* Fix auto-resume timeout: use max(5min, original timeout), not flat 5min

* Improve auto-resume timeout wording for clarity

* Trigger Mintlify preview rebuild

* Trigger Mintlify preview rebuild

---------

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Tomas Beran <tomas.beran@e2b.dev>

Author: 3 people

docs/sandbox/auto-resume.mdx

@@ -54,6 +54,26 @@ sandbox = Sandbox.create(
 
 If you use `autoResume: false`, resume explicitly with [`Sandbox.connect()`](/docs/sandbox/connect).
 
+## Timeout after auto-resume
+
+When a sandbox auto-resumes, it restarts with a **5-minute minimum timeout**. If you originally created the sandbox with a longer timeout, that value carries over.
+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 2-minute timeout:
+
+1. The sandbox runs for 2 minutes, then pauses.
+2. Activity arrives and the sandbox auto-resumes.
+3. A 5-minute timeout starts (the 5-minute minimum applies because the original timeout was shorter).
+4. If no further activity resets the timeout, the sandbox pauses again after 5 minutes.
+
+If you create a sandbox with a 1-hour timeout, the auto-resume timeout will also be 1 hour, since it exceeds the 5-minute minimum.
+
+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.
@@ -304,5 +324,5 @@ print(result.stdout)
 
 ## Cleanup
 Auto-resume is persistent, meaning if your sandbox resumes and later times out again, it will pause again.
-
+Each time the sandbox resumes, it gets a fresh timeout (at least 5 minutes, or longer if the original creation timeout exceeds that) — 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

@@ -209,7 +209,7 @@ Sandbox.kill(sbx.sandbox_id)
 </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, the timeout resets. The default is 5 minutes, but you can pass a custom timeout to the `Sandbox.connect()` method:
 
 <CodeGroup>
 ```js JavaScript & TypeScript