golem-interrupt-resume-agent

Interrupt and resume Golem agents while preserving their state.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the need to temporarily stop a misbehaving or long-running Golem agent without losing its preserved state, then continue processing later from where it left off.

Core Features & Use Cases

  • Interrupt a running agent: Stops execution immediately while preserving state so it transitions to an Interrupted status.
  • Resume an interrupted agent: Restores normal execution and continues processing, including queued invocations.
  • Operational guidance for agent states: Helps you understand when interrupt is valid (Running only) versus when agents are already paused due to suspension.

Quick Start

Interrupt a specific agent instance to pause execution, then resume it when you are ready, using your agent ID or language-specific agent identifier.

Frequently Asked Questions about golem-interrupt-resume-agent

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

FAQPage Schema
How do I pause a running Golem agent without losing its state?

To pause a running Golem agent without losing state, you interrupt the agent instance, which immediately halts execution and transitions its status to Interrupted while preserving all current data.

Can I resume an interrupted Golem agent and continue processing queued tasks?

Yes, you can resume an interrupted Golem agent to restore normal execution, which allows it to continue processing from where it left off and handles any queued invocations.

When should I interrupt a Golem agent during CLI workflows?

You should interrupt a Golem agent during CLI workflows when you need to safely halt long-running work, prevent further invocations during maintenance, or inspect queued tasks before resuming.

Does Golem CLI support transitioning agent states between Running and Interrupted?

Yes, this functionality requires Golem CLI support for agent status transitions between Running and Interrupted, and you must target the appropriate agent identifier format for your agent's language.

Why does interrupting a Golem agent fail when it is already suspended?

Interrupting a Golem agent fails when already suspended because interrupt is only valid for agents with a Running status, whereas paused agents are already halted due to suspension.