Buzz Desktop desktop-v0.5.23 (latest desktop tag in the repo; installed 2026-09-05), buzz CLI buzz.exe dated 2026-09-05 (no version string; buzz --version is not a valid argument). Relay: a Buzz-hosted community relay (*.communities.buzz.xyz), not self-hosted. OS: Windows 11 Pro 10.0.26200, Hyper-V VM; agents run via buzz-acp with the Claude runtime.
2026-09-07 17:44 local, Windows: Buzz Desktop migrated its own data directory from %APPDATA%\Buzz to %APPDATA%\xyz.block.buzz.app (marker file identity.migrated; nobody moved anything by hand). At 17:48-17:49 the new managed-agents.json listed all eight managed agents with NEW key pairs (example: one agent went from 475722cb... to 88975eeb...).
Expected: an app update/migration keeps agent identities.
Observed: every channel membership, at-mention, workflow step and DM of the fleet pointed at the old keys; the owner had to re-invite eight agents and archive the dead profiles. A 6-result search for "pubkey migration" found no existing issue.
Buzz Desktop desktop-v0.5.23 (latest desktop tag in the repo; installed 2026-09-05), buzz CLI buzz.exe dated 2026-09-05 (no version string; buzz --version is not a valid argument). Relay: a Buzz-hosted community relay (*.communities.buzz.xyz), not self-hosted. OS: Windows 11 Pro 10.0.26200, Hyper-V VM; agents run via buzz-acp with the Claude runtime.
2026-09-07 17:44 local, Windows: Buzz Desktop migrated its own data directory from %APPDATA%\Buzz to %APPDATA%\xyz.block.buzz.app (marker file identity.migrated; nobody moved anything by hand). At 17:48-17:49 the new managed-agents.json listed all eight managed agents with NEW key pairs (example: one agent went from 475722cb... to 88975eeb...).
Expected: an app update/migration keeps agent identities.
Observed: every channel membership, at-mention, workflow step and DM of the fleet pointed at the old keys; the owner had to re-invite eight agents and archive the dead profiles. A 6-result search for "pubkey migration" found no existing issue.