migrate-from-v1

Migrate agent state, permissions, and configuration files from NanoClaw v1 to v2.

Updated Jun 27, 2026

Search Tags:#automation #deployment #migration #agent #configuration #nanoclaw

Ready to run

npx skills add https://github.com/VincentChong123/nanoclaw-v2-agy-api-proxy --skill migrate-from-v1-vincentchong123

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrate-from-v1
Source: https://github.com/VincentChong123/nanoclaw-v2-agy-api-proxy/tree/main/.claude/skills/migrate-from-v1
Command: npx skills add https://github.com/VincentChong123/nanoclaw-v2-agy-api-proxy --skill migrate-from-v1-vincentchong123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the complex, non-deterministic transition of agent state, user permissions, and custom configurations from NanoClaw v1 to the v2 architecture, ensuring continuity of service.

Core Features & Use Cases

State Migration: Safely reconciles database records, session transcripts, and channel authentication state.
Configuration Cleanup: Automatically prunes legacy v1 boilerplate from agent documentation while preserving user-defined personality traits.
Access Control: Maps legacy sender allowlists to the new v2 role-based access control system.

Quick Start

Invoke the migrate from v1 skill to begin the final phase of your agent transition after running the initial migration script.

Frequently Asked Questions about migrate-from-v1

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

FAQPage Schema

How do I migrate agent state and configuration from NanoClaw v1 to v2?▼

To migrate agent state, you invoke the migration skill to automatically reconcile database records, session transcripts, and configuration files from NanoClaw v1 to the v2 architecture. This ensures continuity of service during the transition.

Can I automatically map v1 sender allowlists to v2 role-based access control?▼

Yes, the migration process automatically maps legacy sender allowlists to the new v2 role-based access control system. This access control mapping ensures user permissions are correctly transitioned to the v2 architecture.

What do I need to run the NanoClaw v1 to v2 migration process?▼

You need access to the local filesystem data of the v1 installation path and the v2 migration handoff logs. These are required to perform the final reconciliation and cleanup tasks for your agent transition.

Does the NanoClaw migration preserve my custom agent personality traits?▼

Yes, the configuration cleanup process automatically prunes legacy v1 boilerplate from agent documentation while specifically preserving your user-defined personality traits. This maintains your agent's custom behavior in v2.

What's the best way to clean up legacy v1 boilerplate during an agent migration?▼

The best way to clean up legacy boilerplate is to automate the transition using a migration skill that prunes v1 documentation while preserving user-defined configurations. This safely reconciles state and container configurations.