golem-custom-snapshot-ts

Snapshot-based recovery speeds up durable agent recovery by compacting the oplog so the agent resumes from the latest snapshot instead of replaying full history. Configure this using the snapshotting option in the @agent decorator.

Yes, you can implement custom binary serialization for TypeScript agent state by overriding the saveSnapshot and loadSnapshot methods in your BaseAgent class, enabling compact state representation and cross-version compatibility.

Configure periodic snapshotting for Golem agents by setting snapshotting: { periodic: '30s' } in the @agent decorator, or use snapshotting: { every: 1 } to trigger a snapshot on every operation for regular oplog compaction.

Custom snapshots are needed for durable agents with frequent state changes like heartbeat loops, polling workflows, recurring tasks, or high-volume event handling, where long oplogs would otherwise slow down recovery and complicate state version upgrades.

Yes, snapshotting supports cross-version upgrades by allowing you to implement a bespoke serialization format with saveSnapshot and loadSnapshot, ensuring consistent byte formats that can adapt when state serialization needs to change between versions.

Without snapshotting, long-running Golem agents become slow to recover because their oplog grows over time, requiring the full history to be replayed. Upgrades are also difficult when state serialization needs to change between versions.