archon-move-project

To move an Archon project safely, use a non-destructive relocation workflow that applies pre-move backups and post-move fixes. It regenerates venvs, updates paths, and migrates memory, preserving your project configurations without data loss.

Claude Code memory is preserved during relocation using a copy-based migration process. This non-destructive approach ensures your memory data remains intact, while old namespace cleanup only occurs with explicit confirmation.

The best way to prepare for relocation is to verify your git state and create a full backup. Following interactive checklist prompts ensures all pre-move preparations are complete before you move the project directory.

Yes, you need to regenerate venvs after moving an Archon project. Post-move recovery includes regenerating virtual environments and updating path references to ensure Docker and frontend components remain fully operational.

Yes, you can clean up old Claude Code namespaces after migration, but it is optional. The relocation workflow is non-destructive by default, meaning namespace cleanup only executes when you provide explicit confirmation.