golem-configure-durability-ts

Configure durable or ephemeral state persistence for TypeScript Golem agents.

Updated May 17, 2026
One-click install
npx skills add https://github.com/Rust-soham/golem-claw --skill golem-configure-durability-ts-rust-soham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golem-configure-durability-ts
Source: https://github.com/Rust-soham/golem-claw/tree/main/packages/golem/.agents/skills/golem-configure-durability-ts
Command: npx skills add https://github.com/Rust-soham/golem-claw --skill golem-configure-durability-ts-rust-soham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you correctly select and configure agent durability in a TypeScript Golem project so your agent either persists state safely across invocations or stays stateless for lower overhead.

Core Features & Use Cases

  • Durable agents (default): Persist state and record side effects in an oplog for automatic recovery after failures and restarts.
  • Durable with periodic snapshots: Keep durable guarantees while speeding recovery by starting from the latest snapshot instead of replaying the full oplog.
  • Ephemeral agents: Run statelessly per invocation with no oplog, discarding state when the call finishes.

Quick Start

Tell your AI assistant that your agent must persist workflow state across retries and restarts, and ask it to configure the agent as durable or durable with periodic snapshots depending on how long-running and oplog-intensive the workload is.

Frequently Asked Questions about golem-configure-durability-ts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the difference between durable and ephemeral agents in Golem?

To configure state persistence for a TypeScript Golem agent, select durable mode to safely persist state and record side effects in an oplog for automatic recovery after failures and restarts.

How do I speed up oplog replay cost during agent recovery?

Durable Golem agents persist state and record side effects in an oplog for recovery, while ephemeral agents run statelessly per invocation with no oplog, discarding state when the call finishes.

When should I use ephemeral mode for a TypeScript agent?

To speed up oplog replay cost during recovery, configure durable agents with periodic snapshotting, which allows recovery to start from the latest snapshot instead of replaying the full oplog.

Does Golem support stateless per-invocation request handling in TypeScript?

Use ephemeral mode for stateless per-invocation request handling when you need lower overhead and do not need to persist workflow state across retries, restarts, or long-running polling loops.

What are the limitations of durable agent oplog replay for long-running workflows?

Yes, Golem supports stateless per-invocation request handling in TypeScript by configuring agents as ephemeral, which discards state when the call finishes and avoids oplog overhead.

What are the limitations of durable agent oplog replay for long-running workflows?

For long-running heartbeats and polling loops, durable agent oplog replay can become expensive during recovery, a limitation you can mitigate by enabling periodic snapshots to reduce replay cost.