e2b@2.55.0
E2B released version 2.55.0, introducing a new SnapshotMode option ('full' vs 'filesystem') for snapshots and pauses, while deprecating the keepMemory flag.
Why this signal matters
E2B 2.55.0 introduces minor updates to sandbox snapshot and pause mechanics. The new SnapshotMode type allows configuring snapshots as 'full' (default memory snapshot) or 'filesystem' . Under 'filesystem' mode, memory is not saved, resulting in faster and smaller snapshots from which sandboxes perform a cold-boot from disk; the source sandbox continues running in either mode. The pause() method and lifecycle timeout pause configurations now accept this mode property, replacing the now-deprecated keepMemory option ( keepMemory: false maps to mode: 'filesystem' ). Supplying both arguments raises an InvalidArgument error. Additionally, dead empty-chunk checks were cleaned up from command output handling without behavioral changes.
Actionable summary
E2B v2.55.0 adds mode: 'full' | 'filesystem' (SnapshotMode) to createSnapshot , pause , and lifecycle timeout settings. filesystem persists only disk state for faster snapshots and cold-boot restarts. keepMemory is deprecated in favor of mode .
- Agent usefulness
- 94/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Migrate existing usages of keepMemory to mode: 'filesystem' or mode: 'full' in pause() calls and lifecycle timeout settings.
- Adopt mode: 'filesystem' in createSnapshot workflows where faster, disk-only cold-boot snapshots are preferred over full memory restores.