Relocate the complete WorkBuddy data directory to a non-system drive with a Windows junction while preserving existing paths and runtime compatibility.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install workbuddy-data-migration
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install workbuddy-data-migration using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is WorkBuddy Data Directory Migration?
This Openclaw Skills workflow migrates WorkBuddy's complete data root from C:\Users\USER\.workbuddy to a fixed destination such as E:\workbuddy-data. It uses a Windows directory junction so WorkBuddy continues accessing its original path while conversations, sessions, skills, logs, caches, databases, and runtimes are physically stored on the non-system drive.
Unlike an environment-variable-only relocation, this approach also covers WorkBuddy's hardcoded binaries directory, including Python and Node runtimes that can consume several gigabytes. The migration includes safety checks, copy verification, junction validation, and optional cleanup of nonessential caches.
WorkBuddy Data Directory Migration Use Cases
- Free space on C: when WorkBuddy data, runtimes, or caches are a major contributor.
- Move WorkBuddy's environment, cache, logs, or runtime files to an E: or other non-system disk.
- Preserve hardcoded WorkBuddy paths without changing application configuration.
- Relocate data after a WorkBuddy reinstall recreates
C:\Users\USER\.workbuddy. - Ensure Python, Node, GPU-related packages, and future runtimes remain off the system drive.
- Diagnose migration failures on trimmed Windows images with restricted PATH or custom file-operation behavior.
How WorkBuddy Data Directory Migration Works
- Inventory the system. Measure the WorkBuddy data directory, relevant AppData leftovers, and available space on each disk without changing files.
- Request confirmation. Present the proposed cleanup and migration plan before deleting any data.
- Optionally clean safe caches. Remove approved pip caches, stale installers, old traces, logs, or Electron session caches while preserving conversations, projects, sessions, blobs, and
workbuddy.db. - Stage the runtime. The batch launcher copies
node.exetoC:\migrate_tmpso the migration process is not locked inside the directory being moved. - Copy and verify. The Node.js migration script copies the WorkBuddy root to the destination and verifies that the copy is complete.
- Replace the original directory. The script renames the original C: directory and creates a junction from
C:\Users\USER\.workbuddyto the non-system destination. - Run self-checks. It confirms the junction target, verifies Node and WorkBuddy files remain reachable through the original path, checks
workbuddy.db, and confirms reclaimed C: space. - Maintain the relocation. Future files and runtimes written through the original WorkBuddy path are redirected to the destination automatically. Re-run the migration if a reinstall replaces the junction.
WorkBuddy Data Directory Migration Setup
Prerequisites
- Windows with the bundled skill files available.
- A fixed non-system destination such as
E:\workbuddy-datawith sufficient free space. - WorkBuddy fully closed before migration.
- Permission to read and write both the source and destination drives.
- Explicit user confirmation before any optional cache cleanup or deletion.
Run the migration
No package installation or environment-variable configuration is required. Use the bundled ASCII launcher by double-clicking scripts\migrate.bat from the skill directory. It stages Node.js, invokes the migration logic, performs verification, and cleans up its temporary runtime.
For a command-line launch from a Windows shell, use:
scripts\\migrate.bat
If the destination is different from the default configured by the script, review scripts\migrate.js and set the intended fixed destination before running it. Do not use an environment-variable-only solution because the WorkBuddy binaries path is hardcoded. After completion, reopen WorkBuddy and confirm conversations, sessions, skills, and runtimes are available.
If the migration fails silently, consult references\lessons.md. Prefer the bundled Node-native implementation; avoid relying on powershell, mklink, robocopy, or an inherited PATH on trimmed Windows images.
WorkBuddy Data Directory Migration Data Schema & Taxonomy
Source and destination
| Element | Location or behavior |
|---|---|
| Original WorkBuddy root | C:\Users\USER\.workbuddy |
| Recommended destination | A fixed non-system path such as E:\workbuddy-data |
| Redirect mechanism | Windows directory junction from the original root to the destination |
| Temporary runtime staging | C:\migrate_tmp during execution |
| Main database | workbuddy.db, preserved and validated |
Data taxonomy
projects\: conversation and project history; never delete during cleanup.sessions\: session records; preserved during migration.skills\: installed skill data and related metadata.logs\: runtime and application logs; old traces may be cleaned only with confirmation.blobs\: stored conversation or application blobs; never delete as ordinary cache data.binaries\: hardcoded Python and Node runtimes, including packages such as GPU-enabled Whisper dependencies.- App and session directories: application state and Electron-related data.
- Caches: pip, Electron, and stale installer files that may be eligible for optional cleanup.
The junction preserves the original path taxonomy while moving the underlying bytes. New subdirectories and runtime installations automatically inherit the destination location.
WorkBuddy Data Directory Migration Advanced Features
- Filesystem-level compatibility: Covers hardcoded paths that do not honor
WORKBUDDY_CONFIG_DIR. - Runtime protection: Stages Node.js outside the managed directory to avoid self-locking during rename and migration.
- Node-native operations: Uses
fs.cpSyncfor copying andfs.symlinkSync(destination, source, "junction")for junction creation without depending on shell tools. - Database-safety gate: Protects
workbuddy.dband validates that it remains accessible after relocation. - Copy-completeness gate: Verifies the destination before replacing the original directory.
- Post-migration self-checks: Confirms junction type, resolved target, runtime reachability, database validity, and recovered disk space.
- Reinstall recovery: Supports rerunning the migration when a WorkBuddy reinstall recreates the C: directory.
- Trimmed-Windows resilience: Avoids PowerShell and external command dependencies, with forensic troubleshooting guidance in
references\lessons.md. - Conservative cleanup policy: Separates optional cache removal from migration and explicitly protects user history and application data.
SKILL.md
Loading
Related Openclaw Skills
1F3EA Marketplace
1F3EA Marketplace gives AI agents a controlled way to browse, trade, and participate in an agent-only digital marketplace.
FDE Adoption and Value
Convert post-POC evidence into a traceable adoption plan, value measurement framework, and evidence-based investment decision.
Student Life Planner
Student Life Planner turns a student's tasks, fixed events, and deadlines into a realistic, prioritized daily or weekly schedule.
PM Interview Grill Me
An intensive AI product manager interview simulator that asks challenging questions, probes your reasoning, and delivers immediate coaching after every answer.
Account Video Downloader
A command-line skill that retrieves, analyzes, and batch-downloads public account content from Douyin, Kuaishou, Bilibili, and YouTube.
QuickClass Quiz Converter
QuickClass Quiz Converter transforms Word documents, PDFs, scanned worksheets, and images into structured QuickClass homework and quiz JSON.
Featured*
