E2B SDK 2.63 adds strict pause, and resuming an unresponsive snapshot now throws unless you reboot (November 4, 2026)

What you get

On November 4, 2026 E2B released version 2.63.0 of its JavaScript SDK (e2b) and its Python SDK (@e2b/python-sdk@2.63.0 on GitHub). Both add a strict option to pause(). Both also change what happens when you resume some paused sandboxes.

• New strict option, default false. With strict: true (JS) or strict=True (Python), pause is refused while the sandbox's guest agent isn't responding. You get ServiceBusyError (JS) or ServiceBusyException (Python), and the sandbox keeps running.
• Default behaviour. Without strict, the memory snapshot is taken anyway and marked. Sandbox info shows the mark as envdUnresponsiveAtPause (JS) or envd_unresponsive_at_pause (Python).
• Behaviour change. Resuming a marked sandbox without onResume: 'reboot' (JS) or on_resume="reboot" (Python) now throws GuestUnresponsiveError (JS) or GuestUnresponsiveException (Python). Code that resumed these sandboxes before can now fail.

Prerequisites

• An E2B API key in E2B_API_KEY
• The E2B JavaScript or Python SDK at 2.63.0

Steps

1. Upgrade the SDK to 2.63.0.
2. If you pause sandboxes and want to be sure the snapshot is healthy, pass strict: true (JS) or strict=True (Python) to pause(). Catch ServiceBusyError or ServiceBusyException and retry later. The sandbox is still running when this happens.
3. Where you resume paused sandboxes, read the sandbox info first. If envdUnresponsiveAtPause or envd_unresponsive_at_pause is true, resume with or .