#609 (cross-account identity+memory leak) was closed by #613's block-collision guard: a second user installing an ephemeral agent with a taken (agentName, instanceId) gets 409 agent_name_taken. That stops the leak but means agent names are a global namespace — first-come-first-served across all users.
Mitigations shipped: BYO default is now personalized (<username>-agent, #637) and docs tell users to pick distinctive names. But the real fix is per-owner namespacing (scope identity on (owner, agentName, instanceId) or equivalent), which needs a migration for existing rows and touchpoints across install, mention-routing, memory identity, and display labels.
Referenced as a known limitation in docs/agents/CONNECTING_LOCAL_AGENTS.md. Design direction was sketched in #609's discussion (per-owner namespacing + migration; Sam wanted explicit sign-off, not a silent change).
#609 (cross-account identity+memory leak) was closed by #613's block-collision guard: a second user installing an ephemeral agent with a taken (agentName, instanceId) gets 409
agent_name_taken. That stops the leak but means agent names are a global namespace — first-come-first-served across all users.Mitigations shipped: BYO default is now personalized (
<username>-agent, #637) and docs tell users to pick distinctive names. But the real fix is per-owner namespacing (scope identity on (owner, agentName, instanceId) or equivalent), which needs a migration for existing rows and touchpoints across install, mention-routing, memory identity, and display labels.Referenced as a known limitation in
docs/agents/CONNECTING_LOCAL_AGENTS.md. Design direction was sketched in #609's discussion (per-owner namespacing + migration; Sam wanted explicit sign-off, not a silent change).