v0.10.6 - Preserve Config on Re-registration

Bug Fixes

Preserve Agent Configuration During Re-registration

Problem: When you deleted an agent from the manager and re-registered it (using the same agent ID), the configuration was lost. The Git config file was overwritten with an empty template, even though the agent's local config and the old Git file both had the full configuration.

Root Cause: During registration, the manager always created a fresh empty config and saved it to Git, unconditionally overwriting any existing config for that agent ID.

Solution: Manager now checks if a Git config already exists for the agent ID during registration:

• If config exists: Preserves existing workflows, file watchers, and settings; only updates hostname/platform
• If config doesn't exist: Creates new empty initial config as before

Re-registration Workflow Now Works

The following workflow now works correctly:

1. Delete agent from manager UI (removes database entry only, Git config remains)
2. Generate new token in manager
3. Re-register agent using the new token (agent keeps same ID from local config.json)
4. Manager preserves config: Existing Git configuration is maintained
5. Agent pulls config: Gets workflows and file watchers back automatically

Alternatively, you can use ./agent.exe -push-config after re-registration, and it will work correctly.

Benefits

• No more lost configuration when troubleshooting connection issues
• Safe to remove and re-add agents for testing
• Agent identity (ID) remains stable across registrations
• Simplified agent maintenance workflow

---

Full Changelog: v0.10.5...v0.10.6