You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With both devices of the same owner on desktop-v0.5.7, mentioning a managed agent from a second device in a channel (not a DM) still mints a second identity for that agent instead of reaching the running instance on the host device.
Steps to reproduce
On machine A, create a managed agent ("Test agent") and start it. Public key b060393e…4794.
On machine B (same owner, same workspace, also desktop-v0.5.7), open a channel both are in.
Mention @Test agent.
Expected
The mention reaches the running instance on machine A. No new identity is created.
Actual
Machine B mints a second identity for the same agent name, public key 2261ce75…ec44. Both are shown as "managed by you". The instance on machine A does not respond. Machine B renders a "needs configuration" card for the local instance it just created.
Notes
fix(desktop): allow shared agent mentions #4913 ("allow shared agent mentions") appears to have addressed picker eligibility, but the sender-side spawn path (useMentionSendFlow → createMentionedPersonaAgents with ensureRunning: true) still instantiates locally.
Reproduced in a channel, so this is not the deliberate DM fail-closed behaviour.
Removing the local ACP adapter on machine B changes the symptom to an honest "adapter isn't installed" card, but does not prevent the mint attempt.
Summary
With both devices of the same owner on
desktop-v0.5.7, mentioning a managed agent from a second device in a channel (not a DM) still mints a second identity for that agent instead of reaching the running instance on the host device.Steps to reproduce
b060393e…4794.desktop-v0.5.7), open a channel both are in.@Test agent.Expected
The mention reaches the running instance on machine A. No new identity is created.
Actual
Machine B mints a second identity for the same agent name, public key
2261ce75…ec44. Both are shown as "managed by you". The instance on machine A does not respond. Machine B renders a "needs configuration" card for the local instance it just created.Notes
useMentionSendFlow→createMentionedPersonaAgentswithensureRunning: true) still instantiates locally.Environment
macOS,
desktop-v0.5.7on both devices, self-hosted relay, single owner.