golem-undo-agent-state

Revert an agent's state by undoing recorded operations via oplog index or invocation count.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you recover from unwanted agent behavior or failed runs by reverting an agent to a prior state.

Core Features & Use Cases

  • Undo recorded operations: Reverts an agent by undoing its last recorded operations to roll back side effects.
  • Rollback to a specific point: Restores state either by specifying an oplog index or by choosing the last N invocations.
  • Use case: If an agent invocation made incorrect changes and you want to immediately undo the impact, you can revert those operations instead of manually repairing state.

Quick Start

Run golem agent revert <AGENT_ID> --number-of-invocations 1 to undo the agent’s most recent invocation.

Frequently Asked Questions about golem-undo-agent-state

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

FAQPage Schema
How do I roll back an agent's state after a failed invocation?

To roll back agent state after a failed invocation, you revert the agent by undoing its recorded operations. You can specify either an oplog index or the number of invocations to reverse, deterministically restoring the prior state.

What is the best way to undo the side effects of an agent run?

Undoing agent side effects involves reverting recorded operations using oplog indices or invocation counts. This approach applies deterministic reversal to the operation history, removing the need to manually repair the state.

Can I revert an agent to a specific oplog index or do I have to count invocations?

You can revert an agent to a specific oplog index, or you can choose to undo the last N invocations. These two selection methods are mutually exclusive, allowing flexible control over state restoration.

How do I undo an agent's most recent invocation?

To undo an agent's most recent invocation, run the revert command with the agent identifier and set the number-of-invocations parameter to 1. This immediately reverses the side effects of that specific run.

When do I need to use invocation rollback for error recovery?

Invocation rollback is needed when an agent makes incorrect changes during a run and you want to immediately undo the impact. It provides controlled state restoration by applying deterministic reversal to the operation history.

Are there limitations when restoring agent state using oplog indices?

Restoring agent state requires a valid agent identifier and uses either a last-oplog-index or number-of-invocations parameter. These two selection methods are mutually exclusive, meaning you cannot combine them in a single rollback operation.