e2b@2.63.0
E2B 2.63.0 adds a strict option to sandbox pause operations and improves handling of unresponsiveness during resume.
Why this signal matters
In release 2.63.0, E2B introduces the strict flag to pause() (defaulting to false ). When strict is set to true , attempting to pause while the guest agent is unresponsive triggers a ServiceBusyError / ServiceBusyException , preventing the pause and leaving the sandbox active. Under the default non-strict behavior, memory snapshots are taken and marked as envdUnresponsiveAtPause . Resuming a sandbox with this mark now raises GuestUnresponsiveError / GuestUnresponsiveException unless onResume: 'reboot' / on resume="reboot" is explicitly passed.
Actionable summary
E2B release 2.63.0 introduces a strict parameter (default false ) to pause() . If strict is enabled and the guest agent is unresponsive, pause fails with ServiceBusyError while keeping the sandbox running. Non-strict pauses still take marked snapshots, which require onResume: 'reboot' to avoid GuestUnresponsiveError on resume.
- Agent usefulness
- 77/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Opt in to strict: true on pause() calls if sandboxes must not be paused while guest agents are unresponsive.
- Handle GuestUnresponsiveError when resuming sandboxes, or configure onResume: 'reboot' for sandboxes marked with envdUnresponsiveAtPause .