golem-redeploy-agents

Delete and recreate Golem agents to run the latest component version without persisted state.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the need to reset running Golem agents so they start cleanly with the latest component version when persisted state can’t be safely migrated.

Core Features & Use Cases

  • Redeploy agents by recreating them: Deletes each existing agent and recreates it with the same identity, environment variables, and configuration while switching the component to the newest deployed version.
  • State reset with clear data-loss expectations: Permanently removes the agent’s oplog, internal WASM state, and KV storage data so the agent behaves like newly created.
  • Fast operational workflow: Supports redeploying during deploy via a deploy flag or setting an environment-level default in the application manifest for repeated development cycles.

Quick Start

Run golem deploy with redeploy-agents enabled to delete and recreate existing agents so they restart cleanly on the latest component version.

Frequently Asked Questions about golem-redeploy-agents

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

FAQPage Schema
How do I reset Golem agents to run on the latest component version?

Reset Golem agents by deleting and recreating them during deployment, which switches them to the newest component version while permanently clearing their oplog, internal WASM state, and KV storage data.

When do I need to redeploy agents instead of updating them in place?

Redeploy agents when breaking component changes make persisted state incompatible, or during development iterations where preserving the oplog, internal WASM state, and KV storage is not required.

Does agent redeployment preserve environment variables and WASI configuration?

Agent redeployment preserves environment variables and WASI configuration by recreating the agent with the same identity and name, while ensuring only the persisted state is permanently removed.

How do I enable agent redeployment during a Golem deploy?

Enable agent redeployment by using the redeploy-agents deploy flag during the golem deploy command, or by setting an environment-level default in the application manifest for repeated development cycles.

What agent state data is lost when redeploying Golem agents?

Redeploying Golem agents permanently removes the oplog, internal WASM state, and KV storage data, making the agent behave like a newly created instance with a fresh state on the latest component version.

Can I set agent redeployment as a default for development iterations?

Set agent redeployment as an environment-level default in the application manifest to automatically delete and recreate existing agents on each deploy, streamlining repeated development cycles without state preservation.