nemoclaw-user-workspace

Back up and restore NemoClaw workspace files under /sandbox/.openclaw/workspace/.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/bga23/NemoClaw --skill nemoclaw-user-workspace-bga23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-user-workspace
Source: https://github.com/bga23/NemoClaw/tree/main/.agents/skills/nemoclaw-user-workspace
Command: npx skills add https://github.com/bga23/NemoClaw --skill nemoclaw-user-workspace-bga23

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Back up and restore NemoClaw workspace files to prevent loss of agent personality, memory, and configuration during sandbox operations.

Core Features & Use Cases

  • Snapshot-based backups capture all workspace state directories defined in the agent manifest to durable backups.
  • Manual backup and restore guide for copying workspace files to and from a host, ensuring quick recovery after destructive actions.
  • Scripted backup tooling provides automation to simplify regular backups and restorations.

Quick Start

Run the backup script to create a restore-ready copy of the workspace for your agent.

Frequently Asked Questions about nemoclaw-user-workspace

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

FAQPage Schema
How do I back up and restore NemoClaw workspace files before a sandbox destruction?

To back up and restore NemoClaw workspace files, you can use snapshot-based backups or manually copy the files located under /sandbox/.openclaw/workspace/ and the memory directory to a durable location to ensure quick recovery after destructive actions.

What is the best way to preserve agent personality and memory during a sandbox upgrade?

The best way to preserve agent personality and memory during a sandbox upgrade is to create a snapshot-based backup of all workspace state directories defined in the agent manifest, ensuring your configuration and memory persist across the migration.

Do I need to manually copy workspace files to protect my configuration during sandbox restarts?

You do not always need to manually copy workspace files during sandbox restarts, as the provided references describe file persistence behaviors during restarts, but manual backup is recommended before complete sandbox destruction to ensure safety.

Can I automate NemoClaw workspace backups for regular migrations?

You can automate NemoClaw workspace backups using the provided scripted backup tooling, which simplifies regular backups and restorations to generate a restore-ready copy of the workspace for your agent.

What limitations exist when restoring a workspace snapshot to a new sandbox environment?

A key limitation is that snapshot-based backups only capture workspace state directories defined in the agent manifest, so any files outside the /sandbox/.openclaw/workspace/ and memory directory may not persist during complete sandbox destruction or migration.