migrate-from-v1

Completes NanoClaw v1 to v2 migration by seeding owners, cleaning configs, and porting customizations.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill migrate-from-v1-rosedwayane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-from-v1
Source: https://github.com/roseDwayane/LocalizeAgenticSys/tree/main/nanoclaw/.claude/skills/migrate-from-v1
Command: npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill migrate-from-v1-rosedwayane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running the deterministic migrate-v2.sh script, a NanoClaw v1-to-v2 migration still has judgment-dependent leftovers: unseeded owner roles, bloated CLAUDE.local.md files full of obsolete v1 boilerplate, unverified container mounts, and fork customizations that need triage. This Skill guides an AI agent through finishing those steps safely. ## Core Features & Use Cases - Migration handoff triage: Reads logs/setup-migration/handoff.json, fixes blocking failures, and smoke-tests that v2 routes real messages before deeper work. - Owner and access setup: Grants the owner role via the permissions DB helpers and configures unknown_sender_policy (public, strict, or request_approval), optionally importing known senders from the v1 message database. - CLAUDE.local.md cleanup: Diffs each group's file against its v1 template, strips stock boilerplate now handled by v2 fragments, fixes stale workspace paths, and shows proposed content before writing. - Container config and fork porting: Validates additionalMounts host paths, converts fallback sidecar configs, and helps copy or archive v1 fork customizations. - Use Case: You ran bash migrate-v2.sh and the bot is up, but your agent groups still carry v1 instructions and nobody has admin rights. Invoke this Skill to finish the migration end to end. ## Quick Start Ask the agent to finish the v1 migration by saying "finish my NanoClaw v1 to v2 migration" after migrate-v2.sh has completed.

Frequently Asked Questions about migrate-from-v1

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

FAQPage Schema
How do I finish a NanoClaw v1 to v2 migration?

Run `bash migrate-v2.sh` in your terminal first, then invoke this Skill. It reads logs/setup-migration/handoff.json, fixes blocking failures, seeds the owner role, cleans CLAUDE.local.md files, and verifies the install with the setup verify step.

How do I grant the owner role in NanoClaw v2?

Query the users table to find your ID in the format channel_type:platform_handle, then call grantRole from src/modules/permissions/db/user-roles.ts with role 'owner' and a null agent_group_id. Check getUserRoles first so the operation stays re-runnable.

Can I run migrate-v2.sh from inside a Claude session?

No. The script needs interactive prompts for channel selection and service switchover, plus Node, pnpm, Docker, and OneCLI setup with real shell I/O. Run it in your terminal; it hands control back to Claude automatically when done.

What happens to my v1 install during migration?

The v1 checkout is treated as read-only and is never modified. v1's service is paused rather than deleted during the switchover test, so reverting is a single service restart if v2 fails to route messages.

Why is my CLAUDE.local.md full of old v1 instructions?

The migration copies v1's entire CLAUDE.md into CLAUDE.local.md verbatim. This Skill diffs it against the original v1 template, removes stock sections now covered by v2 fragments, fixes stale workspace paths, and shows you the result before writing.

Can v1 fork source code be ported to v2?

No. v2's architecture is fundamentally different, so src/* and agent-runner code is not portable. The Skill stashes it to docs/v1-fork-reference/ with explanatory notes, while portable items like skills and docs can be copied with flagged v1-only references.