This guide covers how to upgrade your Code Conductor installation to the latest version.
Run the same installation command you used initially:
bash <(curl -fsSL https://raw.githubusercontent.com/ryanmac/code-conductor/main/conductor-init.sh)When prompted, choose option 1: Upgrade
The installer automatically detects:
- Your current Code Conductor version (from
VERSIONfile) - Whether an existing installation is present (
.conductordirectory) - The latest available version from GitHub
Before upgrading, the installer backs up:
.conductor/config.yaml- Your project configuration.conductor/CLAUDE.md- Your AI agent instructionsCLAUDE.md- Root-level AI instructions
Only these components are updated:
.conductor/scripts/- Core conductor commands.conductor/roles/- Role definitions.github/workflows/- GitHub Actionssetup.py- Setup scriptrequirements.txt- Python dependenciespyproject.toml- Poetry configurationVERSION- Version tracking file
After updating core files, your backed-up configurations are restored to their original locations.
✅ Fully Preserved:
- Your project configuration (
.conductor/config.yaml) - Custom AI instructions (
CLAUDE.mdfiles) - All GitHub issues and tasks
- Git worktrees and branches
- Agent work in progress
- Task assignments and states
❌ Not Preserved (Intentionally Updated):
- Core scripts and commands
- Role definitions
- GitHub workflow files
- Python dependencies
If you prefer to upgrade manually or need to customize the process:
cp .conductor/config.yaml .conductor/config.yaml.backup
cp .conductor/CLAUDE.md .conductor/CLAUDE.md.backup
cp CLAUDE.md CLAUDE.md.backup 2>/dev/null || truecurl -fsSL https://github.com/ryanmac/code-conductor/archive/main.tar.gz -o conductor-latest.tar.gz
tar -xzf conductor-latest.tar.gz# Update scripts
cp -r code-conductor-main/.conductor/scripts/* .conductor/scripts/
# Update roles
cp -r code-conductor-main/.conductor/roles/* .conductor/roles/
# Update workflows
cp -r code-conductor-main/.github/workflows/* .github/workflows/
# Update setup files
cp code-conductor-main/setup.py .
cp code-conductor-main/requirements.txt .
cp code-conductor-main/pyproject.toml .
cp code-conductor-main/VERSION .cp .conductor/config.yaml.backup .conductor/config.yaml
cp .conductor/CLAUDE.md.backup .conductor/CLAUDE.md
cp CLAUDE.md.backup CLAUDE.md 2>/dev/null || truerm -rf code-conductor-main conductor-latest.tar.gz
rm .conductor/*.backup CLAUDE.md.backup 2>/dev/null || true- Enhanced task listing with rich formatting and priority indicators
- Improved status command with health checks
- Better error handling and recovery mechanisms
- Automatic upgrade detection and seamless upgrade process
- Claude Code automation prompts
- Added conductor wrapper script for simplified commands
- Improved agent coordination with heartbeat monitoring
- Enhanced GitHub integration
- Initial release with core functionality
- GitHub Issues as tasks
- AI code review integration
- Multiple agent role support
Solution: Ensure you have a VERSION file in your project root. If missing:
echo "1.0.0" > VERSION # Replace with your actual versionSolution: The installer creates backups in /tmp/conductor-backup-*. To recover:
# Find backup directory
ls -la /tmp/conductor-backup-*
# Restore from backup
cp /tmp/conductor-backup-*/config.yaml .conductor/Solution: Ensure executable permissions are set:
chmod +x .conductor/scripts/*
chmod +x conductorSolution: Recreate your virtual environment:
# If using venv
rm -rf .venv
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
# If using Poetry
poetry installIf you need to downgrade to a previous version:
- Note your current configuration
- Remove the existing installation:
rm -rf .conductor .github/workflows/conductor-*.yml - Install the specific version you want:
# Replace VERSION with desired version tag curl -fsSL https://raw.githubusercontent.com/ryanmac/code-conductor/VERSION/conductor-init.sh | bash
- Documentation: https://github.com/ryanmac/code-conductor
- Issues: https://github.com/ryanmac/code-conductor/issues
- Community: Join discussions in GitHub Issues
- Always backup before upgrading - While the installer does this automatically, having your own backup is recommended
- Test in a branch first - Create a test branch to verify the upgrade works with your project
- Check the changelog - Review what's new before upgrading to understand the changes
- Upgrade regularly - Stay current to get bug fixes and new features
- Report issues - If you encounter problems, please report them to help improve the upgrade process