{"version":"2.1.232","anchor":"mention-another-session-or-agent-in-your-prompt","canonical_anchor":"mention-another-session-or-agent-in-your-prompt","heading":"@-mention another session or agent in your prompt","tier":"use","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/mention-another-session-or-agent-in-your-prompt","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### @-mention another session or agent in your prompt\n\nType `@name` in a prompt to complete and address a running agent, local, cloud or bridge session.\n\n**What**\n\nTyping `@name` or `@\"name with spaces\"` in a prompt now offers completions and resolves to a running agent, a local session, a cloud session or a bridge session. An optional `[ref]` suffix disambiguates when several candidates share a name.\n\n**Details**\n\n- Sessions still using the automatically derived default name are excluded, so you cannot mention one by its directory name by accident.\n- Each attempt records telemetry under `input_peer_at_mention` with the outcome: resolved, needs a follow-up question, or not found.\n- Cloud and bridge candidates only appear when the cloud-session access gate above is satisfied; agents and local sessions do not depend on it.\n\n**Evidence**\n\n`input_peer_at_mention`\n\n- Area: Cross-Session Messaging\n- Names: `@`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 4\/5"}