Agent skill

nemoclaw-user-workspace

Backs up and restores OpenClaw workspace files before destructive operations. Use when backing up a sandbox, restoring workspace state, or preparing for a destructive operation. Explains what workspace files are, where they live, and how they persist across sandbox restarts. Use when asking about soul.md, identity.md, memory.md, agents.md, or sandbox file persistence.

View SKILL.md on GitHub Repository
Stars 18,977
Forks 2,322

Install this agent skill to your Project

npx add-skill https://github.com/NVIDIA/NemoClaw/tree/main/.agents/skills/nemoclaw-user-workspace

SKILL.md

NemoClaw User Workspace

Backs up and restores OpenClaw workspace files before destructive operations. Use when backing up a sandbox, restoring workspace state, or preparing for a destructive operation.

Context

OpenClaw stores agent identity, behavior, and memory in a set of Markdown files inside the sandbox. These files live at /sandbox/.openclaw/workspace/ and are read by the agent at the start of every session.

File Reference

Each file controls a distinct aspect of the agent's behavior and memory.

File Purpose Upstream Docs
SOUL.md Core personality, tone, and behavioral rules. SOUL template
USER.md Preferences, context, and facts the agent learns about you. USER template
IDENTITY.md Agent name, creature type, emoji, and self-presentation. IDENTITY template
AGENTS.md Multi-agent coordination, memory conventions, and safety guidelines. AGENTS template
MEMORY.md Curated long-term memory distilled from daily notes. —
memory/ Directory of daily note files (YYYY-MM-DD.md) for session continuity. —

Where They Live

All workspace files reside inside the sandbox filesystem:

text
/sandbox/.openclaw/workspace/
├── AGENTS.md
├── IDENTITY.md
├── MEMORY.md
├── SOUL.md
├── USER.md
└── memory/
    ├── 2026-03-18.md
    └── 2026-03-19.md

Note: The workspace directory is hidden (.openclaw). The files are not at /sandbox/SOUL.md. Use the full path when downloading or uploading.

Persistence Behavior

Understanding when these files persist and when they are lost is critical.

Event Workspace files
Sandbox restart Preserved: the sandbox PVC retains its data.
nemoclaw <name> destroy Lost: the sandbox and its PVC are deleted.

Warning: Always back up your workspace files before running nemoclaw <name> destroy. See Back Up and Restore (see the nemoclaw-user-workspace skill) for instructions.

Editing Workspace Files

The agent reads these files at the start of every session. You can edit them in two ways:

  1. Let the agent do it: Ask your agent to update its persona, memory, or user context during a session.
  2. Edit manually: Use openshell sandbox connect to open a terminal inside the sandbox and edit files directly, or use openshell sandbox upload to push edited files from your host.

Prerequisites

  • A running NemoClaw sandbox (for backup) or a freshly created sandbox (for restore).
  • The OpenShell CLI on your PATH.
  • The sandbox name (shown by nemoclaw list).

Workspace files define your agent's personality, memory, and user context. They persist across sandbox restarts but are permanently deleted when you run nemoclaw <name> destroy.

This guide covers manual backup with CLI commands and an automated script.

Step 1: When to Back Up

  • Before running nemoclaw <name> destroy.
  • Before major NemoClaw version upgrades.
  • Periodically, if you have invested time customizing your agent.

Step 2: Manual Backup

Use openshell sandbox download to copy files from the sandbox to your host.

console
$ SANDBOX=my-assistant
$ BACKUP_DIR=~/.nemoclaw/backups/$(date +%Y%m%d-%H%M%S)
$ mkdir -p "$BACKUP_DIR"

$ openshell sandbox download "$SANDBOX" /sandbox/.openclaw/workspace/SOUL.md "$BACKUP_DIR/"
$ openshell sandbox download "$SANDBOX" /sandbox/.openclaw/workspace/USER.md "$BACKUP_DIR/"
$ openshell sandbox download "$SANDBOX" /sandbox/.openclaw/workspace/IDENTITY.md "$BACKUP_DIR/"
$ openshell sandbox download "$SANDBOX" /sandbox/.openclaw/workspace/AGENTS.md "$BACKUP_DIR/"
$ openshell sandbox download "$SANDBOX" /sandbox/.openclaw/workspace/MEMORY.md "$BACKUP_DIR/"
$ openshell sandbox download "$SANDBOX" /sandbox/.openclaw/workspace/memory/ "$BACKUP_DIR/memory/"

Step 3: Manual Restore

Use openshell sandbox upload to push files back into a sandbox.

console
$ SANDBOX=my-assistant
$ BACKUP_DIR=~/.nemoclaw/backups/20260320-120000  # pick a timestamp

$ openshell sandbox upload "$SANDBOX" "$BACKUP_DIR/SOUL.md" /sandbox/.openclaw/workspace/
$ openshell sandbox upload "$SANDBOX" "$BACKUP_DIR/USER.md" /sandbox/.openclaw/workspace/
$ openshell sandbox upload "$SANDBOX" "$BACKUP_DIR/IDENTITY.md" /sandbox/.openclaw/workspace/
$ openshell sandbox upload "$SANDBOX" "$BACKUP_DIR/AGENTS.md" /sandbox/.openclaw/workspace/
$ openshell sandbox upload "$SANDBOX" "$BACKUP_DIR/MEMORY.md" /sandbox/.openclaw/workspace/
$ openshell sandbox upload "$SANDBOX" "$BACKUP_DIR/memory/" /sandbox/.openclaw/workspace/memory/

Step 4: Using the Backup Script

The repository includes a convenience script at scripts/backup-workspace.sh.

Backup

console
$ ./scripts/backup-workspace.sh backup my-assistant
Backing up workspace from sandbox 'my-assistant'...
Backup saved to /home/user/.nemoclaw/backups/20260320-120000/ (6 items)

Restore

Restore from the most recent backup:

console
$ ./scripts/backup-workspace.sh restore my-assistant

Restore from a specific timestamp:

console
$ ./scripts/backup-workspace.sh restore my-assistant 20260320-120000

Step 5: Verifying a Backup

List backed-up files to confirm completeness:

console
$ ls ~/.nemoclaw/backups/20260320-120000/
AGENTS.md
IDENTITY.md
MEMORY.md
SOUL.md
USER.md
memory/

Step 6: Inspecting Files Inside the Sandbox

Connect to the sandbox to list or view workspace files directly:

console
$ openshell sandbox connect my-assistant
$ ls -la /sandbox/.openclaw/workspace/

Related Skills

  • nemoclaw-user-reference — Commands reference
  • nemoclaw-user-monitor-sandbox — Monitor Sandbox Activity

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

NVIDIA/NemoClaw

nemoclaw-user-skills-coding

Describes the agent skills shipped with NemoClaw and how to access them by cloning the repository. Use when users ask about AI agent support, coding assistant integration, or the .agents/skills/ directory.

18,977 2,322
Explore
NVIDIA/NemoClaw

nemoclaw-user-configure-inference

Lists all inference providers offered during NemoClaw onboarding. Use when explaining which providers are available, what the onboard wizard presents, or how inference routing works. Changes the active inference model without restarting the sandbox. Use when switching inference providers, changing the model runtime, or reconfiguring inference routing. Connects NemoClaw to a local inference server. Use when setting up Ollama, vLLM, TensorRT-LLM, NIM, or any OpenAI-compatible local model server with NemoClaw.

18,977 2,322
Explore
NVIDIA/NemoClaw

nemoclaw-maintainer-day

Runs the daytime maintainer loop for NemoClaw, prioritizing items labeled with the current version target. Picks the highest-value item, executes the right workflow (merge gate, salvage, security sweep, test gaps, hotspot cooling, or sequencing), and reports progress. Use during the workday to land PRs and close issues. Designed for /loop (e.g. /loop 10m /nemoclaw-maintainer-day). Trigger keywords - maintainer day, work on PRs, land PRs, make progress, what's next, keep going, maintainer loop.

18,977 2,322
Explore
NVIDIA/NemoClaw

nemoclaw-user-manage-policy

Reviews and approves blocked agent network requests in the TUI. Use when approving or denying sandbox egress requests, managing blocked network calls, or using the approval TUI. Adds, removes, or modifies allowed endpoints in the sandbox policy. Use when customizing network policy, changing egress rules, or configuring sandbox endpoint access.

18,977 2,322
Explore
NVIDIA/NemoClaw

nemoclaw-user-overview

Explains how OpenClaw, OpenShell, and NemoClaw form the ecosystem, NemoClaw's position in the stack, what NemoClaw adds beyond the community sandbox, and when to prefer NemoClaw versus integrating OpenShell and OpenClaw directly. Use when users ask about the relationship between OpenClaw, OpenShell, and NemoClaw, or when to use NemoClaw versus OpenShell. Describes how NemoClaw works internally: CLI, plugin, blueprint runner, OpenShell orchestration, inference routing, and protection layers. Use for sandbox lifecycle and architecture mechanics; not for product definition (Overview) or multi-project placement (Ecosystem). Explains what NemoClaw covers: onboarding, lifecycle management, and management of OpenClaw within OpenShell containers, plus capabilities and why it exists. Use when users ask what NemoClaw is or what the project provides. For ecosystem placement or OpenShell-only paths, use the Ecosystem page; for internal mechanics, use How It Works. Lists changelogs and feature history for NemoClaw rel...

18,977 2,322
Explore
NVIDIA/NemoClaw

nemoclaw-maintainer-find-review-pr

Finds open GitHub PRs with security and priority-high labels, links each to its issue, detects duplicates (multiple PRs fixing the same issue), and presents a table of review candidates. Use when looking for the next PR to review. Trigger keywords - find pr, find review, next pr, pr to review, duplicate pr, security pr.

18,977 2,322
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results